Observed topology
AS43366 OSSO OSSO B.V.
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS43366: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 234 |
| AS6830 | Liberty Global Europe Holding B.V. | Residential | IPv4 IPv6 | 132 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 111 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 12 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 12 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 12 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 12 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 12 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS43366 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203135 | CTNET B.V. | Unclassified | IPv4 IPv6 | 153 |
| AS41153 | Gamma Communications Nederland B.V. | Hosting | IPv4 | 90 |
| AS201791 | Devhouse Spindle B.V. | Hosting | IPv4 IPv6 | 80 |
| AS60880 | Horizon Telecom B.V. | Unclassified | IPv4 IPv6 | 61 |
| AS202606 | Fiber Noord BV | Unclassified | IPv4 | 60 |
| AS44439 | Deksel Enterprises B.V. | Hosting | IPv4 | 56 |
| AS208209 | MobielWerkt B.V. | Unclassified | IPv4 | 55 |
| AS218967 | 2Hip Consultancy B.V. | Unclassified | IPv4 | 54 |
| AS215914 | NetGrid Holding B.V. | Unclassified | IPv4 | 36 |
| AS209495 | Stichting RTV Noord | Unclassified | IPv4 | 34 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43366 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 543 |
| AS6830 | Liberty Global Europe Holding B.V. | Residential | IPv4 IPv6 | 265 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 187 |
| AS203135 | CTNET B.V. | Unclassified | IPv4 IPv6 | 153 |
| AS41153 | Gamma Communications Nederland B.V. | Hosting | IPv4 | 90 |
| AS201791 | Devhouse Spindle B.V. | Hosting | IPv4 IPv6 | 80 |
| AS60880 | Horizon Telecom B.V. | Unclassified | IPv4 IPv6 | 73 |
| AS202606 | Fiber Noord BV | Unclassified | IPv4 | 60 |
| AS44439 | Deksel Enterprises B.V. | Hosting | IPv4 | 56 |
| AS208209 | MobielWerkt B.V. | Unclassified | IPv4 | 55 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.