Observed topology
AS39923 AS-UNIXSOLUTIONS Unix-Solutions Network
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS39923: 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 |
|---|---|---|---|---|
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 IPv6 | 699 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 521 |
| AS13237 | euNetworks GmbH | Unclassified | IPv4 IPv6 | 498 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 429 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 43 |
| AS45049 | Mohamed El Bouddunti | Residential | IPv4 IPv6 | 42 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 35 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 21 |
| AS34019 | Hivane Association | Unclassified | IPv4 | 21 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 20 |
Transit
Downstream networks
Networks for which AS39923 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208792 | Core ICT N.V. | Unclassified | IPv4 | 170 |
| AS200882 | DC Innovations BV | Hosting | IPv4 IPv6 | 155 |
| AS39641 | WILLUX.be N.V. | Unclassified | IPv4 | 118 |
| AS210821 | Creasa VOF | Unclassified | IPv4 IPv6 | 92 |
| AS204120 | Colibri Consulting B.V.B.A. | Unclassified | IPv4 IPv6 | 88 |
| AS50906 | Luciad NV | Unclassified | IPv4 | 56 |
| AS50156 | Boxed IT Ltd. | Hosting | IPv4 IPv6 | 53 |
| AS208725 | Devrandom.be BV | Hosting | IPv4 IPv6 | 26 |
| AS58123 | NG Communications BV | Unclassified | IPv4 IPv6 | 17 |
| AS199670 | DNS-Belgium VZW | Unclassified | IPv4 IPv6 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39923 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 IPv6 | 1,059 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 800 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 518 |
| AS13237 | euNetworks GmbH | Unclassified | IPv4 IPv6 | 498 |
| AS208792 | Core ICT N.V. | Unclassified | IPv4 | 170 |
| AS200882 | DC Innovations BV | Hosting | IPv4 IPv6 | 155 |
| AS50156 | Boxed IT Ltd. | Hosting | IPv4 IPv6 | 129 |
| AS39641 | WILLUX.be N.V. | Unclassified | IPv4 | 118 |
| AS210821 | Creasa VOF | Unclassified | IPv4 IPv6 | 92 |
| AS204120 | Colibri Consulting B.V.B.A. | Unclassified | IPv4 IPv6 | 88 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.