Observed topology
AS9158 TELENOR_DANMARK_AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS9158: 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 | 674 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 474 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 52 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 28 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 28 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 27 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 27 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 27 |
| AS37721 | Virtual-Technologies-Solutions-SA | Residential | IPv4 IPv6 | 27 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 27 |
Transit
Downstream networks
Networks for which AS9158 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203644 | EG Danmark A/S | Unclassified | IPv4 | 232 |
| AS205116 | KRISTELIG FAGFORENING | Unclassified | IPv4 | 58 |
| AS209118 | Helsingoer Kommune | Unclassified | IPv4 | 58 |
| AS211676 | IKAST BETONVAREFABRIK A/S | Unclassified | IPv4 | 54 |
| AS51073 | Aarhus Business College | Unclassified | IPv4 | 27 |
| AS57720 | Wrist Ship Supply A/S | Unclassified | IPv4 | 7 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9158 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 845 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 608 |
| AS203644 | EG Danmark A/S | Unclassified | IPv4 | 232 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 68 |
| AS205116 | KRISTELIG FAGFORENING | Unclassified | IPv4 | 58 |
| AS209118 | Helsingoer Kommune | Unclassified | IPv4 | 58 |
| AS211676 | IKAST BETONVAREFABRIK A/S | Unclassified | IPv4 | 54 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 37 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 36 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 36 |
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.