Observed topology
AS39521 TNGNET
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS39521: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,268 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 524 |
| AS6830 | Liberty Global Europe Holding B.V. | Residential | IPv4 IPv6 | 288 |
| AS5511 | Orange S.A. | Transit | IPv4 | 221 |
| AS61138 | Zappie Host LLC | Unclassified | IPv4 IPv6 | 96 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 88 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 86 |
| AS6206 | Netrouting B.V. | Hosting | IPv4 | 60 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 59 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 56 |
Transit
Downstream networks
Networks for which AS39521 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213784 | TNGNET B.V. | Unclassified | IPv4 | 2,809 |
| AS47690 | TNGNET B.V. | Unclassified | IPv4 | 2,617 |
| AS60117 | Host Sailor Ltd | Unclassified | IPv4 IPv6 | 2,340 |
| AS61060 | NXTcom Nederland BV | Unclassified | IPv4 IPv6 | 633 |
| AS207778 | Jacobus Huijbrechts | Unclassified | IPv4 IPv6 | 117 |
| AS31800 | DALnet | Unclassified | IPv4 | 98 |
| AS24381 | BGP.Exchange | Hosting | IPv6 | 33 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39521 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,137 |
| AS213784 | TNGNET B.V. | Unclassified | IPv4 | 2,809 |
| AS47690 | TNGNET B.V. | Unclassified | IPv4 | 2,617 |
| AS60117 | Host Sailor Ltd | Unclassified | IPv4 IPv6 | 2,340 |
| AS6206 | Netrouting B.V. | Hosting | IPv4 | 1,868 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,646 |
| AS6830 | Liberty Global Europe Holding B.V. | Residential | IPv4 IPv6 | 875 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 670 |
| AS61138 | Zappie Host LLC | Unclassified | IPv4 IPv6 | 640 |
| AS61060 | NXTcom Nederland BV | Unclassified | IPv4 IPv6 | 633 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.