NAVER: PeeringDB fix list
AS23576 · peeringdb.com/net/5282
4 things to fix in NAVER's PeeringDB record, from what its exchanges publish: 3 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on NAVER'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 IPv6 address missing from PeeringDB none 2001:7f8:1::a502:3576:1 Port speed differs 10G 2G - In the entry with IPv4 80.249.211.220: set IPv6 to 2001:7f8:1::a502:3576:1 (now empty); set Speed to 2000 (2G) (now 10000).
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 IPv6 address missing from PeeringDB none 2001:7f8::5c18:0:1 - In the entry with IPv4 80.81.193.48: set IPv6 to 2001:7f8::5c18:0:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4::5c18:1 - In the entry with IPv4 195.66.226.173: set IPv6 to 2001:7f8:4::5c18:1 (now empty).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If NAVER has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 210.173.177.130 IPv6 – Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/23576/: 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.