RIPE NCC K-Root Operations
AS25152 · K-root, k.root-servers.net
RIPE NCC
Tools: Where can I peer with RIPE NCC K-Root Operations? · Where should RIPE NCC K-Root Operations peer next? · Compare RIPE NCC K-Root Operations with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
15 things to fix in RIPE NCC K-Root Operations's PeeringDB record, from what its exchanges publish: 8 to add, 7 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on RIPE NCC K-Root Operations's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (8)
On the exchange's own member list, but not in RIPE NCC K-Root Operations's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.27.170.75 IPv6 2401:7500:fff6::122 Speed 1000 Mbps (1G) RS peer Yes -
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 206.71.8.19 IPv6 2001:504:68::19 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 206.80.232.19 IPv6 2001:504:67::19 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 45.68.40.146 IPv6 2801:1f5::146 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (7)
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 Port speed differs 1G 10G - In the entry with IPv4 193.178.185.126: set Speed to 10000 (10G) (now 1000).
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 1G 10G - In the entry with IPv4 198.179.18.137: set Speed to 10000 (10G) (now 1000).
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 differs 2001:504:44::2:5152:1 2001:504:44::6240:0:1 - In the entry with IPv4 206.53.137.20: set IPv6 to 2001:504:44::6240:0:1 (now 2001:504:44::2:5152:1).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 103.142.153.17: set Speed to 10000 (10G) (now 1000).
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 1G 10G - In the entry with IPv4 196.60.96.44: set Speed to 10000 (10G) (now 1000).
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 1G 10G - In the entry with IPv4 217.29.66.8: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 196.60.9.80: set Speed to 10000 (10G) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 76 |
| Nov 18, 2026 | 76 |
| Nov 17, 2026 | 76 |
| Nov 16, 2026 | 76 |
| Nov 15, 2026 | 76 |
| Nov 14, 2026 | 76 |
| Nov 13, 2026 | 76 |
| Nov 12, 2026 | 76 |
| Nov 11, 2026 | 76 |
| Nov 10, 2026 | 77 |
| Nov 9, 2026 | 77 |
| Nov 8, 2026 | 77 |
| Nov 7, 2026 | 77 |
| Nov 6, 2026 | 77 |
| Nov 5, 2026 | 77 |
| Nov 4, 2026 | 77 |
| Nov 3, 2026 | 77 |
| Nov 2, 2026 | 77 |
| Nov 1, 2026 | 77 |
| Oct 31, 2026 | 77 |
| Oct 30, 2026 | 77 |
| Oct 29, 2026 | 77 |
| Oct 28, 2026 | 77 |
| Oct 27, 2026 | 77 |
| Oct 26, 2026 | 77 |
| Oct 25, 2026 | 76 |
| Oct 24, 2026 | 76 |
| Oct 23, 2026 | 76 |
| Oct 22, 2026 | 76 |
| Oct 21, 2026 | 76 |
| Oct 20, 2026 | 76 |
| Oct 19, 2026 | 76 |
| Oct 18, 2026 | 76 |
| Oct 17, 2026 | 76 |
| Oct 16, 2026 | 76 |
| Oct 15, 2026 | 76 |
| Oct 14, 2026 | 76 |
| Oct 13, 2026 | 76 |
| Oct 12, 2026 | 76 |
| Oct 11, 2026 | 76 |
| Oct 10, 2026 | 76 |
| Oct 9, 2026 | 76 |
| Oct 8, 2026 | 76 |
| Oct 7, 2026 | 76 |
| Oct 6, 2026 | 76 |
| Oct 5, 2026 | 76 |
| Oct 4, 2026 | 76 |
| Oct 3, 2026 | 76 |
Map
Where RIPE NCC K-Root Operations'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.
| AIX Tapos, Depok, Indonesia | 1G | Both | |
| AMS-IX Amsterdam, Netherlands | 10G | Both | |
| BCIX Berlin, Germany | 1G | Both Speed differs | |
| BHNIX Sarajevo, Bosnia and Herzegovina | 1G | Both | |
| BKNIX (Thailand) Bangkok, Thailand | 1G | Both | |
| btIX Thimphu, Bhutan | 1G | Both | |
| CANIX Montreal Montreal, Canada | 1G | Both Speed differs | |
| Central Oregon Internet Exchange Bend, United States | 1G | Both | |
| CitraIX Yogyakarta Yogyakarta, Indonesia | 1G | Both | |
| CIXP Geneva, Switzerland | 1G | Both | |
| CSIX Vancouver, Canada | 10G | PeeringDB | |
| CXC Denpasar Denpasar, Indonesia | 1G | PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both | |
| DE-CIX Mumbai Mumbai, India | 1G | Not in PeeringDB | |
| DE-CIX Richmond Ashland, United States | 1G | Both IPv6 differs | |
| DIX-IE Tokyo, Japan | 1G | PeeringDB | |
| Equinix Miami Miami, United States | 1G | PeeringDB | |
| ESpanix Madrid Lower LAN Madrid, Spain | 1G | PeeringDB | |
| FICIX 2 (Helsinki) Helsinki, Finland | Not in PeeringDB | ||
| France-IX AURA Lyon and Grenoble, France | 200M | PeeringDB | |
| France-IX Lille Lille, France | 200M | PeeringDB | |
| France-IX Marseille Marseille, France | 200M | PeeringDB | |
| France-IX Paris Paris, France | 200M | PeeringDB | |
| France-IX Toulouse Toulouse, France | 200M | PeeringDB | |
| GR-IX::Athens Athens, Greece | 1G | Both | |
| Guam IX Tamuning, Guam | 1G | Both Speed differs | |
| IIX-JawaTimur Surabaya, Indonesia | 1G | PeeringDB | |
| INEX Cork Cork, Ireland | 1G | Both | |
| INEX LAN1 Dublin, Ireland | Website list only | ||
| InterLAN-IX Bucharest, Romania | 1G | Both | |
| IXP.mk Skopje, North Macedonia | 1G | Both | |
| JINX Johannesburg, South Africa | 1G | Both Speed differs | |
| JPNAP Tokyo Tokyo, Japan | 10G | PeeringDB | |
| KazNIX Semey, Kazakhstan | 1G | Both | |
| KG-IX Bishkek Bishkek, Kyrgyzstan | 10G | Both | |
| LINX LON1 London, United Kingdom | 10G | Both | |
| LINX LON2 London, United Kingdom | 10G | Both | |
| LONAP London, United Kingdom | 10G | Both | |
| LU-CIX Luxembourg, Luxembourg | 1G | Both | |
| MIX-IT Milan, Italy | 1G | Both Speed differs | |
| MMIX Mandalay Mandalay, Myanmar | 1G | PeeringDB | |
| MMIX Yangon Yangon, Myanmar | 1G | PeeringDB | |
| MSK-IX Moscow Moscow, Russia | Website list only | ||
| MSK-IX Novosibirsk Novosibirsk, Russia | 1G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 1G | Both Speed differs | |
| NAPVE CCS Caracas, Venezuela | 1G | Both | |
| NAPVE MCBO Maracaibo, Venezuela | 1G | PeeringDB | |
| NetIX Sofia, Bulgaria | 1G | Both | |
| Ninja-IX Las Vegas Las Vegas, United States | 10G | Not in PeeringDB | |
| Ninja-IX Raleigh Raleigh, NC, United States | 10G | Not in PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 10G | Both | |
| PatagoniaIX Punta Arenas, Chile | 1G | Both | |
| PCIX Piacenza, Italy | 1G | Both | |
| PIT Honduras San Pedro Sula, Honduras | 10G | PeeringDB | |
| PIT MX Queretaro, Mexico | 1G | PeeringDB | |
| PIT Santiago - PIT Chile Santiago, Chile | 1G | PeeringDB | |
| Rheintal IX Eschen, Liechtenstein | 1G | Both | |
| RIX Reykjavik, Iceland | 1G | Both | |
| RTIX Tallinn, Estonia | 1G | PeeringDB | |
| RUDAKI-IX Kiev, Ukraine | 1G | Both | |
| SAIX Salzburg, Austria | 1G | PeeringDB | |
| SAIX Saudi Arabia Riyadh Riyadh, Saudi Arabia | 10G | Both | |
| STIX.DO Santiago, Dominican Republic | 10G | Not in PeeringDB | |
| STUIX Taipei City, Taiwan | 1G | Both | |
| SUPRnet Saint George, United States | 1G | Both | |
| SwissIX Zurich, Switzerland | 1G | Both | |
| TahoeIX Reno, United States | Not in PeeringDB | ||
| THINX Warsaw Warsaw, Poland | 1G | Both | |
| TPIX-TW Taipei/Taiwan, Taiwan | 1G | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 10G | Both | |
| UEPG Internet Exchange Ponta Grossa/PR, Brazil | 1G | PeeringDB | |
| VIX Vienna, Austria | 1G | Both | |
| VNIX-HCM Ho Chi Minh City, Vietnam | 1G | PeeringDB | |
| VNIX-HN Hanoi, Vietnam | 1G | PeeringDB | |
| YXEIX Saskatoon, Canada | 1G | Both | |
| YYCIX Calgary, Canada | 1G | Both |
RIPE NCC K-Root Operations lists no facilities in PeeringDB.
Recent changes Search them
- Nov 18, 2026 [WEB] AS25152 RIPE NCC K-Root Operations dropped from NAPAfrica IX Johannesburg's website list (still in PeeringDB and on its IX-F list)
- Nov 11, 2026 [PDB] AS25152 RIPE NCC K-Root Operations left NIXI Delhi