Observed topology
AS200020 NBIP-AS Stichting NBIP-NaWas
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS200020: 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 | 85 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 27 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 3 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 2 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 2 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 2 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 2 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS200020 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39647 | Enreach Netherlands B.V. | Hosting | IPv4 | 180 |
| AS24586 | Intermax Group B.V. | Hosting | IPv4 | 122 |
| AS8315 | WorldStream B.V. | Hosting | IPv4 | 121 |
| AS12414 | Solcon Internetdiensten B.V. | Residential | IPv4 | 62 |
| AS15703 | TrueFullstaq B.V. | Hosting | IPv4 | 62 |
| AS8368 | Dstny BE N.V. | Unclassified | IPv4 | 60 |
| AS34373 | XXLnet B.V. | Unclassified | IPv4 | 60 |
| AS57124 | Gemeente Maastricht | Unclassified | IPv4 | 60 |
| AS12859 | BIT BV | Hosting | IPv4 | 59 |
| AS39686 | Eurofiber Nederland BV | Residential | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS200020 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 779 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 352 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 243 |
| AS39647 | Enreach Netherlands B.V. | Hosting | IPv4 | 180 |
| AS24586 | Intermax Group B.V. | Hosting | IPv4 | 122 |
| AS8315 | WorldStream B.V. | Hosting | IPv4 | 121 |
| AS50266 | Odido Netherlands B.V. | Unclassified | IPv4 | 68 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 64 |
| AS12414 | Solcon Internetdiensten B.V. | Residential | IPv4 | 62 |
| AS15703 | TrueFullstaq B.V. | Hosting | IPv4 | 62 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.