Observed topology
AS35200 TransitX-Ltd TransitX Ltd
Unclassified RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS35200: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 | 284 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 224 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 147 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 60 |
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 51 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 34 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 30 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 15 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 15 |
Transit
Downstream networks
Networks for which AS35200 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS199741 | TransitX Ltd | Unclassified | IPv4 IPv6 | 7,948 |
| AS42831 | UK Dedicated Servers Limited | Hosting | IPv4 | 4,610 |
| AS64080 | SYN LTD | Unclassified | IPv4 | 1,106 |
| AS142594 | SpeedyPage Ltd | Unclassified | IPv4 IPv6 | 551 |
| AS61272 | UAB Bacloud | Unclassified | IPv4 IPv6 | 504 |
| AS200260 | Debugged Ltd | Hosting | IPv4 | 450 |
| AS7489 | HostUS | Hosting | IPv4 | 394 |
| AS202448 | MVPS LTD | Unclassified | IPv4 IPv6 | 386 |
| AS58051 | Alpha Internet Limited | Unclassified | IPv4 IPv6 | 361 |
| AS27176 | DataWagon LLC | Hosting | IPv4 IPv6 | 327 |
Adjacency
Adjacent networks
Every AS seen directly next to AS35200 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS199741 | TransitX Ltd | Unclassified | IPv4 IPv6 | 7,948 |
| AS42831 | UK Dedicated Servers Limited | Hosting | IPv4 IPv6 | 7,811 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 7,479 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,810 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 1,767 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 1,626 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 1,128 |
| AS64080 | SYN LTD | Unclassified | IPv4 | 1,106 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 914 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 560 |
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.