NAVER
AS23576 · Naver Cloud Corp.
NAVER BUSINESS PLATFORM ASIA PACIFIC PTE LTD
Tools: Where can I peer with NAVER? · Where should NAVER peer next? · Compare NAVER with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in NAVER's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 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).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 10 |
| Nov 18, 2026 | 10 |
| Nov 17, 2026 | 10 |
| Nov 16, 2026 | 10 |
| Nov 15, 2026 | 10 |
| Nov 14, 2026 | 10 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 10 |
| Nov 8, 2026 | 10 |
| Nov 7, 2026 | 10 |
| Nov 6, 2026 | 10 |
| Nov 5, 2026 | 10 |
| Nov 4, 2026 | 10 |
| Nov 3, 2026 | 10 |
| Nov 2, 2026 | 10 |
| Nov 1, 2026 | 10 |
| Oct 31, 2026 | 10 |
| Oct 30, 2026 | 10 |
| Oct 29, 2026 | 10 |
| Oct 28, 2026 | 10 |
| Oct 27, 2026 | 10 |
| Oct 26, 2026 | 10 |
| Oct 25, 2026 | 10 |
| Oct 24, 2026 | 10 |
| Oct 23, 2026 | 10 |
| Oct 22, 2026 | 10 |
| Oct 21, 2026 | 10 |
| Oct 20, 2026 | 10 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 10 |
| Oct 3, 2026 | 10 |
Map
Where NAVER's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| AMS-IX Amsterdam, Netherlands | 10G | Both IPv6 not in PeeringDBSpeed differs | |
| BBIX Tokyo Tokyo, Japan | 100G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both IPv6 not in PeeringDB | |
| Equinix San Jose San Jose, United States | 10G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 2 × 100G | PeeringDB | |
| JPNAP Tokyo Tokyo, Japan | 100G | PeeringDB | |
| KINX Seoul, South Korea | 2 × 100G | PeeringDB | |
| KRIX(SEJONG) Seoul, South Korea | 2 × 20G | PeeringDB | |
| LINX LON1 London, United Kingdom | 10G | Both IPv6 not in PeeringDB | |
| NYIIX New York New York, United States | 10G | PeeringDB |
These exchanges have a switch in a facility where NAVER lists itself in PeeringDB, but don't have NAVER as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| DE-CIX New YorkNew York, United States | 281 | |
| SGIXSingapore, Singapore | 277 | |
| JPIX TOKYOTokyo, Japan | 275 | |
| NetIXSofia, Bulgaria | 204 | |
| BBIX SingaporeSingapore, Singapore | 169 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| Equinix TokyoTokyo, Japan | 127 | |
| SFMIXSan Francisco, United States | 100 | |
| BBIX US-WestWest Coast, United States | 87 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| Equinix Palo AltoPalo Alto, United States | 69 | |
| Digital Realty New YorkNew York/New Jersey, United States | 53 | |
| MegaIX SingaporeSingapore, Singapore | 46 | |
| Japan Community IXJapan, Japan | 32 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX New YorkNew York, United States | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| Japan Community IX - INIXPJapan, Japan | 15 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (6)
The buildings NAVER lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix FR4 - Frankfurt, WestFrankfurt | 1 of 9 | |
| Equinix SV1/SV5/SV10 - Silicon Valley, San JoseSan Jose | 1 of 8 | |
| Equinix SG3 - SingaporeSingapore | 1 of 7 | |
| AT TOKYO (CC1/CC2)Tokyo | 2 of 6 | |
| Digital Realty NYC (111 8th Ave)New York | 1 of 6 | |
| Equinix TY2 - TokyoTokyo | 2 of 6 |