Observed topology
AS62000 NETRIX-AS Netrix
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 | 451 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 215 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 208 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 202 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 147 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 78 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 49 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 39 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 27 |
| AS37721 | Virtual Technologies & Solutions | Residential | 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 | 988 |
| AS47160 | MOJI SAS | Residential | IPv4 IPv6 | 807 |
| AS207992 | FEELB SARL | Unclassified | IPv4 IPv6 | 711 |
| AS208226 | Ouiheberg SARL | Unclassified | IPv4 IPv6 | 623 |
| AS60718 | OELIS SARL | Unclassified | IPv4 IPv6 | 434 |
| AS209097 | NETSYST SAS | Hosting | IPv4 IPv6 | 418 |
| AS198053 | GREEN DATA SAS | Unclassified | IPv4 IPv6 | 409 |
| AS198831 | GENIUSWEER SAS | Hosting | IPv4 | 346 |
| AS215596 | KISSGROUP SAS | Residential | IPv4 IPv6 | 325 |
| AS198825 | VERYCLOUD SAS | Unclassified | IPv4 IPv6 | 294 |
Adjacency
Adjacent networks
Every AS seen directly next to AS62000 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 4,385 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 3,202 |
| AS47160 | MOJI SAS | Residential | IPv4 IPv6 | 3,083 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,097 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,018 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 1,473 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,083 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,048 |
| AS207992 | FEELB SARL | Unclassified | IPv4 IPv6 | 1,041 |
| AS202089 | Unimedia Services SAS | Unclassified | IPv4 IPv6 | 988 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.