All Systems Operational

Uptime over the past 90 days. View historical uptime.
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.98 % 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.98 % uptime
Today
Billing & Payments Operational
RIPEstat Operational
90 days ago
99.92 % 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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Planned Maintenance - no down time is expected. RIPE NCC Access Account (SSO), LIR Portal, RIPE Database and RPKI Dashboard Mar 3, 2026 17:30-18:30 CET

We will do maintenance. We do not expect any down time.
Posted on Feb 18, 2026 - 11:45 CET

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

We will do maintenance.
Posted on Feb 26, 2026 - 12:03 CET
Feb 28, 2026

No incidents reported today.

Feb 27, 2026

No incidents reported.

Feb 26, 2026
Planned Maintenance: RIPE Atlas
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
RIPE Atlas API and user interface are currently unavailable
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
Feb 25, 2026
Feb 24, 2026

No incidents reported.

Feb 23, 2026

No incidents reported.

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Feb 20, 2026

No incidents reported.

Feb 19, 2026
Planned Maintenance: root-servers.org
Completed - The scheduled maintenance has been completed.
Feb 19, 16:29 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 19, 16:00 CET
Scheduled - We will be carrying out maintenance on server supporting root-servers.org. The website will be unreachable during the maintenance window.
Feb 18, 15:25 CET
RIPE Database Mail Update Failures
Resolved - This incident has been resolved.
Feb 19, 12:05 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 19, 09:01 CET
Update - We are continuing to investigate this issue.
Feb 19, 09:01 CET
Investigating - Between approximately 1:00 to 9:00 CET today, there were some failures updating the RIPE database through mailupdates. We are investigating the cause(s).
Feb 19, 09:00 CET
Feb 18, 2026
RIPE Database Switchover
Completed - The scheduled maintenance has been completed.
Feb 18, 08:13 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 18, 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.
Feb 11, 14:24 CET
Feb 17, 2026
RIPE Database Update Failures
Resolved - Between approximately 12:04 to 12:16 CET today, there were some failures updating the RIPE database. We are investigating the cause(s).
Feb 17, 14:28 CET
RIPE Database Update Failures
Resolved - Between approximately 10:35 to 10:49 CET this morning, there were some failures updating the RIPE database. We are investigating the cause(s).
Feb 17, 14:26 CET
Feb 16, 2026
RIS RRC05 and RRC07 — data processing issues
Resolved - We completed our checks and found no data issues. This incident has been resolved.
Feb 16, 15:40 CET
Update - Processing for rrc05 and rrc07 has recovered. We will verify on Monday that the bview files contain all expected data and post a further update then.
Feb 14, 23:08 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 14, 23:05 CET
Investigating - We are investigating an issue affecting rrc05 and rrc07. A problem with processing part of the incoming data is blocking downstream data production, resulting in:

RIS-live: Several peers for rrc05 and rrc07 are not receiving data updates.
RIS Raw Data (dumps): We are not producing new bview and update files for rrc05 and rrc07.

Both collectors continue to collect data normally. The last available update files are:
* rrc05: updates.20260214.1405.gz
* rrc07: updates.20260214.1300.gz

We are currently investigating this issue.
Feb 14, 22:58 CET
Feb 15, 2026

No incidents reported.

Feb 14, 2026
← Incident History Powered by Atlassian Statuspage