asn.dev

Observed topology

AS26806 SRNET-SASKATCHEWAN-RESEARCH-NETWORK

Unclassified ARIN Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26806: 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 LLCTransitIPv4213
AS6509CANARIE IncEducationIPv4 IPv661
AS6327Shaw CommunicationsResidentialIPv433

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27628Innovation SaskatchewanUnclassifiedIPv4830
AS22950University of SaskatchewanUnclassifiedIPv4 IPv6821
AS35857Saskatchewan PolytechnicUnclassifiedIPv4340
AS393607Innovation SaskatchewanUnclassifiedIPv4265
AS399844Saskatchewan TelecommunicationsUnclassifiedIPv4203
AS26206University of ReginaUnclassifiedIPv4 IPv6160

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,221
AS22950University of SaskatchewanUnclassifiedIPv4 IPv6878
AS27628Innovation SaskatchewanUnclassifiedIPv4830
AS6509CANARIE IncEducationIPv4 IPv6502
AS35857Saskatchewan PolytechnicUnclassifiedIPv4340
AS393607Innovation SaskatchewanUnclassifiedIPv4265
AS6327Shaw CommunicationsResidentialIPv4 IPv6260
AS399844Saskatchewan TelecommunicationsUnclassifiedIPv4203
AS26206University of ReginaUnclassifiedIPv4 IPv6160

Provenance

Where this comes from

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