asn.dev

Observed topology

AS17306 RISE-BROADBAND - JAB Wireless, INC.

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17306: 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
AS6939Hurricane Electric LLCTransitIPv45,120
AS6461Zayo BandwidthTransitIPv4 IPv63,310
AS174Cogent Communications, LLCTransitIPv42,755
AS293ESnetUnclassifiedIPv499
AS14907Wikimedia Foundation Inc.HostingIPv457
AS24482SG.GSHostingIPv442
AS11164Internet2EducationIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40744Coors Distributing CompanyUnclassifiedIPv427
AS19191JAB Wireless, INC.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv45,147
AS6461Zayo BandwidthTransitIPv4 IPv63,310
AS174Cogent Communications, LLCTransitIPv42,756
AS293ESnetUnclassifiedIPv499
AS14907Wikimedia Foundation Inc.HostingIPv457
AS24482SG.GSHostingIPv442
AS40744Coors Distributing CompanyUnclassifiedIPv427
AS11164Internet2EducationIPv41
AS19191JAB Wireless, INC.UnclassifiedIPv41

Provenance

Where this comes from

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