BGP.Exchange - Toronto

Canada

City
Toronto

About this IXP

Data last updated July 2026

Capacity at this IXP

4 Gbps

Cumulative port speeds of all IXP members. This shows the potential maximum traffic that can be exchanged at this IXP at one time.

Membership and capacity

The size and strength of an IXP is determined by a combination of how many members it has, and the total capacity. Larger networks tend to bring more capacity, which can benefit all members.

Data for BGP.Exchange - Toronto as shown in PeeringDB in July 2026

Members of this IXP

4

ASNs (autonomous system numbers) are listed in PeeringDB

In the last 12 months

  • ASNs left4
  • New ASNs joined3

Participates in the MANRS IXP program

No

IXPs that join this voluntary program apply a framework of enhanced routing security in peering. It signals an extra commitment to responsible Internet stewardship.

Source: MANRS

RIPE Atlas anchor

No

Organizations that run IXPs can host anchors to measure Internet connectivity and traffic. An anchor is a large capacity probe often used by IXPs.

Source: RIPEStat

Member information

Last sync from PeeringDB: July 2026

View this IXP on PeeringDB

Countries of registration

A summary of member registrations by country. An IXP with a mixture of international and near-neighbor members can indicate that an IXP is influential, or acts as a hub within its region or sub-region.

  • Canada: 2
  • United States of America: 1
  • South Africa: 1

Types of network at this IXP

The mix of members is an indication of a strength or focus of an IXP.

  • Content: 1
  • Educational/Research: 1
  • Network Services: 1
  • Non-Profit: 1

Members peering at the route server

4 / 4

The route server is a central hub that makes it easier for all networks to peer without having to create individual agreements with other members.

Members using RPKI

4 / 4

members at this IXP use Resource Public Key Infrastructure (RPKI), a security measure that helps ensure traffic is routed correctly. A member is counted as using RPKI if they have at least one valid ROA.

Peering policies of IXP members

Members of an IXP can choose how they peer with others. The Internet Society encourages open policies where possible.

Member list for BGP.Exchange - Toronto

This list uses the data available in PeeringDB, which is based on self-reported data, and was last updated in Pulse July 2026

Name AS Number Peering policy RPKI Enabled
Computer Power
  • Autonomous system (AS) number: 213975
  • Type of AS: Non-Profit
  • Peering policy: Open
  • Port speed: 1 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: South Africa
  • Total peering locations for this AS: 6
213975 Open Yes
ECCN
  • Autonomous system (AS) number: 211548
  • Type of AS: Network Services
  • Peering policy: Open
  • Port speed: 1 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Canada
  • Total peering locations for this AS: 3
211548 Open Yes
STiBaRC
  • Autonomous system (AS) number: 26533
  • Type of AS: Content
  • Peering policy: Open
  • Port speed: 1 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: United States of America
  • Total peering locations for this AS: 5
26533 Open Yes
ZZNYJIDI
  • Autonomous system (AS) number: 402104
  • Type of AS: Educational/Research
  • Peering policy: Open
  • Port speed: 1 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Canada
  • Total peering locations for this AS: 3
402104 Open Yes