Observed topology
AS60439 SERVERNET-AS
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS60439: 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 |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 1,198 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 459 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 175 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 76 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 65 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 62 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 41 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 41 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 31 |
| AS12859 | BIT BV | Hosting | IPv4 IPv6 | 24 |
Transit
Downstream networks
Networks for which AS60439 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS207477 | PEACHY SERVERS LIMITED | Unclassified | IPv4 IPv6 | 96 |
| AS14475 | D4 Networks L.L.C. | Unclassified | IPv4 IPv6 | 94 |
| AS199738 | VATORA LIMITED | Unclassified | IPv4 IPv6 | 94 |
| AS402072 | OZONTI NETWORK LLC | Unclassified | IPv4 IPv6 | 94 |
| AS208024 | Ronald Agorsah trading as Alpenhost e.U. | Unclassified | IPv4 IPv6 | 93 |
| AS206479 | AceRDP Ltd | Unclassified | IPv4 | 59 |
| AS402162 | Benthost LLC | Unclassified | IPv4 | 59 |
| AS63025 | NOHAVPS LLC | Hosting | IPv6 | 36 |
Adjacency
Adjacent networks
Every AS seen directly next to AS60439 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 1,463 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 571 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 281 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 149 |
| AS207477 | PEACHY SERVERS LIMITED | Unclassified | IPv4 IPv6 | 96 |
| AS14475 | D4 Networks L.L.C. | Unclassified | IPv4 IPv6 | 94 |
| AS199738 | VATORA LIMITED | Unclassified | IPv4 IPv6 | 94 |
| AS402072 | OZONTI NETWORK LLC | Unclassified | IPv4 IPv6 | 94 |
| AS208024 | Ronald Agorsah trading as Alpenhost e.U. | Unclassified | IPv4 IPv6 | 93 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 88 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.