Observed topology
AS39040 NTSWORKSPACEAG-AS39040
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS39040: 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 AS39040 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203434 | Open Circle AG | Unclassified | IPv4 IPv6 | 198 |
| AS210861 | Open Networks Association | Unclassified | IPv4 IPv6 | 99 |
| AS25353 | BAR Informatik AG | Unclassified | IPv4 IPv6 | 77 |
| AS206616 | wwcom AG | Unclassified | IPv4 | 74 |
| AS204178 | Winet Voicetec Solutions AG | Unclassified | IPv4 | 59 |
| AS15716 | Adfinis AG | Hosting | IPv4 IPv6 | 58 |
| AS44879 | Zentrale Informatikdienste ZID Kanton Basel-Landschaft | Unclassified | IPv4 | 57 |
| AS25563 | Multimedia Networks AG | Hosting | IPv4 IPv6 | 56 |
| AS198951 | BLS AG | Unclassified | IPv4 IPv6 | 56 |
| AS39265 | Stadtverwaltung der Stadt Bern | Unclassified | IPv4 IPv6 | 39 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39040 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29075 | IELO-LIAZO SERVICES SAS | Unclassified | IPv4 IPv6 | 636 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 554 |
| AS203434 | Open Circle AG | Unclassified | IPv4 IPv6 | 198 |
| AS51907 | Kanton Zug | Unclassified | IPv4 IPv6 | 156 |
| AS210861 | Open Networks Association | Unclassified | IPv4 IPv6 | 99 |
| AS25353 | BAR Informatik AG | Unclassified | IPv4 IPv6 | 77 |
| AS206616 | wwcom AG | Unclassified | IPv4 | 74 |
| AS204178 | Winet Voicetec Solutions AG | Unclassified | IPv4 | 59 |
| AS15716 | Adfinis AG | Hosting | IPv4 IPv6 | 58 |
| AS44879 | Zentrale Informatikdienste ZID Kanton Basel-Landschaft | Unclassified | IPv4 | 57 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.