asn.dev

Observed topology

AS54429 LOCAL-CONNECTIVITY-LAB - Local Connectivity Lab

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS54429: 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
AS101University of WashingtonUnclassifiedIPv4 IPv6163
AS6939Hurricane Electric LLCTransitIPv668
AS395823doof.netUnclassifiedIPv448
AS26073Cofractal, Inc.UnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv63
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv63
AS3130RGnet OUUnclassifiedIPv41
AS9002RETN LimitedUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401894/dev/hackUnclassifiedIPv4 IPv6162

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS395823doof.netUnclassifiedIPv4166
AS101University of WashingtonUnclassifiedIPv4 IPv6163
AS401894/dev/hackUnclassifiedIPv4 IPv6162
AS6939Hurricane Electric LLCTransitIPv6102
AS26073Cofractal, Inc.UnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv66
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv66
AS3130RGnet OUUnclassifiedIPv43
AS9002RETN LimitedUnclassifiedIPv43

Provenance

Where this comes from

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