ixreport

flew2

AS208884

5Exchanges, of which 2 VIX
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
5Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

2 things to fix in flew2's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-11-19 18:41 UTC.

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

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone193.189.83.140
    • In the entry with IPv6 2001:7f8:33::a120:8884:1: set IPv4 to 193.189.83.140 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If flew2 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States KCIX Kansas City, United States · PeeringDB 249Not on its IX-F export or website members list
    IPv4–
    IPv62001:504:1b:1::65
    Speed1000 Mbps (1G)

Exchanges over time

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

Map

Where flew2'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 4.1G across 5 exchanges.

Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1:0:20:8884:1 1G Yes Both
United States ixFabric - ChicagoVIX Chicago, United States 2a0e:8f01:1000:82::11e 1G Yes PeeringDB
Japan ixFabric - TokyoVIX Tokyo, Japan 2a0e:8f01:1000:9::11d 1G Yes PeeringDB
United States KCIX Kansas City, United States 2001:504:1b:1::65 1G Yes PeeringDB only
Germany KleyReX Frankfurt, Germany 2001:7f8:33::a120:8884:1 100M Yes Both IPv4 not in PeeringDB

flew2 lists no facilities in PeeringDB.