asn.dev

Observed topology

AS51013 WEBSUPPORT-SRO-SK-AS

Hosting RIPE

Upstreams 10 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 7
Upstream graph Who carries AS51013, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS51013 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51013: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4480
AS6939Hurricane Electric LLCTransitIPv4 IPv6290
AS174Cogent Communications, LLCTransitIPv4 IPv6268
AS199803ComSource s.r.o.HostingIPv4247
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv646
AS31230Slovak University of Technology in BratislavaUnclassifiedIPv4 IPv629
AS33891Core-Backbone GmbHHostingIPv424
AS24482SG.GSHostingIPv4 IPv620
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv620
AS8447A1 Telekom Austria AGResidentialIPv43

Transit

Downstream networks

inferred

Networks for which AS51013 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS25234ACTIVE 24, s.r.o.HostingIPv4 IPv65

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS51013 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4480
AS6939Hurricane Electric LLCTransitIPv4 IPv6290
AS174Cogent Communications, LLCTransitIPv4 IPv6268
AS199803ComSource s.r.o.HostingIPv4247
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv647
AS31230Slovak University of Technology in BratislavaUnclassifiedIPv4 IPv629
AS33891Core-Backbone GmbHHostingIPv424
AS24482SG.GSHostingIPv4 IPv622
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv622
AS25234ACTIVE 24, s.r.o.HostingIPv4 IPv65

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.