asn.dev

Observed topology

AS62917 GIGABITFIBER-ICFN

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62917: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6849
AS6461Zayo BandwidthTransitIPv4 IPv6374
AS1299Arelion Sweden ABTransitIPv4 IPv6150
AS32505ConterraUnclassifiedIPv4 IPv690
AS3257GTT Communications Inc.TransitIPv4 IPv657
AS3356Level 3 Parent, LLCTransitIPv4 IPv654
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv617
AS971PureVoltage Hosting Inc.UnclassifiedIPv415
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397161North Texas Fiber, IncUnclassifiedIPv4130
AS40107Quality Technology Services, LLCUnclassifiedIPv465

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6997
AS6461Zayo BandwidthTransitIPv4 IPv6386
AS1299Arelion Sweden ABTransitIPv4 IPv6150
AS397161North Texas Fiber, IncUnclassifiedIPv4130
AS32505ConterraUnclassifiedIPv4 IPv690
AS3257GTT Communications Inc.TransitIPv4 IPv674
AS3356Level 3 Parent, LLCTransitIPv4 IPv672
AS40107Quality Technology Services, LLCUnclassifiedIPv465
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv617
AS971PureVoltage Hosting Inc.UnclassifiedIPv415

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.