iYoRoy-Network: PeeringDB fix list
AS205369 · peeringdb.com/net/40075
3 things to fix in iYoRoy-Network's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on iYoRoy-Network'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 (3)
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 33.0.0.86 - In the entry with IPv6 2a0f:7803:fc60:aaaa::2053:69: set IPv4 to 33.0.0.86 (now empty).
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.0.24.188 - In the entry with IPv6 2001:7f8:aa::188: set IPv4 to 185.0.24.188 (now empty).
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 23.154.164.153 - In the entry with IPv6 2602:f429:31::1a: set IPv4 to 23.154.164.153 (now empty).
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.
From ixreport.com/net/205369/: 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.