Observed topology
AS1248 HERE
Unclassified RIPE Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS1248: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 283 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 74 |
| AS9957 | KINX | Hosting | IPv4 | 62 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 36 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 18 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 12 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 8 |
| AS293 | ESnet | Unclassified | IPv4 | 6 |
| AS1836 | green.ch AG | Residential | IPv4 | 6 |
| AS3741 | Dimension Data | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS1248 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14803 | HERE North America LLC | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS1248 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 310 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 82 |
| AS9957 | KINX | Hosting | IPv4 | 62 |
| AS14803 | HERE North America LLC | Unclassified | IPv4 | 59 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 36 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 21 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 14 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 10 |
| AS293 | ESnet | Unclassified | IPv4 | 7 |
| AS1836 | green.ch AG | Residential | IPv4 | 7 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.