Observed topology

AS35911 BNQ-1 - Telebec

Unclassified ARIN

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35911: 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
AS577	Bell Canada	Mobile	IPv4 IPv6	6,421

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS25636	NorthernTel Limited Partnership	Unclassified	IPv4	352
AS63019	Parolink.net	Unclassified	IPv4 IPv6	149
AS22867	Hearst Connect Corporation	Unclassified	IPv4	116
AS32315	The Western James Bay Telecom Network	Unclassified	IPv4	116
AS398259	Cochrane Telecom Services	Unclassified	IPv4	116
AS32817	Northern College of Applied Arts & Technology	Unclassified	IPv4	20

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS577	Bell Canada	Mobile	IPv4 IPv6	7,290
AS25636	NorthernTel Limited Partnership	Unclassified	IPv4	352
AS63019	Parolink.net	Unclassified	IPv4 IPv6	149
AS22867	Hearst Connect Corporation	Unclassified	IPv4	116
AS32315	The Western James Bay Telecom Network	Unclassified	IPv4	116
AS398259	Cochrane Telecom Services	Unclassified	IPv4	116
AS32817	Northern College of Applied Arts & Technology	Unclassified	IPv4	20

Provenance

Where this comes from

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