asn.dev

Observed topology

AS1248 HERE

Unclassified RIPE Enterprise

Upstreams 29 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 30
Adjacent (IPv6) 0
Upstream graph Who carries AS1248, and who carries them, drawn as a map up to the transit-free core. 7 exchanges Where AS1248 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 29

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.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4283
AS6939Hurricane Electric LLCTransitIPv474
AS9957KINXHostingIPv462
AS4637Telstra GlobalUnclassifiedIPv436
AS34549meerfarbig GmbH & Co. KGHostingIPv418
AS50304Blix Solutions ASUnclassifiedIPv412
AS33891Core-Backbone GmbHHostingIPv48
AS293ESnetUnclassifiedIPv46
AS1836green.ch AGResidentialIPv46
AS3741Dimension DataUnclassifiedIPv46

Transit

Downstream networks

inferred

Networks for which AS1248 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS14803HERE North America LLCUnclassifiedIPv459

Adjacency

Adjacent networks

All 30

Every AS seen directly next to AS1248 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4310
AS6939Hurricane Electric LLCTransitIPv482
AS9957KINXHostingIPv462
AS14803HERE North America LLCUnclassifiedIPv459
AS4637Telstra GlobalUnclassifiedIPv436
AS34549meerfarbig GmbH & Co. KGHostingIPv421
AS50304Blix Solutions ASUnclassifiedIPv414
AS33891Core-Backbone GmbHHostingIPv410
AS293ESnetUnclassifiedIPv47
AS1836green.ch AGResidentialIPv47

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.