Plains Internet: PeeringDB fix list

AS393737 · peeringdb.com/net/18205

PeeringDB

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

Make the changes on Plains Internet'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 DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.53.202.134206.53.202.51 206.53.202.134
    IPv6 address missing from PeeringDBnone2001:504:61:0:6:209:0:1 2001:504:61:0:6:209:0:2
    Port speed differs10G2 × 10G
    • In the entry with IPv4 206.53.202.134: set IPv6 to 2001:504:61:0:6:209:0:1 (now empty).
    • Add an entry: IPv4 206.53.202.51, IPv6 2001:504:61:0:6:209:0:2, speed 10000 (10G), RS peer yes.

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