asn.dev

Observed topology

AS48417 ITS-

Unclassified APNIC NSP

Upstreams 13 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 8
Upstream graph Who carries AS48417, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS48417 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS48417: 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 ABTransitIPv4 IPv6413
AS6939Hurricane Electric LLCTransitIPv4 IPv656
AS15685CASABLANCA INT a.s.HostingIPv433
AS16019Vodafone Czech Republic a.s.UnclassifiedIPv417
AS6855Slovak Telekom, a.s.MobileIPv4 IPv614
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS25512CD-Telematika a.s.UnclassifiedIPv46
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

All 13 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6413
AS6939Hurricane Electric LLCTransitIPv4 IPv656
AS15685CASABLANCA INT a.s.HostingIPv433
AS16019Vodafone Czech Republic a.s.UnclassifiedIPv417
AS6855Slovak Telekom, a.s.MobileIPv4 IPv614
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS25512CD-Telematika a.s.UnclassifiedIPv46
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

All 13 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.