TWDX IP: PeeringDB fix list
AS27552 · peeringdb.com/net/629
2 things to fix in TWDX IP's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on TWDX IP'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 TWDX IP's PeeringDB record. Add one entry per connection with these values.
-
Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204From its website members listIPv4 206.51.40.21 IPv6 2001:504:13:1::21 Speed Not published RS peer Not published
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.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 100G + 20G - In the entry with IPv4 206.53.143.35: set Speed to 20000 (20G) (now 100000).
From ixreport.com/net/27552/: 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.