Observed topology
AS20847 PREVIDER-AS Previder B.V.
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS20847: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 226 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 165 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 153 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 137 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 90 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 55 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 25 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 25 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 25 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 25 |
Transit
Downstream networks
Networks for which AS20847 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39591 | Previder B.V. | Hosting | IPv4 IPv6 | 1,411 |
| AS39390 | Mainfreight Holding BV | Unclassified | IPv4 | 159 |
| AS201597 | Previder B.V. | Unclassified | IPv4 IPv6 | 151 |
| AS48972 | BetterBe B.V. | Hosting | IPv4 IPv6 | 59 |
| AS56517 | Vitens N.V. | Unclassified | IPv4 | 59 |
| AS56599 | Dennis Doeve trading as I.C. Solutions | Unclassified | IPv4 | 58 |
| AS16350 | Root Holding B.V. | Unclassified | IPv4 IPv6 | 50 |
| AS213050 | Nedap N.V. | Unclassified | IPv4 IPv6 | 27 |
| AS211465 | Thales Nederland BV | Unclassified | IPv4 | 12 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20847 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39591 | Previder B.V. | Hosting | IPv4 IPv6 | 1,762 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 755 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 477 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 427 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 384 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 311 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 175 |
| AS39390 | Mainfreight Holding BV | Unclassified | IPv4 | 159 |
| AS201597 | Previder B.V. | Unclassified | IPv4 IPv6 | 151 |
| AS48972 | BetterBe B.V. | Hosting | IPv4 IPv6 | 74 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.