Yukari Networks: PeeringDB fix list
AS202396 · peeringdb.com/net/41305
2 things to fix in Yukari Networks's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Yukari Networks'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 33.0.0.41 - In the entry with IPv6 2a0f:7803:fc60:aaaa::2023:96: set IPv4 to 33.0.0.41 (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 IPv4 address missing from PeeringDB none 195.60.92.69 - In the entry with IPv6 2602:f93b:1a35:1311::69: set IPv4 to 195.60.92.69 (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/202396/: 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.