asn.dev

Observed topology

AS200675 HYDRO66 NORTHERN DATA SERVICES (UK) LIMITED

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200675: 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
AS12552GlobalConnect ABUnclassifiedIPv4 IPv675
AS1299Arelion Sweden ABTransitIPv4 IPv661
AS6939Hurricane Electric LLCTransitIPv4 IPv631
AS1257Tele2 Sverige ABMobileIPv4 IPv625
AS50304Blix Solutions ASUnclassifiedIPv46
AS24482SG.GSHostingIPv4 IPv64
AS20764CJSC RASCOMUnclassifiedIPv43
AS20473The Constant Company, LLCHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59437Northern Data AGUnclassifiedIPv62
AS207470The Production Office in Stockholm ABUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12552GlobalConnect ABUnclassifiedIPv4 IPv676
AS1299Arelion Sweden ABTransitIPv4 IPv662
AS6939Hurricane Electric LLCTransitIPv4 IPv631
AS1257Tele2 Sverige ABMobileIPv4 IPv625
AS50304Blix Solutions ASUnclassifiedIPv46
AS24482SG.GSHostingIPv4 IPv64
AS20764CJSC RASCOMUnclassifiedIPv43
AS20473The Constant Company, LLCHostingIPv62
AS59437Northern Data AGUnclassifiedIPv62
AS207470The Production Office in Stockholm ABUnclassifiedIPv41

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.