NYI: PeeringDB fix list

AS11403 · peeringdb.com/net/2233

PeeringDB

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

Make the changes on NYI'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 (1)

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

  1. United States MegaIX New York New York, United States · PeeringDB 4318From its IX-F export
    IPv4206.53.173.16
    IPv62606:a980:0:2::10
    SpeedNot published
    RS peerNo

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

Correct these entries (2)

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. United States DE-CIX Chicago Chicago, United States · PeeringDB 3378
    ProblemPeeringDB hasThe export has
    Port speed differs10G40G
    • In the entry with IPv4 149.112.11.1: set Speed to 40000 (40G) (now 10000).
  2. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs10G40G
    • In the entry with IPv4 206.82.104.20: set Speed to 40000 (40G) (now 10000).

From ixreport.com/net/11403/: 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.