Eons Data: PeeringDB fix list
AS138997 · peeringdb.com/net/20145
3 things to fix in Eons Data's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Eons Data'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 Eons Data's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.80.238.36 IPv6 2001:504:91::36 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 × 600G 600G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Eons Data has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958Not on its website members listIPv4 185.0.43.112 IPv6 2001:7f8:115:1::1:112 Speed 40000 Mbps (40G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/138997/: 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.