asn.dev

Observed topology

AS15191 WIN-NET

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15191: 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
AS2914NTT America, Inc.TransitIPv4 IPv6274
AS11404Wave BroadbandResidentialIPv4 IPv6157
AS7385Allstream Business US, LLCUnclassifiedIPv4 IPv6131

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33509Cascade Access, LLCUnclassifiedIPv4 IPv6801
AS54523WSTCUnclassifiedIPv4295
AS53823Scio Mutual Telephone AssociationUnclassifiedIPv4118
AS393626Sherwood BroadbandResidentialIPv445
AS55122Digital Communications Consulting LLCUnclassifiedIPv436
AS33470Canby Telephone AssociationResidentialIPv4 IPv626
AS395808Jet Communications, LLCUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6927
AS33509Cascade Access, LLCUnclassifiedIPv4 IPv6801
AS11404Wave BroadbandResidentialIPv4 IPv6592
AS7385Allstream Business US, LLCUnclassifiedIPv4 IPv6382
AS54523WSTCUnclassifiedIPv4295
AS53823Scio Mutual Telephone AssociationUnclassifiedIPv4118
AS393626Sherwood BroadbandResidentialIPv445
AS55122Digital Communications Consulting LLCUnclassifiedIPv436
AS33470Canby Telephone AssociationResidentialIPv4 IPv628
AS395808Jet Communications, LLCUnclassifiedIPv42

Provenance

Where this comes from

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