Archive Incident - List of impacted data directories

Last modified on November 28, 2025 • 3 min read • 519 words

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.

If you are wanting to understand which data may be missing, please look at the list below in the first instance. It has been separated into types of data held in the archive: Earth Observation, Atmosphere and Climate, Oceanographic, Polar, Energy, and Geological.

Some of the larger volume datasets like Sentinel and CMIP have some significant gaps at present.

We are working on retrieving data from our routine back ups. We will initially focus on missing top level directories so that the structure of the Archive is complete. This will then allow us to progress quickly with the recovery of priority datasets.

We do have a full list of more specific directories that have been affected - but it is a long list so we recommend checking the shorter list (below) in the first instance: https://dap.ceda.ac.uk/badc/ARCHIVE_INFO/logical_paths_of_affected_data_nov2025.txt 

All affected directories in the archive are flagged with a “recovery_readme_nov2025.txt” file.

Please see the FAQ further down about how these directories map to datasets.

The “top-level” directories in the archive that were affected by the incident last week are given below. Please note: due to the way data are spread across storage, the list includes directories that are both completely and partially affected.

Earth Observation data  

/neodc/sentinel3a
/neodc/sentinel1a
/neodc/sentinel5p
/neodc/sentinel1b
/neodc/sentinel3b
/neodc/modis
/neodc/sentinel2b
/neodc/sentinel2a
/neodc/esacci
/neodc/sentinel_ard
/neodc/qa4ecv
/neodc/aatsr_multimission
/neodc/globalbedo_broadband_brdf
/neodc/caliop
/neodc/avhrr_gac
/neodc/nceo_ard
/neodc/iasi_metop_a
/neodc/eustace
/neodc/comet
/neodc/lsasaf
/neodc/gome2_metop_a
/neodc/arsf
/neodc/oltraj
/neodc/eocis
/neodc/slstr_calibration
/neodc/globalbedo_broadband_albedo
/neodc/tomcat_ozone
/neodc/tls
/neodc/surface_velocities_afar_rift
/neodc/sentinel3b
/neodc/sentinel2c
/neodc/oltraj
/neodc/ocean_reanalysis
/neodc/misr
/neodc/meris
/neodc/landsat8
/neodc/landmap
/neodc/iasi_metop_c
/neodc/iasi_metop_b
/neodc/gome2_metop_c
/neodc/gome2_metop_b
/neodc/globalbedo_broadband_brdf
/neodc/glas_veg_height
/neodc/forestscan
/neodc/fiduceo
/neodc/dcmex
/neodc/comet-cgps
/neodc/c3s_erb
/neodc/baci_ssv
/neodc/avhrr_gac
/neodc/avhrr_dundee
/neodc/avhrr3_metop_c

Atmospheric and climate data  

/badc/cmip6
/badc/eiscat
/badc/cmip5
/badc/ecmwf-era5
/badc/ukmo-nwp
/badc/msg
/badc/wcrp-ccmi
/badc/ukmo-nimrod
/badc/specs
/badc/apposite
/badc/ukmo-hadobs
/badc/woest
/badc/ukmo-metdb
/badc/ukmo-lidarnet
/badc/ukmo-charts
/badc/ukmo-assim
/badc/uk-decc-network
/badc/ukcp18
/badc/sonata
/badc/snowdon-gnss
/badc/smurphs
/badc/orchestra
/badc/openifs_at_home
/badc/ncas-wao
/badc/ncas-longterm-obs
/badc/ncas-cao
/badc/moya
/badc/mosaic-arctic
/badc/kilimanjaro-climate
/badc/ipcc-ddc-regions
/badc/icecaps-ace
/badc/hydro-jules
/badc/highresmip-derived
/badc/glocaem
/badc/gauge
/badc/evoflood
/badc/eucleia
/badc/deposited2023
/badc/deposited2022
/badc/deposited2021
/badc/deposited2019
/badc/deposited2018
/badc/auchencorth
/badc/ar6_sr15

Oceanographic data  

/bodc/BAS210037
/bodc/UOX220077
/bodc/BAS210038
/bodc/BAS210039
/bodc/SOC220065
/bodc/deposits01
/bodc/SOC210130
/bodc/SOC210128
/bodc/POL150147
/bodc/USO220011
/bodc/SMI230145
/bodc/SMI230145
/bodc/pol250716
/bodc/POL150147
/bodc/POL130189
/bodc/POL100124
/bodc/POL100124
/bodc/POL090139
/bodc/BGS230127
/bodc/BGS230126
/bodc/BGS220061

Polar data  

/pdc/GB-NERC-BAS-PDC-01730
/pdc/GB-NERC-BAS-PDC-01728

Energy data  

/edc/nuclear
/edc/efficiency

Geological data  

/ngdc/R001693-1

FAQ: How do I understand the impact on specific datasets? How will you inform users about this?

The CEDA Archive includes both small and very large datasets. This means that, coupled with the hierarchical structure we have, means the above directory list may relate to one or more datasets as listed in our data catalogue service ( https://catalogue.ceda.ac.uk  ).

Whilst users can discover datasets via the catalogue, we also know users go direct to parts of the archive (via https://data.ceda.ac.uk/)  , so in the first instance we wanted to make sure the affected directories were suitably flagged with the recovery_readme_nov2025.txt files. This ensures we are conveying the information to all users, regardless of how they get to the affected directories.

With this in place, our next step will be to add in a news banner on the catalogue records for the affected datasets to further inform users.