asn.dev

Observed topology

AS49375 AS-NOONEINTERNET No One Internet - www.noone.co.uk

Residential RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS49375: 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 IPv6307
AS51945ENLINK LTDUnclassifiedIPv4 IPv6271
AS6939Hurricane Electric LLCTransitIPv4 IPv6194
AS34549meerfarbig GmbH & Co. KGHostingIPv454
AS42708Glesys ABUnclassifiedIPv4 IPv619
AS50304Blix Solutions ASUnclassifiedIPv4 IPv619
AS3216PJSC "Vimpelcom"MobileIPv418
AS3741Dimension DataUnclassifiedIPv418
AS4657StarHub LtdResidentialIPv418
AS12552GlobalConnect ABUnclassifiedIPv418

All 19 upstreams →

Transit

Downstream networks

inferred

Networks for which AS49375 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 19

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6307
AS51945ENLINK LTDUnclassifiedIPv4 IPv6271
AS6939Hurricane Electric LLCTransitIPv4 IPv6194
AS34549meerfarbig GmbH & Co. KGHostingIPv454
AS42708Glesys ABUnclassifiedIPv4 IPv619
AS50304Blix Solutions ASUnclassifiedIPv4 IPv619
AS3216PJSC "Vimpelcom"MobileIPv418
AS3741Dimension DataUnclassifiedIPv418
AS4657StarHub LtdResidentialIPv418
AS12552GlobalConnect ABUnclassifiedIPv418

All 19 adjacent →

Provenance

Where this comes from

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