Wyyerd Group: PeeringDB fix list

AS54936 · peeringdb.com/net/32027

PeeringDB

One thing to fix in Wyyerd Group's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Wyyerd Group'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. United States Ninja-IX Phoenix Phoenix, United States · PeeringDB 662
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:3b::40
    • In the entry with IPv4 206.41.105.40: set IPv6 to 2001:504:3b::40 (now empty).

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