asn.dev

Observed topology

AS54201 WEWORK-MANAGEMENT-LLC

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS54201: 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
AS9318SK Broadband Co LtdUnclassifiedIPv4378
AS3356Level 3 Parent, LLCTransitIPv4 IPv6277
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6251
AS701Verizon BusinessResidentialIPv6118
AS3786LG DACOM CorporationUnclassifiedIPv477
AS33491Comcast Cable Communications, LLCUnclassifiedIPv668
AS6461Zayo BandwidthTransitIPv665
AS46887Crown Castle Fiber LLCUnclassifiedIPv662
AS3257GTT Communications Inc.TransitIPv646
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv643

All 21 upstreams →

Transit

Downstream networks

inferred

Networks for which AS54201 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 21

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

ASNetworkTypeFamiliesPaths seen
AS9318SK Broadband Co LtdUnclassifiedIPv4378
AS3356Level 3 Parent, LLCTransitIPv4 IPv6277
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6251
AS701Verizon BusinessResidentialIPv6118
AS3786LG DACOM CorporationUnclassifiedIPv477
AS33491Comcast Cable Communications, LLCUnclassifiedIPv668
AS6461Zayo BandwidthTransitIPv665
AS46887Crown Castle Fiber LLCUnclassifiedIPv662
AS3257GTT Communications Inc.TransitIPv646
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv643

All 21 adjacent →

Provenance

Where this comes from

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