Observed topology

AS26110 MHT-ASN - Manitoba Hydro International LTD

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26110: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	1,428
AS174	Cogent Communications, LLC	Transit	IPv4	288

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS394989	Gene's Telecom	Unclassified	IPv4	396
AS400078	Manitoba Liquor and Lotteries Corporation	Unclassified	IPv4	190
AS26320	MONARCH INDUSTRIES LIMITED	Unclassified	IPv4	66
AS395248	Loewen	Unclassified	IPv4	61
AS21671	Manitoba Hydro	Unclassified	IPv4	45

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	2,058
AS174	Cogent Communications, LLC	Transit	IPv4	416
AS394989	Gene's Telecom	Unclassified	IPv4	396
AS400078	Manitoba Liquor and Lotteries Corporation	Unclassified	IPv4	190
AS26320	MONARCH INDUSTRIES LIMITED	Unclassified	IPv4	66
AS395248	Loewen	Unclassified	IPv4	61
AS21671	Manitoba Hydro	Unclassified	IPv4	45

Provenance

Where this comes from

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