Kirino: PeeringDB fix list

AS41378 · peeringdb.com/net/19561

PeeringDB

2 things to fix in Kirino's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Kirino'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 GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

    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 Kirino 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 FL-IX Miami, United States · PeeringDB 954Not on its IX-F export or website members list
    IPv4206.41.108.212
    IPv62001:504:40:108::1:212
    Speed10000 Mbps (10G)

From ixreport.com/net/41378/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.