RIPE Network Coordination Centre Outage History

RIPE Network Coordination Centre is up right now

There were 16 RIPE Network Coordination Centre outages since February 5, 2026 totaling 356h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ripe.net

Major April 30, 2026

Issue processing incoming RIPE Atlas measurement results

Detected by Pingoru
Apr 30, 2026, 09:09 PM UTC
Resolved
May 01, 2026, 06:59 AM UTC
Duration
9h 50m
Affected: RIPE Atlas
Timeline · 3 updates
  1. investigating Apr 30, 2026, 09:09 PM UTC

    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.

  2. monitoring Apr 30, 2026, 09:29 PM UTC

    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.

  3. resolved May 01, 2026, 06:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 23, 2026

Issues affecting RIPEstat (including rpki and routing registry based datasets)

Detected by Pingoru
Apr 23, 2026, 05:28 AM UTC
Resolved
Apr 23, 2026, 09:37 AM UTC
Duration
4h 8m
Affected: RIPEstat
Timeline · 3 updates
  1. monitoring Apr 23, 2026, 05:28 AM UTC

    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.

  2. monitoring Apr 23, 2026, 05:28 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Apr 23, 2026, 09:37 AM UTC

    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.

Read the full incident report →

Notice April 23, 2026

rpki-validator.ripe.net unavailable

Detected by Pingoru
Apr 23, 2026, 03:25 AM UTC
Resolved
Apr 23, 2026, 04:11 AM UTC
Duration
46m
Timeline · 2 updates
  1. investigating Apr 23, 2026, 03:25 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 23, 2026, 04:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 15, 2026

Issues with AFAS Software

Detected by Pingoru
Apr 15, 2026, 01:22 PM UTC
Resolved
Apr 15, 2026, 05:35 PM UTC
Duration
4h 12m
Affected: LIR (Member) Portal
Timeline · 2 updates
  1. investigating Apr 15, 2026, 01:22 PM UTC

    We are currently experiencing issues caused by the AFAS software, which are affecting the invoice functionality in the LIR Portal. Members may experience difficulties viewing or paying their invoices.

  2. resolved Apr 15, 2026, 05:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 4, 2026

No new BGP data in some widgets/data calls

Detected by Pingoru
Apr 04, 2026, 08:00 PM UTC
Resolved
Apr 07, 2026, 06:06 AM UTC
Duration
2d 10h
Affected: RIPEstat
Timeline · 2 updates
  1. identified Apr 04, 2026, 08:00 PM UTC

    We are currently experiencing issues with the distributed database (HBase) that is used by RIS and RIPEstat. As a result, some data can not be written to the database. This is causing issues with the data processing pipeline for RIPEstat. As a result: * Data in RIPEstat for RRC25 can not be updated after 2026-04-03 08:00 UTC. * Data for some RIPEstat data calls/widgets, that contain BGP data derived from RIS, has not updated after 2026-04-03 08:00 UTC. For the RIPEstat looking glass, routes collected from RRC25 are outdated. RIS-live is not affected, updates for RRC25 are processed as usual. Resolving this issue requires multiple colleagues to be available. We expect to provide an update on Tuesday 7 April after the Easter holiday.

  2. resolved Apr 07, 2026, 06:06 AM UTC

    This problem was caused by a combination of problems in our HBase database and the MRT publishing pipeline of RIS. This incident has been resolved.

Read the full incident report →

Minor April 3, 2026

RIS: RRC25 MRT update files are not created

Detected by Pingoru
Apr 03, 2026, 08:44 PM UTC
Resolved
Apr 07, 2026, 06:05 AM UTC
Duration
3d 9h
Affected: RIS (Routing Information Service)
Timeline · 4 updates
  1. investigating Apr 03, 2026, 08:44 PM UTC

    MRT update files for the RIS collector RRC25 are not being created.

  2. investigating Apr 04, 2026, 05:50 AM UTC

    The MRT file are not being created due to a kafka rebalancing problem affecting a specific consumer group. This is likely caused by a problem in our hadoop backend.

  3. identified Apr 05, 2026, 01:20 PM UTC

    The root cause is an issue in BGP error handling in our BGP processing pipeline. This prevents messages from being processed. We are also working on a separate issue with our Hadoop backend, that might be affecting the creation of update files for RRC25. We will work on the error handling issue first.

  4. resolved Apr 07, 2026, 06:05 AM UTC

    We 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.

Read the full incident report →

Minor April 3, 2026

Connectivity Issue with AFAS

Detected by Pingoru
Apr 03, 2026, 10:08 AM UTC
Resolved
Apr 03, 2026, 10:10 AM UTC
Duration
2m
Affected: LIR (Member) Portal
Timeline · 2 updates
  1. investigating Apr 03, 2026, 10:08 AM UTC

    We are currently facing connectivity issues with AFAS, which are affecting the invoice functionality in the portal. Members may experience difficulties viewing or paying their invoices.

  2. resolved Apr 03, 2026, 10:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 19, 2026

Unexpected issues during maintenance

Detected by Pingoru
Mar 19, 2026, 06:02 PM UTC
Resolved
Mar 19, 2026, 06:57 PM UTC
Duration
55m
Affected: RIPE DatabaseRPKI DashboardLIR (Member) PortalRIPE NCC Access
Timeline · 4 updates
  1. investigating Mar 19, 2026, 06:02 PM UTC

    During our planned maintenance we experienced issues. We are still working on the maintenance and we are trying to solve these issues

  2. investigating Mar 19, 2026, 06:57 PM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 19, 2026, 06:57 PM UTC

    This incident has been resolved.

  4. postmortem Mar 19, 2026, 06:58 PM UTC

    We 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 longer than we anticipated.

Read the full incident report →

Major March 11, 2026

RIPE Atlas controller problems

Detected by Pingoru
Mar 11, 2026, 02:11 PM UTC
Resolved
Mar 12, 2026, 08:03 AM UTC
Duration
17h 52m
Affected: RIPE Atlas
Timeline · 4 updates
  1. investigating Mar 11, 2026, 02:11 PM UTC

    A part the RIPE Atlas probe population is unable to connect to our infrastructure. We're investigating the issue.

  2. identified Mar 11, 2026, 02:28 PM UTC

    We identified the root cause of the issue and applied a fix, probes are connecting again.

  3. monitoring Mar 11, 2026, 03:42 PM UTC

    A fix has been implemented and we're monitoring the situation.

  4. resolved Mar 12, 2026, 08:03 AM UTC

    This 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 problem and would have been detected and resolved before it affected the probe population. However, independently of this, and as part of our normal software development process, we rolled out upgrades to our controlling infrastructure, which caused most of the probes to disconnect and try to re-register with the system. This is normal and expected - but in this case the registration server was not ready to answer them, and as a result they were unable to immediately re-join.

Read the full incident report →

Major March 3, 2026

Increased error rate with RIPEstat

Detected by Pingoru
Mar 03, 2026, 06:50 AM UTC
Resolved
Mar 03, 2026, 02:04 PM UTC
Duration
7h 14m
Affected: RIPEstat
Timeline · 3 updates
  1. investigating Mar 03, 2026, 06:50 AM UTC

    We are experiencing issues with RIPEstat since ~02:17 UTC. We are investigating and will update this announcement once we know more.

  2. monitoring Mar 03, 2026, 08:26 AM UTC

    We have mitigated the issue and will continue to monitor the situation closely. We will share an update when it has been fully resolved.

  3. resolved Mar 03, 2026, 02:04 PM UTC

    The 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 connections were flushed and the issue resolved.

Read the full incident report →

Major February 25, 2026

RIPE Atlas API and user interface are currently unavailable

Detected by Pingoru
Feb 25, 2026, 09:37 PM UTC
Resolved
Feb 26, 2026, 07:07 AM UTC
Duration
9h 30m
Affected: RIPE Atlas
Timeline · 4 updates
  1. investigating Feb 25, 2026, 09:37 PM UTC

    We are currently investigating this issue.

  2. identified Feb 25, 2026, 09:40 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 25, 2026, 09:47 PM UTC

    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.

  4. resolved Feb 26, 2026, 07:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 19, 2026

RIPE Database Mail Update Failures

Detected by Pingoru
Feb 19, 2026, 08:00 AM UTC
Resolved
Feb 19, 2026, 11:05 AM UTC
Duration
3h 4m
Affected: RIPE Database
Timeline · 4 updates
  1. investigating Feb 19, 2026, 08:00 AM UTC

    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).

  2. investigating Feb 19, 2026, 08:01 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 19, 2026, 08:01 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 19, 2026, 11:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 17, 2026

RIPE Database Update Failures

Detected by Pingoru
Feb 17, 2026, 01:28 PM UTC
Resolved
Feb 17, 2026, 01:28 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 17, 2026, 01:28 PM UTC

    Between approximately 12:04 to 12:16 CET today, there were some failures updating the RIPE database. We are investigating the cause(s).

Read the full incident report →

Minor February 14, 2026

RIS RRC05 and RRC07 — data processing issues

Detected by Pingoru
Feb 14, 2026, 09:58 PM UTC
Resolved
Feb 16, 2026, 02:40 PM UTC
Duration
1d 16h
Affected: RIS (Routing Information Service)
Timeline · 4 updates
  1. investigating Feb 14, 2026, 09:58 PM UTC

    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.

  2. monitoring Feb 14, 2026, 10:05 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Feb 14, 2026, 10:08 PM UTC

    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.

  4. resolved Feb 16, 2026, 02:40 PM UTC

    We completed our checks and found no data issues. This incident has been resolved.

Read the full incident report →

Major February 10, 2026

Failing Updates

Detected by Pingoru
Feb 10, 2026, 12:19 PM UTC
Resolved
Feb 11, 2026, 11:03 AM UTC
Duration
22h 44m
Affected: RIPE Database
Timeline · 3 updates
  1. investigating Feb 10, 2026, 12:19 PM UTC

    WHOIS is facing issues when trying to update

  2. monitoring Feb 10, 2026, 12:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 11, 2026, 11:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 5, 2026

High Error Rates for RIPEstat API Endpoints

Detected by Pingoru
Feb 05, 2026, 04:35 PM UTC
Resolved
Feb 09, 2026, 05:03 PM UTC
Duration
4d
Affected: RIPEstat
Timeline · 6 updates
  1. investigating Feb 05, 2026, 04:35 PM UTC

    We observe a high error rate for RIPEstat. We are currently investigating the issue.

  2. identified Feb 05, 2026, 04:41 PM UTC

    The issue is a shift in API traffic, leading to a > 10000% increase in traffic to some specific endpoints compared to the 7 day average. We will apply rate-limits to mitigate the issue.

  3. monitoring Feb 05, 2026, 09:36 PM UTC

    We have implemented a mitigation and are monitoring the results. We will provide the next update on the morning of 6 February.

  4. monitoring Feb 06, 2026, 11:05 AM UTC

    We experienced elevated error rates overnight. Following a new intervention, the error rate and latency have now returned to normal levels. We continue to monitor for any further issues.

  5. monitoring Feb 06, 2026, 11:05 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Feb 09, 2026, 05:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track RIPE Network Coordination Centre downtime and outages?

Pingoru polls RIPE Network Coordination Centre's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when RIPE Network Coordination Centre reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track RIPE Network Coordination Centre alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring RIPE Network Coordination Centre for free

5 free monitors · No credit card required