asn.dev

Observed topology

AS37904 BBIX-NETWORK BBIX, Inc.

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37904: 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
AS63927RISEResidentialIPv4 IPv6155
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS17676SoftBank Corp.MobileIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135607Infinivan IncorporatedResidentialIPv4100
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv695
AS20940Akamai International B.V.HostingIPv4 IPv695

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS63927RISEResidentialIPv4 IPv6447
AS135607Infinivan IncorporatedResidentialIPv4102
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv695
AS20940Akamai International B.V.HostingIPv4 IPv695
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS17676SoftBank Corp.MobileIPv41

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.