Automattic: PeeringDB fix list
AS2635 · peeringdb.com/net/6460
5 things to fix in Automattic's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on Automattic'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 (2)
On the exchange's own member list, but not in Automattic's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.69.119.63 IPv6 2001:7f8:d:fb::63 Speed Not published RS peer Yes -
IPv4 195.245.240.63 IPv6 2001:7f8:d:fc::63 Speed Not published RS peer Yes
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.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 149.112.11.65: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G 10G - In the entry with IPv4 217.29.67.20: set Speed to 10000 (10G) (now 20000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Automattic has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.41.110.82 IPv6 2001:504:41:110::82 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/2635/: 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.