Observed topology
AS39704 CJ2-AS
Hosting RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS39704: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 349 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 236 |
| AS6830 | Liberty Global Europe Holding B.V. | Residential | IPv4 | 90 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 19 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 19 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 19 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 19 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 19 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 19 |
Transit
Downstream networks
Networks for which AS39704 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202315 | Arcus IT Managed Services B.V. | Unclassified | IPv4 IPv6 | 306 |
| AS198508 | Plusine Systems B.V. | Hosting | IPv4 IPv6 | 289 |
| AS42152 | VCD Infra Solutions B.V. | Unclassified | IPv4 | 116 |
| AS48812 | Office IT B.V. | Unclassified | IPv4 | 116 |
| AS48501 | Init3 BV | Hosting | IPv4 IPv6 | 95 |
| AS215914 | NetGrid Holding B.V. | Unclassified | IPv4 | 84 |
| AS41037 | Meta Micro Automatisering B.V. | Hosting | IPv4 | 58 |
| AS41038 | Mediacaster B.V. | Unclassified | IPv4 IPv6 | 55 |
| AS204751 | MobielWerkt B.V. | Unclassified | IPv4 IPv6 | 43 |
| AS210882 | Tim Zuidema trading as TiZu | Unclassified | IPv6 | 36 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39704 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 751 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 649 |
| AS202315 | Arcus IT Managed Services B.V. | Unclassified | IPv4 IPv6 | 306 |
| AS198508 | Plusine Systems B.V. | Hosting | IPv4 IPv6 | 289 |
| AS6830 | Liberty Global Europe Holding B.V. | Residential | IPv4 | 194 |
| AS42152 | VCD Infra Solutions B.V. | Unclassified | IPv4 | 116 |
| AS48812 | Office IT B.V. | Unclassified | IPv4 | 116 |
| AS48501 | Init3 BV | Hosting | IPv4 IPv6 | 95 |
| AS215914 | NetGrid Holding B.V. | Unclassified | IPv4 | 84 |
| AS41037 | Meta Micro Automatisering B.V. | Hosting | IPv4 | 58 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.