asn.dev

Observed topology

AS31726 TELEFIBER

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31726: 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
AS29695Lyse Tele ASUnclassifiedIPv4 IPv6430
AS6939Hurricane Electric LLCTransitIPv4 IPv6231
AS2116GLOBALCONNECT ASResidentialIPv4 IPv6142
AS50304Blix Solutions ASUnclassifiedIPv4 IPv625
AS24482SG.GSHostingIPv4 IPv615
AS34927iFog GmbHHostingIPv4 IPv615
AS49788Nexthop ASUnclassifiedIPv415
AS57381Daniel HusandUnclassifiedIPv4 IPv615
AS56655Gigahost ASUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59978Hafslund Kraft ASUnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29695Lyse Tele ASUnclassifiedIPv4 IPv6437
AS6939Hurricane Electric LLCTransitIPv4 IPv6231
AS2116GLOBALCONNECT ASResidentialIPv4 IPv6144
AS50304Blix Solutions ASUnclassifiedIPv4 IPv626
AS24482SG.GSHostingIPv4 IPv616
AS34927iFog GmbHHostingIPv4 IPv616
AS57381Daniel HusandUnclassifiedIPv4 IPv616
AS49788Nexthop ASUnclassifiedIPv415
AS59978Hafslund Kraft ASUnclassifiedIPv413
AS56655Gigahost ASUnclassifiedIPv45

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.