asn.dev

Observed topology

AS15221 STRATUSIQ

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15221: 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
AS7029Windstream Communications LLCResidentialIPv4 IPv6706
AS33302Data102HostingIPv4 IPv6287

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS7832PCI Fiber, LLCUnclassifiedIPv4325
AS26399Broadmoor Hotel IncUnclassifiedIPv4149
AS32142Academy School District 20UnclassifiedIPv4126
AS398996California Casualty Management CompanyUnclassifiedIPv484
AS31756City of Colorado SpringsUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS33302Data102HostingIPv4 IPv61,012
AS7029Windstream Communications LLCResidentialIPv4 IPv6706
AS7832PCI Fiber, LLCUnclassifiedIPv4325
AS26399Broadmoor Hotel IncUnclassifiedIPv4149
AS32142Academy School District 20UnclassifiedIPv4126
AS398996California Casualty Management CompanyUnclassifiedIPv484
AS31756City of Colorado SpringsUnclassifiedIPv465
AS6461Zayo BandwidthTransitIPv424

Provenance

Where this comes from

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