asn.dev

Observed topology

AS7752 THRES

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS7752: 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
AS6461Zayo BandwidthTransitIPv4 IPv695
AS6939Hurricane Electric LLCTransitIPv4 IPv657
AS2914NTT America, Inc.TransitIPv4 IPv654
AS20055Wholesail networks LLCResidentialIPv432
AS9002RETN LimitedUnclassifiedIPv48
AS852TELUS Communications Inc.ResidentialIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS3130RGnet OUUnclassifiedIPv44
AS7575Australian Academic and Research Network (AARNet)EducationIPv44

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63479HamWANUnclassifiedIPv4168

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6213
AS63479HamWANUnclassifiedIPv4176
AS2914NTT America, Inc.TransitIPv4 IPv6102
AS6939Hurricane Electric LLCTransitIPv4 IPv657
AS20055Wholesail networks LLCResidentialIPv432
AS852TELUS Communications Inc.ResidentialIPv4 IPv614
AS9002RETN LimitedUnclassifiedIPv48
AS24482SG.GSHostingIPv4 IPv66
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS3130RGnet OUUnclassifiedIPv44

All 12 adjacent →

Provenance

Where this comes from

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