RIPE NCC Outage History

109 incidents recorded over the last 365 days, 72 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live RIPE NCC status100.00% uptime history

Every Recorded RIPE NCC Incident

RIPE NCC incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026RPKI Publication as a Service rejecting publicationsOn 3 November between 20.07 and 22:50 UTC the RFC8181 endpoint that provides Publication as a Service failed to validate publishers. As a result, CAs could not publish objects during that time. After restarting the…-1116 minResolved
Nov 3, 2026Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, and RIPE DatabaseScheduled maintenance is still in progress. We will provide updates as necessary.59 minScheduled
Nov 3, 2026RPKI System MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.30 minScheduled
Nov 3, 2026Planned Maintenance: RIPE AtlasScheduled maintenance is currently in progress. We will provide updates as necessary.30 minScheduled
Nov 3, 2026Intermitted issues accessing Resource information in LIR PortalThe applications using the database were impacted by failover of the load-balancer. We mitigated this short-term by clearing up the stale connections. We will work on the long-term mitigations: review of the…55 minResolved
Oct 30, 2026Intermittent RIPE Database update failuresWe had a short network link interruption on our primary Load balancer, which caused it to fail over to the standby Load balancer. Due to a misconfiguration, new Whois update connections to the database started via the…0 minResolved
Oct 29, 2026Invoices unavailable in the LIR PortalFollowing maintenance carried out by AFAS yesterday, we experienced a disruption to invoicing functionality which has now returned to normal.4h 19mResolved
Oct 28, 2026Intermittent RIPE Database update failuresThis incident has been resolved.27 minResolved
Oct 23, 2026RPKI System MaintenanceRPKI Dashboard is unavailable due to planned maintenance.30 minScheduled
Oct 23, 2026Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, RIPE DatabaseThe scheduled maintenance has been completed.1h 0mScheduled
Oct 23, 2026RPKI System MaintenanceThe scheduled maintenance has been completed.30 minScheduled
Oct 21, 2026RIPE NCC Academy, NRO and ASO Websites Temporarily UnavailableAll services are back online.44h 54mResolved
Oct 21, 2026Maintenance of RRC12, DE-CIX, FrankfurtThe scheduled maintenance has been completed.5h 0mScheduled
Oct 20, 2026Delayed data in RIPEstatThe delay in the final dataset that was affected was resolved by/on Tuesday 25 October 10:30 UTC. Other datasets recovered between Friday and Monday.196h 34mResolved
Oct 20, 2026RIS bview/update files are delayedThis incident has been resolved.35h 27mResolved
Oct 15, 2026Planned Maintenance: RIPE NCC WebsitesThe scheduled maintenance has been completed.1h 0mScheduled
Oct 7, 2026RIPE Database web application returning intermittent errorsThis incident has been resolved.24h 35mResolved
Oct 6, 2026RIS: RRC07 MRT update files are not producedThis incident has been resolved at 21.53 UTC of October 6th, 2026. Bview files were created normally.12h 47mResolved
Oct 6, 2026RIPE Atlas controller updatesThe scheduled maintenance has been completed.1h 0mScheduled
Oct 2, 2026RPKI dashboard in pilot environment is not availableThis incident has been resolved.10 minResolved
Oct 2, 2026Issues with rsync at rpki.ripe.netDowngrading the package resolved the issue. We will review our patching policy, as this incident shows that security updates of packages can contain behavioural changes that affect production services.1h 11mResolved
Oct 2, 2026RIS: RRC12 MRT update and bview files are not producedThis incident has been resolved. After the initial process recovered, the bview and update files since 2 October were produced successfully. The incident trigger was a high volume of updates from one peer. This caused…95h 1mResolved
Oct 1, 2026Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, RIPE Database and RPKI DashboardThe scheduled maintenance has been completed.30 minScheduled
Sep 30, 2026RPKI Pilot APIs are unavailableThis incident has been resolved.38 minResolved
Sep 29, 2026Problems authenticating with RIPE AtlasAuthentication / logins have been working correctly since the last update.22h 19mResolved
Sep 23, 2026Planned Maintenance: RIPE AtlasThe scheduled maintenance has been completed.30 minScheduled
Sep 17, 2026RPKI Test Environment: external APIs are not workingThis incident has been resolved.37 minResolved
Sep 7, 2026RIS pipeline issue — not publishing update/bview filesRIS updates and bviews for RRC24 have been published. On startup, the pipeline step processing the Kafka partition handled an unusually large volume of records, which caused a timeout. This is unlikely to be related to…30h 28mResolved
Sep 4, 2026rrc18 CATNIX, Barcelona: RIS update/bview files are not being publishedThe problem with RRC18 was resolved by restarting two services running in the backend, however the root cause is not clear yet. We keep troubleshooting. A similar problem is now affecting RRC24 at Montevideo, Uruguay.63h 5mResolved
Sep 1, 2026Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, RIPE Database and RPKI DashboardThe scheduled maintenance has been completed.30 minScheduled
Aug 26, 2026Maintenance of RRC24 - Montevideo, UruguayThe scheduled maintenance has been completed.6h 0mScheduled
Aug 26, 2026Document Retrieval Failure in Document Management System (Alfresco)This incident has been resolved.26h 57mResolved
Aug 25, 2026No new bview files being publishedThis incident has been resolved.234h 45mResolved
Aug 25, 2026RIPE Atlas controller updateThe scheduled maintenance has been completed.1h 0mScheduled
Aug 24, 2026Document Retrieval Failure in Document Management System (Alfresco)This incident has been resolved.1h 0mResolved
Aug 22, 2026Document Management System UpdateThe scheduled maintenance has been completed.12h 0mScheduled
Aug 20, 2026Planned Maintenance: Meeting Registration SoftwareThe scheduled maintenance has been completed.1h 30mScheduled
Aug 20, 2026Planned Maintenance: Meeting SoftwareWe will be undergoing scheduled maintenance during this time.1h 30mScheduled
Aug 18, 2026Issue with scheduling some RIPE Atlas measurementsA fix to an internal backend was deployed at around 13:30 CEST and the issue has not reappeared since. We are working on extra monitoring to prevent issues of this type from affecting measurement scheduling in the…4h 17mResolved
Aug 5, 2026Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, RIPE Database and RPKI DashboardThe scheduled maintenance has been completed.30 minScheduled
Aug 4, 2026NRTM and Split files : Not workingBetween approximately 00:06 UTC on Sunday, 2 August 2026 and 12:30 UTC on Tuesday, 4 August 2026, there was an issue affecting the RIPE Database NRTM mirroring service. The root cause was an invalid RPSL object being…5h 22mResolved
Jul 30, 2026Maintenance of RRC11, NYIIX, New York CityThe scheduled maintenance has been completed.1h 0mScheduled
Jul 28, 2026Maintenance of RRC01 at LINX/LONAP, LondonThe scheduled maintenance has been completed.1h 0mScheduled
Jul 23, 2026Maintenance of RRC07 at Netnod, StockholmThe scheduled maintenance has been completed.1h 0mScheduled
Jul 21, 2026Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, RIPE Database and RPKI DashboardThe scheduled maintenance has been completed.30 minScheduled
Jul 20, 2026Billing and Payment system unavailablePayment confirmation functionality has returned and invoices are available. The incident has been resolved.3h 34mResolved
Jul 20, 2026RIPE Database: Mail Updates Not WorkingMail Updates were failing due to an issue with the central mail server. This has since been resolved at 12:14 UTC3h 7mResolved
Jul 17, 2026Maintenance of RRC07, Netnod, StockholmThe scheduled maintenance has been completed.2h 10mScheduled
Jul 16, 2026Scheduled Maintenance Report for RIPE NCCThe scheduled maintenance has been completed.7h 0mScheduled
Jul 16, 2026Billing and Payment system intermittently unavailablePayment confirmation functionality has returned and invoices are available. The incident has been resolved.30h 36mResolved
Jul 14, 2026RIPE Atlas outageThis incident has been resolved.12h 36mResolved
Jul 7, 2026RIPE Database SwitchoverThe scheduled maintenance has been completed.1h 0mScheduled
Jul 2, 2026RIS update files are not being writtenThe backlog of update files was published by 6:25 UTC. This incident has been resolved.42 minResolved
Jul 1, 2026RIPE Database SwitchoverThe scheduled maintenance has been completed.1h 0mScheduled
Jun 30, 2026informational: ASPA objects close to expiryThe 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.7h 10mResolved
Jun 29, 2026RPKI System MaintenanceThe scheduled maintenance has been completed.30 minScheduled
Jun 29, 2026delayed routing data in ripestat (except looking glass)Data processing has caught up. This incident has been resolved.18h 33mResolved
Jun 29, 2026Maintenance of RRC03, AMS-IX / NL-IX, AmsterdamThe scheduled maintenance has been completed.6h 0mScheduled
Jun 20, 2026RIS data files unavailableWe 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…48h 9mResolved
Jun 18, 2026High error rate and degrated performance for RIPEstatThis incident has been resolved.91h 23mResolved
Jun 18, 2026rrc18 is not availableThis incident has been resolved. rrc18 did not capture data between 17 June 13:25 UTC and 18 June 7:45 UTC. We will work on the underlying monitoring gap that extended the duration of the outage.21 minResolved
Jun 17, 2026RIPE Database SwitchoverThe scheduled maintenance has been completed.1h 0mScheduled
Jun 11, 2026RRC12 DE-CIX Frankfurt: shutdown for maintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jun 8, 2026Planned Maintenance: LIR PortalThe scheduled maintenance has been completed.1h 0mScheduled
Jun 8, 2026rrc07 is not availableThis incident has been resolved. No data was lost during this incident, data from rrc07 during the affected time period (~11:15-19:45 UTC) is available in the RIS archives.14h 44mResolved
Jun 8, 2026RIPE Atlas software probes degradationThis incident has been resolved. The root cause was a backend that started answering slower than expected and caused many internal requests to take too long, clogging up the processing pipelines. These requests were…7h 43mResolved
Jun 5, 2026Planned Maintenance: AFAS OnlineThe scheduled maintenance has been completed.3h 0mScheduled
Jun 5, 2026TLSA records on our email MX serversThis incident has been resolved.40h 43mResolved
Jun 5, 2026Planned maintenance: RIPE AtlasThe scheduled maintenance has been completed.1h 0mScheduled
Jun 5, 2026Issue with RIPEstatOur intervention worked and performance recovered.This incident has been resolved.94h 46mResolved
Jun 4, 2026Intermittent unavailability of FTP.RIPE.NETThis incident has been resolved.21 minResolved
Jun 2, 2026RIPE Atlas MaintenanceThe scheduled maintenance has been completed.5h 0mScheduled
Jun 2, 2026RIPE Database SwitchoverThe scheduled maintenance has been completed.1h 0mScheduled
May 30, 2026RIS bview files 1-3-2026 and 21-5-2026 downloaded after 26-5The files have been restored.48h 0mResolved
May 28, 2026Maintenance of RIS MRT dataUpdates 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: •…1h 0mScheduled
May 27, 2026Maintenance of RIS MRT dataThis maintenance is cancelled.1h 0mScheduled
May 27, 2026Intermittent errors on RIPE AccessWe are monitoring the issue. We opened two incidents in parallel by accident, and are closing this duplicate.13 minResolved
May 27, 2026Intermittent availability of RIPE Access, RPKI dashboard, and other services that require loginThe root cause for this was an engineer from our supplier performing work on another fiber in the same manhole as ours, and affecting our fiber in the process, causing it to disconnect for a couple of minutes…19 minResolved
May 21, 2026Billing & Payment system intermittently unavailableThis incident has been resolved.29 minResolved
May 20, 2026Issue accessing RIPE NCC ServicesOn 20 May 2026, between 11:29 and 12:40 UTC, a partial outage affected access to different RIPE NCC services. Primarily, users on the RIPE Meeting network experienced “Access denied” responses served by Akamai, our CDN…1h 19mResolved
May 19, 2026Billing & Payment system intermittently unavailableThis incident has been resolved.22 minResolved
May 14, 2026Intermittent RIPE Database Query Error ResponsesThere were intermittent errors occurring while updating and querying the RIPE database between 12:54-14:24 CEST . The issue has now been resolved.0 minResolved
May 7, 2026Issues with longitudinal RIS data APIS (e.g. routing history)This incident has been resolved.4h 36mResolved
May 4, 2026Issues with delegated CAsThis incident has been resolved.16h 4mResolved
Apr 30, 2026Issue processing incoming RIPE Atlas measurement resultsThis incident has been resolved.9h 50mResolved
Apr 23, 2026Issues affecting RIPEstat (including rpki and routing registry based datasets)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.4h 8mResolved
Apr 23, 2026rpki-validator.ripe.net unavailableThis incident has been resolved.46 minResolved
Apr 15, 2026Issues with AFAS SoftwareThis incident has been resolved.4h 12mResolved
Apr 4, 2026No new BGP data in some widgets/data callsThis problem was caused by a combination of problems in our HBase database and the MRT publishing pipeline of RIS. This incident has been resolved.58h 5mResolved
Apr 3, 2026RIS: RRC25 MRT update files are not createdWe fixed the BGP error handling issue, and MRT files for RRC25 are now created as expected. This incident has been fully resolved since 6 April at approximately 19:15 CEST.81h 20mResolved
Apr 3, 2026Connectivity Issue with AFASThis incident has been resolved.2 minResolved
Mar 19, 2026Unexpected issues during maintenanceWe were migrating databases for which we planned an hour of downtime. When doing that, we have faced some issues, which we needed to fix to be able to complete the migration successfully. That's why the migration took…55 minResolved
Mar 11, 2026RIPE Atlas controller problemsThis 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…17h 52mResolved
Mar 3, 2026Increased error rate with RIPEstatThe 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…7h 14mResolved
Feb 25, 2026RIPE Atlas API and user interface are currently unavailableThis incident has been resolved.9h 30mResolved
Feb 19, 2026RIPE Database Mail Update FailuresThis incident has been resolved.3h 4mResolved
Feb 17, 2026RIPE Database Update FailuresBetween approximately 12:04 to 12:16 CET today, there were some failures updating the RIPE database. We are investigating the cause(s).0 minResolved
Feb 17, 2026RIPE Database Update FailuresBetween approximately 10:35 to 10:49 CET this morning, there were some failures updating the RIPE database. We are investigating the cause(s).0 minResolved
Feb 14, 2026RIS RRC05 and RRC07 — data processing issuesWe completed our checks and found no data issues. This incident has been resolved.40h 42mResolved
Feb 10, 2026Failing UpdatesThis incident has been resolved.22h 44mResolved
Feb 5, 2026High Error Rates for RIPEstat API EndpointsThis incident has been resolved.96h 28mResolved
Jan 21, 2026Increased error rate for RIPEstatThis incident has been resolved.3h 22mResolved
Jan 16, 2026Increased error rate for ripestatAll indicators have been stable since the last update. This incident has been resolved.4h 40mResolved
Jan 7, 2026Empty RPKI repositories (and missing trust anchor certificate) publishedOn 7 January 2026 at 15:11 UTC, all objects were removed from both our RRDP and rsync RPKI repositories. At 15:20 UTC, the repository state was restored, and all objects were back. At 15:08 UTC, we did a production…43 minResolved
Dec 23, 2025Elevated Error Rates for RIPEstat API EndpointsThis incident has been resolved.3h 19mResolved
Dec 5, 2025External ticketing system has access issuesThe issue has now been resolved and services have been restored in the LIR Portal. An external service provider experienced an outage which affected our ticketing system.3h 53mResolved
Dec 4, 2025Issue with RIPE PortalThis incident has been resolved.2h 20mResolved
Nov 27, 2025Reduced network redundancy following link failureThe link is fully restored and services are stable. A post‑mortem will be published shortly.25h 37mResolved
Nov 27, 2025Delays in RIPE Atlas measurementsThis incident has been resolved.23h 51mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next RIPE NCC incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This RIPE NCC Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before RIPE NCC acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single RIPE NCC outage in this window ran 9d 18h, against a mean recovery of 16h 11m. If you depend on RIPE NCC in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.