Observed topology
AS62000 AS62000 SERVERD SAS
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS62000: 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 |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 457 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 196 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 189 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 181 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 158 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 94 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 56 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 43 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 28 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 27 |
Transit
Downstream networks
Networks for which AS62000 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202089 | Unimedia Services SAS | Unclassified | IPv4 IPv6 | 1,002 |
| AS47160 | MOJI SAS | Residential | IPv4 IPv6 | 807 |
| AS207992 | FEELB SARL | Unclassified | IPv4 IPv6 | 799 |
| AS208226 | Ouiheberg SARL | Unclassified | IPv4 IPv6 | 666 |
| AS198053 | GREEN DATA SAS | Unclassified | IPv4 IPv6 | 414 |
| AS60718 | OELIS SARL | Unclassified | IPv4 IPv6 | 320 |
| AS198825 | VERYCLOUD SAS | Unclassified | IPv4 IPv6 | 306 |
| AS209952 | Mistral Compute Holding SAS | Unclassified | IPv4 IPv6 | 261 |
| AS199088 | OctoGency SARL | Hosting | IPv4 | 248 |
| AS216155 | MIRIDIA SASU | Unclassified | IPv4 IPv6 | 234 |
Adjacency
Adjacent networks
Every AS seen directly next to AS62000 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47160 | MOJI SAS | Residential | IPv4 IPv6 | 2,813 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 2,353 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,220 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,123 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,020 |
| AS207992 | FEELB SARL | Unclassified | IPv4 IPv6 | 1,328 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,174 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,102 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 1,102 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,023 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.