Identified - We have received confirmed reports of email delivery issues affecting messages sent to the RIPE NCC. Some senders may have received temporary delivery failure notifications, but affected messages are expected to be retried and delivered automatically.
Jun 05, 2026 - 20:02 CEST
Investigating - The certificate authority we use changed the intermediate certificate of the certificates we use on our email MX servers, which we missed. This led to the TLSA records for our email MX servers to be incorrect. The TLSA records have been updated today around 16:00 Amsterdam time, but people verifying these may experience issues for the TTL duration of the records, which is 86400 seconds after the update in the worst case scenario.
Jun 05, 2026 - 16:18 CEST
Update - The immediate fix has been applied and the service is now operating in a degraded state. Some queries and API endpoints remain unavailable or unreliable, and the service may continue to experience periods of overload.
We are continuing to monitor the situation and will work on further mitigations to improve stability and latency.
Jun 05, 2026 - 17:15 CEST
Monitoring - Old backend infrastructure was decommissioned on 4/Jun as part of the Backend Infrastructure Switch announced on May 27. A configuration was still referencing such infrastructure; the configuration has been updated and the service is now restored. We will monitor how the new backend service performs.
Jun 05, 2026 - 11:39 CEST
Investigating - We are experiencing issues with RIPEstat. We are investigating and will update this announcement once we know more.
Jun 05, 2026 - 09:43 CEST
RIPE Database
Operational
90 days ago
99.99
% uptime
Today
Email to/from the RIPE NCC
Degraded Performance
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.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
Partial Outage
90 days ago
99.67
% uptime
Today
Billing & Payments
Operational
RIPEstat
Partial Outage
90 days ago
99.84
% 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.87
% 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.
Related
No incidents or maintenance related to this downtime.
The third-party service that we use for billing and payments, AFAS, will perform an upgrade of its database servers. During this maintenance, AFAS Online will be temporarily unavailable, which may flag any payment issues. Posted on
Jun 04, 2026 - 10:27 CEST
Completed -
The scheduled maintenance has been completed.
Jun 5, 11:00 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 5, 10:00 CEST
Scheduled -
We will be carrying out software updates on the RIPE Atlas controllers. You may experience delays in scheduling one-off measurements and receiving results during this time.
Jun 4, 09:49 CEST
Completed -
The scheduled maintenance has been completed.
Jun 2, 08:14 CEST
Verifying -
Verification is currently underway for the maintenance items.
Jun 2, 08:03 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 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.
May 29, 15:29 CEST
Resolved -
The files have been restored.
Jun 1, 09:02 CEST
Update -
Later today we will roll back the infrastructure change made on 28 May. Once the rollback is complete, the affected bview files will be republished from the previous infrastructure. Due to the data volume and the performance of the storage used by data.ris.ripe.net we expect this to take a significant amount of time.
We will provide a final update once the restore is complete.
May 30, 14:00 CEST
Identified -
We have identified a misconfiguration in the pipeline that publishes RIS bview files to data.ris.ripe.net, and are giving early notice.
As part of an infrastructure change on 27 May 2026, the publishing pipeline re-copied historical bview files produced after February 2022. This had two effects:
* File modification timestamps changed for historical bview files published after February 2022. * Some bview files produced between 1 March 2026 and 21 May 2026 may be incomplete.
This affects copies of files downloaded after 26 May 2026.
For the incomplete files, the likely impact is that data from some RIS peers may be missing from the affected bviews. The data has not been lost. We have multiple copies available and expect to fully recover the affected files after the weekend.
May 30, 09:02 CEST
Completed -
Updates and routing table dumps (bview*) are now generated from our new infrastructure, running on rented bare metal servers.
There are no changes to the data, and no action is required on your end.
What this means: • Update files dated after updates.20260528.0855.gz are produced by the new pipeline. • Dump files (bview*) dated after bview.20260528.0800.gz are produced by the new pipeline.
If you notice any unexpected behaviour, please don't hesitate to reach out.
May 28, 13:44 CEST
Verifying -
Verification is currently underway for the maintenance items.
May 28, 12:03 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 11:00 CEST
Scheduled -
We are performing maintenance on the pipeline responsible for generating MRT dumps and update files. During the maintenance window, new update files will not be published. (This maintenance was originally scheduled for May 27th)
May 27, 10:57 CEST
Completed -
This maintenance is cancelled.
May 27, 10:59 CEST
Scheduled -
We are performing maintenance on the pipeline responsible for generating MRT dumps and update files. During the maintenance window, new update files will not be published.
May 26, 23:04 CEST
Resolved -
We had a fiber issue between our data centers which also caused network problems for RIPE Access. The fiber issues seems to be fixed now and RIPE Access has also recovered.
May 27, 10:46 CEST
Update -
We are continuing to monitor for any further issues.
May 27, 10:38 CEST
Monitoring -
We have resolved the issue and continue to monitor the situation closely. We will share an update when it has been fully resolved.
May 27, 10:37 CEST
Identified -
We have identified the issue, the [explain the issue] and we are working to resolve it.
May 27, 10:36 CEST
Investigating -
We are currently investigating this issue.
May 27, 10:26 CEST
Completed -
The scheduled maintenance has been completed.
May 27, 10:30 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 27, 10:15 CEST
Scheduled -
Status: informational. We expect no impact.
On Wednesday May 27 at 08:15 UTC we will switch the backend used by RIPEstat from our on-premise backends to a backend hosted on rented bare metal servers. This will lead to additional latency between RIPEstat and backend systems.
We have evaluated the latency increase and expect no significant impact. We have evaluated the expected increase and do not anticipate any significant impact. Recent work to parallelise backend queries should help hide most of this additional latency.
We will carefully monitor how this migration affects RIPEstat. Please contact us if you observe a change in either the data or performance.
May 26, 17:52 CEST
Completed -
The scheduled maintenance has been completed.
May 26, 14:00 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 26, 13:00 CEST
Scheduled -
We will carry out maintenance on a backend system of RIS Live component as part of our migration of RIS backend systems to new infrastructure. During this maintenance RIS Live will not produce data for up to 30 minutes.
During the maintenance window we will switch an upstream system used by RIS Live. The new instance runs independently from the current one. As a result, RIS Live cannot continue producing data during the switchover without risking duplicate messages. Instead, there will be a short downtime.
During the maintenance window, we will: * Stop RIS Live data production * Reconfigure backend systems * Start RIS Live data production from the new backend systems
There will be no overlap in data. We expect a gap of up to 30 minutes in RIS Live data.
May 22, 15:15 CEST