Expedient: PeeringDB fix list
AS17054 · peeringdb.com/net/6166
3 things to fix in Expedient's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Expedient'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 Expedient's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.53.143.8 IPv6 – Speed 10000 Mbps (10G) RS peer No
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 Address belongs to another network in PeeringDB 206.53.143.8 is AS3 Massachusetts Institute of Technology 206.53.143.8 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:504:77::12 - In the entry with IPv4 206.71.141.12: set IPv6 to 2001:504:77::12 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/17054/: 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.