Major incident

RIPE NCC: Intermittent RIPE Database update failures

Affected: Reverse DNS

Current status of RIPE NCC: Operational — live RIPE NCC status

Timeline

1. Oct 30, 2026, 09:33 UTC
   resolved
   Between 2026-10-28 11:42 UTC and 2026-10-28 19:40 UTC RIPE Database updates failed intermittently. This had the effect that the creation, update or deletion of reverse delegations was failing intermittently as well. This incident is tracked in https://status.ripe.net/incidents/0kyh1b9zn60h Update [2026-10-30 13:07 UTC]: A more detailed investigation of the failed requests showed than none would have resulted in a change of reverse delegations because they either contained no changes or failed predelegation checks in zonemaster.
2. Nov 3, 2026, 13:13 UTC
   postmortem
   We had a short network link interruption on our primary Load balancer, which caused it to fail over to the standby Load balancer. Due to a misconfiguration, new Whois update connections to the database started via the newly elected load balancer to the read-only database instead of the primary database, which caused some updates to fail. Existing connections from the application remained connected to the primary database and were unaffected.

Updates as published by RIPE NCC (original).