Data-Incident-Nov25 on Centre for Environmental Data Analysis

Data Incident - New Year Update

Thu, 22 Jan 2026 14:30:00 +0000

Dear users, We have an update to share with you regarding our progress on the Archive data incident that occurred on the 18th November 2025.

Data Incident Christmas Update

Fri, 19 Dec 2025 10:30:00 +0000

This is an update on the Archive data incident that occurred on 18th November 2025 - see previous updates here.

We are making good progress with recovering data back into the Archive and have made significant progress. Over 1.6 Petabytes of data have been recovered to a holding area - 1.3 Petabytes of this has now been moved to its correct location in the Archive. Most of this should now be available to users - we are doing some final checks for data permissions.

Archive Incident - List of impacted data directories

Fri, 28 Nov 2025 12:00:00 +0000

Dear users, We now have a list of data directories that have been affected by the data incident on 18th November 2025. You can see the top-level list below.

Archive Incident - Data Ingest Resuming

Tue, 25 Nov 2025 12:00:00 +0000

Dear users,

We have another update regarding the CEDA Archive data incident that occurred on 18th November 2025. Please read the key points below:

CEDA Archive Incident update & FAQ

Mon, 24 Nov 2025 12:00:00 +0000

Please note that we are processing incoming data where needed, but we are not presently depositing to the archive. Please hold off any large deposits for now and keep in touch with your CEDA point of contact to coordinate delivery.

Dear JASMIN and CEDA users, we have an update on the CEDA Archive incident that occured on Tuesday the 18th of November. Some common questions are answered below including how to request which data you’d like to be a priority for recovery.

CEDA ARCHIVE INCIDENT - 18th November 2025

Wed, 19 Nov 2025 16:30:00 +0000

Dear JASMIN and CEDA users,

At approximately 10:02 on 18th November 2025, during the migration of data in the CEDA archive, a mistake was made which resulted in some data being deleted from the archive. The issue was identified at approximately 12:07, the archive was locked down preventing further loss by approximately 12:25, and the incident was fully diagnosed by 14:00.