asn.dev

Observed topology

AS15290 ZAYO-CAN-15290

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15290: 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
AS6461Zayo BandwidthTransitIPv4 IPv65,326
AS577Bell CanadaMobileIPv4 IPv660

Transit

Downstream networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS11342Pathway CommunicationsUnclassifiedIPv4356
AS6401Zayo BandwidthUnclassifiedIPv4295
AS4470Citenet Telecom Inc.UnclassifiedIPv4229
AS32564Intact Financial CorporationUnclassifiedIPv4187
AS36698Fatbanana Broadband Inc.ResidentialIPv4156
AS17025Zayo BandwidthUnclassifiedIPv4118
AS54587SoftekUnclassifiedIPv4118
AS19005J2 Global Ventures, LLCUnclassifiedIPv4110
AS7734Toronto Dominion BankUnclassifiedIPv469
AS13729Fidessa CorporationUnclassifiedIPv459

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv67,437
AS11342Pathway CommunicationsUnclassifiedIPv4356
AS6401Zayo BandwidthUnclassifiedIPv4295
AS4470Citenet Telecom Inc.UnclassifiedIPv4229
AS32564Intact Financial CorporationUnclassifiedIPv4187
AS36698Fatbanana Broadband Inc.ResidentialIPv4156
AS17025Zayo BandwidthUnclassifiedIPv4118
AS54587SoftekUnclassifiedIPv4118
AS577Bell CanadaMobileIPv4 IPv6110
AS19005J2 Global Ventures, LLCUnclassifiedIPv4110

Provenance

Where this comes from

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