Observed topology

AS10965 MRNET

Education ARIN

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

Upstream graph Who carries AS10965, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS10965 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10965: 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.

AS	Network	Type	Families	Paths seen
AS17001	University of Manitoba	Unclassified	IPv4	108
AS6509	CANARIE Inc	Education	IPv4	21

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS16796	MERLIN	Unclassified	IPv4	287
AS22686	University of Winnipeg	Unclassified	IPv4 IPv6	44
AS17001	University of Manitoba	Unclassified	IPv4	23
AS18472	Canadian Museum for Human Rights	Unclassified	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6509	CANARIE Inc	Education	IPv4 IPv6	408
AS16796	MERLIN	Unclassified	IPv4	315
AS17001	University of Manitoba	Unclassified	IPv4	131
AS22686	University of Winnipeg	Unclassified	IPv4 IPv6	44
AS18472	Canadian Museum for Human Rights	Unclassified	IPv4	5

Provenance

Where this comes from

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