Observed topology
AS202053 UPCLOUD
Hosting RIPE Content
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,816 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 753 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 750 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 127 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 109 |
| AS4657 | StarHub Ltd | Residential | IPv4 IPv6 | 104 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 74 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 70 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 66 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 62 |
Transit
Downstream networks
Networks for which AS202053 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213427 | Lettermint B.V. | Hosting | IPv4 IPv6 | 150 |
Adjacency
Adjacent networks
Every AS seen directly next to AS202053 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,892 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 780 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 753 |
| AS213427 | Lettermint B.V. | Hosting | IPv4 IPv6 | 150 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 130 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 109 |
| AS4657 | StarHub Ltd | Residential | IPv4 IPv6 | 106 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 77 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 70 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 66 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.