asn.dev

Observed topology

AS202053 UPCLOUD UpCloud Ltd

Hosting RIPE Content

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

Transit

Upstream networks

All 41

Networks observed carrying traffic for AS202053: 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 IPv61,769
AS6939Hurricane Electric LLCTransitIPv4 IPv6738
AS174Cogent Communications, LLCTransitIPv4 IPv6688
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6124
AS3356Level 3 Parent, LLCTransitIPv4 IPv6109
AS4657StarHub LtdResidentialIPv4 IPv6107
AS4637Telstra GlobalUnclassifiedIPv4 IPv680
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv673
AS2914NTT America, Inc.TransitIPv4 IPv662
AS12552GlobalConnect ABUnclassifiedIPv460

All 41 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213427Lettermint B.V.HostingIPv4 IPv6150

Adjacency

Adjacent networks

All 42

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,842
AS6939Hurricane Electric LLCTransitIPv4 IPv6769
AS174Cogent Communications, LLCTransitIPv4 IPv6688
AS213427Lettermint B.V.HostingIPv4 IPv6150
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6127
AS3356Level 3 Parent, LLCTransitIPv4 IPv6109
AS4657StarHub LtdResidentialIPv4 IPv6109
AS4637Telstra GlobalUnclassifiedIPv4 IPv680
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv676
AS2914NTT America, Inc.TransitIPv4 IPv662

All 42 adjacent →

Provenance

Where this comes from

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