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.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
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.71 % uptime
Today
Billing & Payments Operational
RIPEstat Operational
90 days ago
99.97 % 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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

RIPE Database Switchover May 6, 2026 13:00-14: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 May 05, 2026 - 12:24 CEST
May 6, 2026

No incidents reported today.

May 5, 2026
Issues with delegated CAs
Resolved - This incident has been resolved.
May 5, 13:07 CEST
Identified - We are currently investigating an issue that prevents delegated CAs from communicating with the RIPE NCC parent CA.

This issue does not affect the validity of delegated CAs that already have a current certificate. Publication by delegated CAs is also unaffected.

The BPKI TA certificate used in the RFC 8183 XML setup messages for delegated CAs, and the CRL included in RFC 6492 provisioning protocol messages signed by the RIPE NCC CA have expired.

The impact is as follows:
Delegated CAs cannot be configured at the moment
Existing delegated CAs may see the following error message: "RFC 6492 Issue: CMS is not valid: CRL nextUpdate time in the past"
Existing delegated CAs cannot request certificates for updated resources
Existing delegated CAs cannot perform an RPKI key rollover

As far as we understand, Krill verifies the validity period of the BPKI TA certificate during setup only, and then continues to trust the public key until it is told otherwise. Because of this we expect that the issues experienced by existing Krill CAs will be resolved when our system starts using updated CRLs in the RFC 6492 messages.

We are working on a fix. Because the fix is non-trivial we expect that this issue may persist for the next 12 to 24 hours.

We will provide a further update tomorrow morning.
May 4, 21:03 CEST
May 4, 2026
May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026
Issue processing incoming RIPE Atlas measurement results
Resolved - This incident has been resolved.
May 1, 08:59 CEST
Monitoring - The problems appear to have been caused by temporary connectivity issues between our data queuing systems and the processing environment. Those issues now seem to be resolved. We will monitor the situation.
Apr 30, 23:29 CEST
Investigating - There is currently an issue with the processing of incoming measurement results for RIPE Atlas. We are investigating the issue and will update this status message when we have more details to share.
Apr 30, 23:09 CEST
Apr 30, 2026
Apr 29, 2026

No incidents reported.

Apr 28, 2026

No incidents reported.

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026

No incidents reported.

Apr 23, 2026
Issues affecting RIPEstat (including rpki and routing registry based datasets)
Resolved - Our IRRd instances that we use to have a local copy of internet routing registry data have recovered. This final recovery resolves this incident for RIPEstat.
Apr 23, 11:37 CEST
Update - We are continuing to monitor for any further issues.
Apr 23, 07:28 CEST
Monitoring - RIPEstat experienced partial unavailability between 03:00 and 05:30 UTC due to a widespread Docker infrastructure issue at RIPE NCC. Because the issue also affected our monitoring infrastructure during this window, we cannot fully determine the scope of the impact. Services have recovered. We are investigating the root cause.
Apr 23, 07:28 CEST
rpki-validator.ripe.net unavailable
Resolved - This incident has been resolved.
Apr 23, 06:11 CEST
Investigating - We are currently investigating this issue.
Apr 23, 05:25 CEST
Apr 22, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage