asn.dev

Observed topology

AS54600 PEG-SV

Hosting DROP-listed space ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS54600: 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 IPv611,352
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv67,138
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv42,011
AS6939Hurricane Electric LLCTransitIPv41,379
AS3223Voxility LLPHostingIPv4818
AS4809China Telecom Next Generation Carrier NetworkUnclassifiedIPv4307
AS24482SG.GSHostingIPv4165
AS398823PEG TECH INCHostingIPv491
AS58453China Mobile International LimitedUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398823PEG TECH INCHostingIPv42,223
AS402169Uscloud IncUnclassifiedIPv41,419
AS151630Yun Zhong Technology LimitedUnclassifiedIPv4628

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv612,991
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv68,504
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv43,395
AS398823PEG TECH INCHostingIPv43,096
AS151630Yun Zhong Technology LimitedUnclassifiedIPv41,883
AS402169Uscloud IncUnclassifiedIPv41,419
AS6939Hurricane Electric LLCTransitIPv41,379
AS3223Voxility LLPHostingIPv4859
AS4809China Telecom Next Generation Carrier NetworkUnclassifiedIPv4619
AS24482SG.GSHostingIPv4165

All 12 adjacent →

Provenance

Where this comes from

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