Observed topology
AS8283 COLOCLUE-AS Netwerkvereniging Coloclue
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8283: 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 |
|---|---|---|---|---|
| AS49127 | Asimo Networks B.V. | Hosting | IPv4 IPv6 | 33 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 30 |
| AS57866 | Fusix Networks B.V. | Unclassified | IPv4 IPv6 | 30 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 23 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 10 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 8 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 4 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 4 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 4 |
Transit
Downstream networks
Networks for which AS8283 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200998 | Final Frontier B.V. | Unclassified | IPv4 IPv6 | 455 |
| AS213333 | Jacob Willem de Vos | Unclassified | IPv4 IPv6 | 215 |
| AS45009 | Rogier Krieger | Hosting | IPv4 IPv6 | 130 |
| AS4601 | Antonios A. Chariton | Unclassified | IPv4 IPv6 | 124 |
| AS30875 | V.R.I.S. Consultancy Services B.V. | Unclassified | IPv4 IPv6 | 95 |
| AS38970 | Michiel Klaver | Unclassified | IPv4 IPv6 | 95 |
| AS57984 | XINDI Networks SRL | Unclassified | IPv4 IPv6 | 95 |
| AS206218 | Anne-Jan Zwart | Unclassified | IPv4 IPv6 | 95 |
| AS209845 | Jacob Willem de Vos | Unclassified | IPv4 IPv6 | 95 |
| AS214810 | Mitchell van der Velden | Unclassified | IPv4 IPv6 | 95 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8283 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49127 | Asimo Networks B.V. | Hosting | IPv4 IPv6 | 680 |
| AS200998 | Final Frontier B.V. | Unclassified | IPv4 IPv6 | 455 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 436 |
| AS57866 | Fusix Networks B.V. | Unclassified | IPv4 IPv6 | 372 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 277 |
| AS213333 | Jacob Willem de Vos | Unclassified | IPv4 IPv6 | 215 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 163 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 163 |
| AS4601 | Antonios A. Chariton | Unclassified | IPv4 IPv6 | 136 |
| AS45009 | Rogier Krieger | Hosting | IPv4 IPv6 | 130 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.