asn.dev

Observed topology

AS7530 BBTOWER-LAB BroadBand Tower, Inc.

Hosting ARIN Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7530: 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
AS9607BroadBand Tower, Inc.HostingIPv4 IPv6126
AS6939Hurricane Electric LLCTransitIPv429
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43
AS24482SG.GSHostingIPv43
AS9002RETN LimitedUnclassifiedIPv42
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150363SoftEther CorporationResidentialIPv433

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9607BroadBand Tower, Inc.HostingIPv4 IPv6183
AS150363SoftEther CorporationResidentialIPv444
AS6939Hurricane Electric LLCTransitIPv429
AS2500WIDE ProjectUnclassifiedIPv613
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43
AS24482SG.GSHostingIPv43
AS9002RETN LimitedUnclassifiedIPv42
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv41

Provenance

Where this comes from

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