asn.dev

Observed topology

AS23316 BAI-IP-SERVICES - Bel Air Internet, LLC

Residential ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS23316: 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 IPv61,035
AS20055Wholesail networks LLCResidentialIPv4582
AS2914NTT America, Inc.TransitIPv4 IPv6548
AS6939Hurricane Electric LLCTransitIPv4451
AS174Cogent Communications, LLCTransitIPv4232
AS11404Wave BroadbandResidentialIPv4159
AS3257GTT Communications Inc.TransitIPv464
AS4455IX Reach LtdUnclassifiedIPv437
AS7575Australian Academic and Research Network (AARNet)EducationIPv434
AS17639Converge ICT Solutions Inc.UnclassifiedIPv434

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6551America ISPUnclassifiedIPv458
AS17210Everywhere Wireless, LLCResidentialIPv41

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,065
AS20055Wholesail networks LLCResidentialIPv4582
AS2914NTT America, Inc.TransitIPv4 IPv6564
AS6939Hurricane Electric LLCTransitIPv4460
AS174Cogent Communications, LLCTransitIPv4233
AS11404Wave BroadbandResidentialIPv4159
AS3257GTT Communications Inc.TransitIPv464
AS6551America ISPUnclassifiedIPv458
AS4455IX Reach LtdUnclassifiedIPv437
AS7575Australian Academic and Research Network (AARNet)EducationIPv435

All 14 adjacent →

Provenance

Where this comes from

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