Observed topology
AS35332 DATAWEB DataWeb B.V.
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS35332: 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.
Transit
Downstream networks
Networks for which AS35332 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16089 | iPublications Holding B.V. | Unclassified | IPv4 IPv6 | 217 |
| AS8694 | Rotterdamse Electrische Tram N.V. | Unclassified | IPv4 | 122 |
| AS31433 | STEF Nederland B.V. | Unclassified | IPv4 | 61 |
| AS209936 | Databalance Services B.V. | Unclassified | IPv4 IPv6 | 53 |
| AS215922 | BMC Software Distribution BV | Unclassified | IPv4 | 31 |
| AS61346 | Heerema Marine Contractors Nederland SE | Unclassified | IPv4 | 23 |
| AS30012 | Universal Music Group, INC. | Unclassified | IPv4 | 16 |
Adjacency
Adjacent networks
Every AS seen directly next to AS35332 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6830 | Liberty Global Europe Holding B.V. | Residential | IPv4 IPv6 | 557 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 513 |
| AS8455 | atom86 BV | Hosting | IPv4 IPv6 | 443 |
| AS16089 | iPublications Holding B.V. | Unclassified | IPv4 IPv6 | 217 |
| AS8694 | Rotterdamse Electrische Tram N.V. | Unclassified | IPv4 | 122 |
| AS31433 | STEF Nederland B.V. | Unclassified | IPv4 | 61 |
| AS209936 | Databalance Services B.V. | Unclassified | IPv4 IPv6 | 53 |
| AS215922 | BMC Software Distribution BV | Unclassified | IPv4 | 31 |
| AS61346 | Heerema Marine Contractors Nederland SE | Unclassified | IPv4 | 23 |
| AS30012 | Universal Music Group, INC. | Unclassified | IPv4 | 16 |
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.