Observed topology
AS2119 TELENOR-NORGE-AS Telenor Norge AS
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS2119: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,244 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 876 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 850 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 307 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 235 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 109 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 109 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 109 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 108 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 108 |
Transit
Downstream networks
Networks for which AS2119 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5619 | Tieto Norway AS | Unclassified | IPv4 IPv6 | 928 |
| AS43905 | SPACE NORWAY SATCOM AS | Unclassified | IPv4 | 872 |
| AS61275 | NEAS ENERGI TELEKOM AS | Unclassified | IPv4 IPv6 | 757 |
| AS21293 | Norsk Rikskringkasting AS | Unclassified | IPv4 IPv6 | 543 |
| AS200168 | Telenor Norge AS | Unclassified | IPv4 IPv6 | 422 |
| AS41729 | Atea AS | Unclassified | IPv4 IPv6 | 418 |
| AS199791 | Embriq AS | Unclassified | IPv4 IPv6 | 326 |
| AS203424 | TUSSA IKT AS | Unclassified | IPv4 IPv6 | 323 |
| AS44381 | ITsjefen AS | Unclassified | IPv4 IPv6 | 308 |
| AS206993 | A ENERGI AS | Unclassified | IPv4 | 308 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2119 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,132 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,111 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,537 |
| AS5619 | Tieto Norway AS | Unclassified | IPv4 IPv6 | 1,262 |
| AS203779 | NORDFIBER AS | Residential | IPv4 IPv6 | 1,227 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,158 |
| AS44381 | ITsjefen AS | Unclassified | IPv4 IPv6 | 1,097 |
| AS43905 | SPACE NORWAY SATCOM AS | Unclassified | IPv4 | 988 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 862 |
| AS61275 | NEAS ENERGI TELEKOM AS | Unclassified | IPv4 IPv6 | 798 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.