ixreport

KeyArg

AS219411

Key Arg B.V.

1Exchange
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
SelectivePeering policy
1Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in KeyArg's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on KeyArg'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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1:0:a500:21:9411:1
    • In the entry with IPv4 80.249.214.64: set IPv6 to 2001:7f8:1:0:a500:21:9411:1 (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.

Exchanges over time

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

Map

Where KeyArg'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 10G across 1 exchange.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.214.64 10G 1 routes Both IPv6 not in PeeringDB

Exchanges in its buildings that it isn't on (6)

These exchanges have a switch in a facility where KeyArg lists itself in PeeringDB, but don't have KeyArg as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 NorthC Amsterdam 1
Netherlands Speed-IXDronten, Netherlands 289 NorthC Amsterdam 1
Netherlands ERA-IX AmsterdamAmsterdam, Netherlands 244 NorthC Amsterdam 1
Netherlands ixFabric - AmsterdamAmsterdam, Netherlands 181 NorthC Amsterdam 1
Netherlands Clue-IXAmsterdam, Netherlands 36 NorthC Amsterdam 1
Netherlands NSIX AmsterdamAmsterdam, Netherlands 13 NorthC Amsterdam 1
Facilities (1)

The buildings KeyArg lists in PeeringDB, and how many of the exchanges in each it's on.

Netherlands NorthC Amsterdam 1Amsterdam 1 of 7