Observed topology
AS203329 ESHELTER NTT Global Data Centers EMEA GmbH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS203329: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 283 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 229 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 169 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 110 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 63 |
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 | 51 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 33 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 17 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 13 |
Transit
Downstream networks
Networks for which AS203329 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62075 | Julian Lannert | Unclassified | IPv4 IPv6 | 203 |
| AS50246 | 360 Treasury Systems AG | Unclassified | IPv4 | 61 |
| AS47219 | NTT Global Data Centers EMEA UK Ltd. | Hosting | IPv4 IPv6 | 50 |
| AS208025 | RSG Group GmbH | Unclassified | IPv4 | 49 |
| AS213314 | WallCloud GmbH | Unclassified | IPv4 IPv6 | 37 |
| AS715 | WoodyNet, Inc. | Unclassified | IPv6 | 34 |
| AS209419 | Julian Lannert | Unclassified | IPv6 | 20 |
| AS29205 | VERCOM S.A. | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS203329 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 364 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 319 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 263 |
| AS62075 | Julian Lannert | Unclassified | IPv4 IPv6 | 203 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 139 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 83 |
| AS50246 | 360 Treasury Systems AG | Unclassified | IPv4 | 61 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 56 |
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 | 51 |
| AS47219 | NTT Global Data Centers EMEA UK Ltd. | Hosting | IPv4 IPv6 | 50 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.