Error downloading hourly daily data from ERA5 from 5 days ago

I've been facing this error issue for a few weeks when trying to download data from ERA5 rescan from 5 days ago. For example, today, the 23rd, the data from the 18th appears available for download, but when downloading via python it doesn't work, an error appears whenever I try to make this request, and this only occurs with the 5-day data ago, because if I try to download the data from 6 days ago (day 17 in this example), I can download it successfully. I repeat, this problem is not new and yes it has been happening for a few weeks! Please take a look at what might be going on.

This is the data I'm using: ERA5 hourly data on single levels from 1959 to present


I am attaching the script below which extracts directly from the copernicus website:

When trying to run it on your machine to test, replace the day with the date of 5 days ago, and then test with 6 days ago that you saw the error occur.

import cdsapi

c = cdsapi.Client()

‘product_type’: ‘reanalysis’,
‘format’: ‘netcdf’,
‘variable’: [
‘2m_temperature’, ‘sea_surface_temperature’, ‘total_precipitation’,
‘year’: ‘2022’,
‘month’: ‘07’,
‘day’: ‘18’,
‘time’: [
‘00:00’, ‘01:00’, ‘02:00’,
‘03:00’, ‘04:00’, ‘05:00’,
‘06:00’, ‘07:00’, ‘08:00’,
‘09:00’, ‘10:00’, ‘11:00’,
‘12:00’, ‘13:00’, ‘14:00’,
‘15:00’, ‘16:00’, ‘17:00’,
‘18:00’, ‘19:00’, ‘20:00’,
‘21:00’, ‘22:00’, ‘23:00’,
‘area’: [
90, -180, -90,

Hi Luiz,

There is a 5 day embargo on the download of ERA5T data, although currently for operational reasons the data may appear on the CDS forms before this embargo period has passed. Hence you need to make sure that your request only includes 'valid' dates for ERA5T data.

Hope that helps,



We are facing the same issue as in the original post. For instance, today (August 5), it is possible to download only the data up to July 30, while in the past the last day of the month was available the 5th of the next month. 

So, it seems that the embargo is now longer than 5 days, and this is a recent issue (I would say of the last month of so). Is this a conscious choice of ECMWF to extend the embargo, a side effect of some changes to the API or a temporal issues?

Any feedback would be appreciate, in order to plan if we need to rethink our real-time activities based on ERA5.


Hi, please see my comments at UserError: Restricted access to ERA5T. Please, check that that your date selection is valid. It was added on 18th August 2022.