MYIP: PeeringDB fix list
AS215956 · peeringdb.com/net/34730
3 things to fix in MYIP's PeeringDB record, from what its exchanges publish: 2 to correct, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.
Make the changes on MYIP'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 (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 IPv4 address missing from PeeringDB none 80.249.215.87 - In the entry with IPv6 2001:7f8:1:0:a500:21:5956:1: set IPv4 to 80.249.215.87 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 2.5G 1G - In the entry with IPv6 2602:fed2:fff:ffff:6::f7: set Speed to 1000 (1G) (now 2500).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 – IPv6 2a14:7580:eff0:ab9e:0:21:5956:1 Speed 1000 Mbps (1G)
From ixreport.com/net/215956/: 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.