All Systems Operational

RIPE Database Operational
90 days ago
99.95 % uptime
Today
Email to/from the RIPE NCC Operational
90 days ago
100.0 % uptime
Today
K-root/DNS Operational
90 days ago
100.0 % uptime
Today
LIR (Member) Portal Operational
90 days ago
99.99 % uptime
Today
RIPE NCC Access Operational
90 days ago
99.98 % uptime
Today
RPKI Operational
90 days ago
99.99 % uptime
Today
RPKI Dashboard Operational
90 days ago
99.99 % uptime
Today
RRDP Repository Operational
90 days ago
99.99 % uptime
Today
rsync Repository Operational
90 days ago
99.99 % uptime
Today
Publication as a Service (API endpoints) Operational
90 days ago
100.0 % uptime
Today
www.ripe.net Operational
90 days ago
100.0 % uptime
Today
Reverse DNS Operational
90 days ago
100.0 % uptime
Today
Non-Critical Services Operational
90 days ago
99.97 % uptime
Today
Billing & Payments Operational
RIPEstat Operational
90 days ago
99.89 % uptime
Today
DNSMON Operational
Mailing Lists Operational
RIPE NCC Academy Operational
RIPE NCC Certified Professionals Operational
RIPE Atlas Operational
RIPE Labs Operational
RIS (Routing Information Service) Operational
90 days ago
100.0 % uptime
Today
Meeting Software Operational
Pilot (RPKI) Operational
90 days ago
100.0 % uptime
Today
ftp.ripe.net Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Scheduled Maintenance

Disaster recovery test for DNS provisioning Mar 19, 2026 15:00-17:00 CET

We will be performing a disaster recovery exercise for our DNS provisioning system. During this time frame, changes to domain objects in the RIPE Database will not be propagated automatically to the DNS servers.

The DNS service itself will not be affected.

Posted on Mar 12, 2026 - 13:31 CET

Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, RIPE Database and RPKI Dashboard Mar 19, 2026 18:00-19:00 CET

We will carry out scheduled maintenance
Posted on Mar 11, 2026 - 10:54 CET
Mar 13, 2026

No incidents reported today.

Mar 12, 2026
Resolved - This incident has been resolved. It was ultimately caused by an overly restrictive permission check in the component that serves as the entry point for probe (the "registration server"). In itself this was not a major problem and would have been detected and resolved before it affected the probe population. However, independently of this, and as part of our normal software development process, we rolled out upgrades to our controlling infrastructure, which caused most of the probes to disconnect and try to re-register with the system. This is normal and expected - but in this case the registration server was not ready to answer them, and as a result they were unable to immediately re-join.
Mar 12, 09:03 CET
Monitoring - A fix has been implemented and we're monitoring the situation.
Mar 11, 16:42 CET
Identified - We identified the root cause of the issue and applied a fix, probes are connecting again.
Mar 11, 15:28 CET
Investigating - A part the RIPE Atlas probe population is unable to connect to our infrastructure. We're investigating the issue.
Mar 11, 15:11 CET
Mar 11, 2026
Completed - The scheduled maintenance has been completed.
Mar 11, 08:23 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 11, 08:00 CET
Scheduled - 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.
Mar 5, 17:08 CET
Mar 10, 2026

No incidents reported.

Mar 9, 2026
Completed - The scheduled maintenance has been completed.
Mar 9, 18:36 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 9, 18:30 CET
Scheduled - We will do maintenance.
Feb 26, 12:03 CET
Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026

No incidents reported.

Mar 4, 2026
Completed - The scheduled maintenance has been completed.
Mar 4, 13:54 CET
Verifying - Verification is currently underway for the maintenance items.
Mar 4, 13:31 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 4, 12:30 CET
Scheduled - We will be undergoing scheduled maintenance during this time.
Mar 4, 10:18 CET
Mar 3, 2026
Completed - The scheduled maintenance has been completed.
Mar 3, 18:16 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 3, 17:30 CET
Scheduled - We will do maintenance. We do not expect any down time.
Feb 18, 11:45 CET
Completed - The scheduled maintenance has been completed.
Mar 3, 17:29 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 3, 13:00 CET
Scheduled - We will be undergoing scheduled maintenance during this time.
Mar 3, 09:12 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
Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

No incidents reported.