Observed topology
AS39563 UCSYSTEMS CTA Systems B.V.
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS39563: 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 |
|---|---|---|---|---|
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 129 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 125 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 81 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 56 |
| AS43350 | NForce Entertainment B.V. | Unclassified | IPv4 IPv6 | 40 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv4 IPv6 | 10 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 10 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 10 |
Transit
Downstream networks
Networks for which AS39563 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35055 | Connect B.V. | Unclassified | IPv4 IPv6 | 50 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39563 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 129 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 125 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 81 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 75 |
| AS43350 | NForce Entertainment B.V. | Unclassified | IPv4 IPv6 | 63 |
| AS35055 | Connect B.V. | Unclassified | IPv4 IPv6 | 50 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv4 IPv6 | 14 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 14 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.