asn.dev

Observed topology

AS52075 WIFIRST Wifirst IP Network

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 39

Networks observed carrying traffic for AS52075: 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
AS2914NTT America, Inc.TransitIPv4 IPv6283
AS6939Hurricane Electric LLCTransitIPv4 IPv6276
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6165
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv670
AS50304Blix Solutions ASUnclassifiedIPv436
AS6461Zayo BandwidthTransitIPv432
AS1836green.ch AGResidentialIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv628
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv628
AS44530HOPUS SASUnclassifiedIPv4 IPv628

All 39 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210070Hotsplots GmbHUnclassifiedIPv4244

Adjacency

Adjacent networks

All 40

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6304
AS2914NTT America, Inc.TransitIPv4 IPv6287
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6251
AS210070Hotsplots GmbHUnclassifiedIPv4244
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv682
AS3320Deutsche Telekom AGMobileIPv4 IPv654
AS50304Blix Solutions ASUnclassifiedIPv436
AS1836green.ch AGResidentialIPv4 IPv632
AS6461Zayo BandwidthTransitIPv432
AS24482SG.GSHostingIPv4 IPv632

All 40 adjacent →

Provenance

Where this comes from

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