asn.dev

Observed topology

AS11670 Toronto Internet Exchange Community

Unclassified ARIN Route Server

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36750City of MississaugaUnclassifiedIPv4225
AS36445CoextroResidentialIPv420
AS3026577997 Newfoundland and Labrador Inc.ResidentialIPv43
AS399337Netcrawler IncUnclassifiedIPv43

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS15024Packetworks Inc.UnclassifiedIPv4225
AS36750City of MississaugaUnclassifiedIPv4225
AS400281651884 Ontario Inc.UnclassifiedIPv442
AS36445CoextroResidentialIPv420
AS3026577997 Newfoundland and Labrador Inc.ResidentialIPv410
AS53356Free Range Cloud Hosting Inc.HostingIPv45
AS21949Beanfield Technologies Inc.UnclassifiedIPv44
AS53486Niagara Regional Broadband Networks LimitedUnclassifiedIPv44
AS399337Netcrawler IncUnclassifiedIPv43
AS7992Cogeco Connexion Inc.ResidentialIPv42

All 11 adjacent →

Provenance

Where this comes from

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