asn.dev

Observed topology

AS51154 PCLOUD

Hosting RIPE

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

Transit

Upstream networks

All 45

Networks observed carrying traffic for AS51154: 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 ABTransitIPv4347
AS2914NTT America, Inc.TransitIPv4122
AS3257GTT Communications Inc.TransitIPv4107
AS6939Hurricane Electric LLCTransitIPv482
AS34224Neterra Ltd.UnclassifiedIPv441
AS56665Proximus Luxembourg S.A.ResidentialIPv441
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv438
AS5511Orange S.A.TransitIPv431
AS34549meerfarbig GmbH & Co. KGHostingIPv415
AS24482SG.GSHostingIPv411

All 45 upstreams →

Transit

Downstream networks

inferred

Networks for which AS51154 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 45

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4347
AS2914NTT America, Inc.TransitIPv4122
AS3257GTT Communications Inc.TransitIPv4107
AS6939Hurricane Electric LLCTransitIPv482
AS34224Neterra Ltd.UnclassifiedIPv441
AS56665Proximus Luxembourg S.A.ResidentialIPv441
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv438
AS5511Orange S.A.TransitIPv431
AS34549meerfarbig GmbH & Co. KGHostingIPv415
AS24482SG.GSHostingIPv411

All 45 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 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.