ixreport

AetherNet

AS215207

4Exchanges
4On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
3Using the route servers
4To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with AetherNet? · Where should AetherNet peer next? · Compare AetherNet with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in AetherNet's PeeringDB record, from what its exchanges publish: 4 to add. As of 2026-11-19 12:40 UTC.

Make the changes on AetherNet's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (4)

On the exchange's own member list, but not in AetherNet's PeeringDB record. Add one entry per connection with these values.

  1. United States F4IX MCI Kansas City, United States · PeeringDB 4378From its IX-F export
    IPv4–
    IPv62602:fa3d:f4:1::bf
    Speed100 Mbps (100M)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:ca:1:0:21:5207:1
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. Canada ONIX Toronto, Canada · PeeringDB 4059From its IX-F export and website members list
    IPv4–
    IPv62001:504:125:e1::bca
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  4. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4192.34.27.132
    IPv6–
    SpeedNot published
    RS peerNot published
    IPv4–
    IPv62602:ffb1:200:0:192:34:27:132
    SpeedNot published
    RS peerNot published

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20263
Oct 24, 20262
Oct 23, 20262
Oct 22, 20263
Oct 21, 20263
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where AetherNet's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 2.1G, at the 3 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United States F4IX MCI Kansas City, United States 2602:fa3d:f4:1::bf 100M Yes Not in PeeringDB
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1::21:5207:1 1G Yes Not in PeeringDB
Canada ONIX Toronto, Canada 2001:504:125:e1::bca 1G Yes Not in PeeringDB
Canada UNM-Exch Canada-West Vancouver, Canada 192.34.27.132 2602:ffb1:200:0:192:34:27:132 Not in PeeringDB

AetherNet lists no facilities in PeeringDB.