asn.dev

Observed topology

AS63296 AWBROADBAND

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63296: 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 LLCTransitIPv4626
AS6461Zayo BandwidthTransitIPv4117
AS394177SHIFT HOSTING LLCHostingIPv491
AS14907Wikimedia Foundation Inc.HostingIPv413
AS19754The Fusion Network, LLCUnclassifiedIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397056AgWorks, LLCUnclassifiedIPv4183
AS399051ALLSTATE SECURITY INDUSTRIES, INC.UnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4841
AS397056AgWorks, LLCUnclassifiedIPv4183
AS6461Zayo BandwidthTransitIPv4117
AS394177SHIFT HOSTING LLCHostingIPv4115
AS399051ALLSTATE SECURITY INDUSTRIES, INC.UnclassifiedIPv465
AS14907Wikimedia Foundation Inc.HostingIPv417
AS19754The Fusion Network, LLCUnclassifiedIPv416

Provenance

Where this comes from

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