asn.dev

Observed topology

AS59437 NORTHERNDATA

Unclassified RIPE

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS59437: 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 ABTransitIPv4 IPv6498
AS6939Hurricane Electric LLCTransitIPv4 IPv6377
AS33891Core-Backbone GmbHHostingIPv4 IPv6333
AS212175Stelia LtdUnclassifiedIPv4 IPv6225
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6137
AS2116GLOBALCONNECT ASResidentialIPv4 IPv6124
AS3257GTT Communications Inc.TransitIPv4 IPv684
AS6461Zayo BandwidthTransitIPv4 IPv671
AS1257Tele2 Sverige ABMobileIPv430
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv626

All 22 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6498
AS6939Hurricane Electric LLCTransitIPv4 IPv6377
AS33891Core-Backbone GmbHHostingIPv4 IPv6337
AS212175Stelia LtdUnclassifiedIPv4 IPv6225
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6137
AS2116GLOBALCONNECT ASResidentialIPv4 IPv6124
AS3257GTT Communications Inc.TransitIPv4 IPv684
AS6461Zayo BandwidthTransitIPv4 IPv671
AS1257Tele2 Sverige ABMobileIPv430
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv626

All 23 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.