We plan to perform a switchover of the RIPE database primary instance, so we can perform patching on the server. We don't expect any downtime for Whois queries or updates. Posted on
Mar 05, 2026 - 17:08 CET
Resolved -
The error rates have come back and stayed within typical levels. The issue was caused by the application keeping TCP connections in a non-closed state, exhausting resources. After restarting some backend services those connections were flushed and the issue resolved.
Mar 3, 15:04 CET
Monitoring -
We have mitigated the issue and will continue to monitor the situation closely. We will share an update when it has been fully resolved.
Mar 3, 09:26 CET
Investigating -
We are experiencing issues with RIPEstat since ~02:17 UTC. We are investigating and will update this announcement once we know more.
Mar 3, 07:50 CET
Completed -
The scheduled maintenance has been completed.
Feb 26, 08:51 CET
Update -
Scheduled maintenance is still in progress. We will provide updates as necessary.
Feb 26, 08:51 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 26, 08:15 CET
Scheduled -
We will carry out planned maintenance on RIPE Atlas. During this time, RIPE Atlas will be unavailable or not fully functional.
Feb 26, 07:03 CET
Resolved -
This incident has been resolved.
Feb 26, 08:07 CET
Monitoring -
A network issue affected connectivity within our Hadoop cluster. The cluster and HBase database are back to normal operations. Processing delays are decreasing. We are monitoring the results.
Feb 25, 22:47 CET
Identified -
The issue has been identified and a fix is being implemented.
Feb 25, 22:40 CET
Investigating -
We are currently investigating this issue.
Feb 25, 22:37 CET