All Systems Operational

Uptime over the past 90 days. View historical uptime.
RIPE Database Operational
90 days ago
99.99 % 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.99 % 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
100.0 % uptime
Today
rsync Repository Operational
90 days ago
100.0 % 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.44 % uptime
Today
Billing & Payments Operational
RIPEstat Operational
90 days ago
98.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
98.86 % 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

RIPE Database Switchover Jul 7, 2026 08:00-09:00 CEST

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 Jul 03, 2026 - 10:43 CEST
Jul 4, 2026

No incidents reported today.

Jul 3, 2026

No incidents reported.

Jul 2, 2026
RIS update files are not being written
Resolved - The backlog of update files was published by 6:25 UTC. This incident has been resolved.
Jul 2, 08:45 CEST
Identified - The issue has been identified. It was a repeat of an earlier issue. Unfortunately our attempto to fix the monitoring gap in https://status.ripe.net/incidents/vmt6vb0jxdkq did not work, causing the extended outage.
Jul 2, 08:14 CEST
Investigating - RIS update files were not written since 1 July, 21:40 UTC. We are currently investigating the issue.
Jul 2, 08:03 CEST
Jul 1, 2026
RIPE Database Switchover
Completed - The scheduled maintenance has been completed.
Jul 1, 09:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 1, 08:00 CEST
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.
Jun 30, 10:21 CEST
Jun 30, 2026
informational: ASPA objects close to expiry
Resolved - The affected ASPA objects (287 ASPA objects for 232 hosted CAs signed in 2025) were re-signed and published around 14:50 UTC.

The underlying software bug has been fixed. This incident has been resolved.
Jun 30, 21:14 CEST
Identified - We have noticed that a number of ASPA are approaching their expiry date. The ASPA objects were not re-issued when the CA certificate that signed them was re-issued on 1 January.

We have identified the issue and are implementing a fix. The fix will be rolled out before objects expire. We do not expect any impact.
Jun 30, 14:03 CEST
delayed routing data in ripestat (except looking glass)
Resolved - Data processing has caught up. This incident has been resolved.
Jun 30, 10:02 CEST
Update - The situation is improving. Some APIs are up to date. Other APIs (for example routing-status) still return stale or partial data.

We will provide another update tomorrow morning.
Jun 29, 17:32 CEST
Identified - Most BGP data in RIPEstat, except for the Looking Glass, is currently delayed. This issue started on 26 June 2026.

We have not processed new data since 26 June due to problems in our big data backend systems. A disruption in our ZooKeeper cluster prevented data from being processed. The zookeeper cluster was running, but a single type of data processing flow did not make progress.

This affects the following RIPEstat APIs:
* announced-prefixes
* prefix-count
* prefix-size-distribution
* prefix-overview
* prefix-routing-consistency
* routing-history
* routing-statistics
* routing-status.

Data processing has now resumed. We will share another update when we have an ETA for the backlog to clear.

A monitoring gap delayed our detection of this issue. The RIS team is already working on improving the monitoring for the processing pipeline. We will also fix the monitoring gap for the ZooKeeper cluster that this issue uncovered.
Jun 29, 15:28 CEST
Jun 29, 2026
RPKI System Maintenance
Completed - The scheduled maintenance has been completed.
Jun 29, 22:08 CEST
Verifying - Verification is currently underway for the maintenance items.
Jun 29, 22:08 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 29, 22:00 CEST
Scheduled - RPKI Dashboard is unavailable due to planned maintenance.
Jun 29, 14:44 CEST
Maintenance of RRC03, AMS-IX / NL-IX, Amsterdam
Completed - The scheduled maintenance has been completed.
Jun 29, 16:49 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 29, 12:00 CEST
Scheduled - We will be carrying out maintenance on rrc03.ripe.net, RIS collector at AMS-IX and NL-IX.

During the maintenance window:
BGP sessions will be down.
MRT files will not be produced.
Jun 26, 16:05 CEST
Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.

Jun 25, 2026

No incidents reported.

Jun 24, 2026

No incidents reported.

Jun 23, 2026

No incidents reported.

Jun 22, 2026
RIS data files unavailable
Resolved - We applied a mitigation and RIS update file production, including the backfill of affected data, recovered on Saturday, 20 June, at around 15:35 UTC.

The root cause was a process that had become stuck. A gap in our monitoring after the recent migration means we did not detect this. We have now fixed that monitoring gap.

This incident has been resolved.
Jun 22, 16:34 CEST
Investigating - We are seeing issues with the production of RIS update files for our RRCs. The issue is under investigation, we will resolve this problem and backfill data at our earliest convenience. Once more updates are available, we will share them here.
Jun 20, 16:24 CEST
High error rate and degrated performance for RIPEstat
Resolved - This incident has been resolved.
Jun 22, 09:08 CEST
Monitoring - The root cause likely is a cascade of HBase region server restarts after a Zookeeper session expired due to an unknown cause. The most likely cause is timeout after a worker did not communicate for 40 seconds.

We will add high resolution network monitoring between each zookeeper node and all zookeeper clients to track potential network issues.
Jun 18, 15:51 CEST
Identified - We have identified a faulty node in the HBase cluster and applied mitigations.

The error rate remains elevated at around 5%, but RIPEstat functionality has improved. We are continuing to monitor the situation.
Jun 18, 14:20 CEST
Investigating - Since around 10:15 UTC, RIPEstat has been experiencing elevated error rates and increased latency.

The issue is caused by a failing node in HBase, the distributed database used by many RIPEstat datasets. We are currently investigating the issue.
Jun 18, 13:45 CEST
Jun 21, 2026

No incidents reported.

Jun 20, 2026
← Incident History Powered by Atlassian Statuspage