ECMWF AWS issues? (Oct 30th) #487
Replies: 5 comments 17 replies
|
I am also having issues trying to download grib files from their aws buckets as well for this latest cycle |
|
Google seems to work, so I submitted this PR to add it as an optional source for ECMWF IFS and AIFS: #489. |
|
I'm having similar issues with IFS via AWS again. I first noticed it a few days ago and it seems to be ongoing but intermittent. Anyone else having problems? |
|
@karlwx I'm using a combination of Google and Azure at the moment. As far as I can tell, the data is available at more or less the same time. The performance in recent days via the ECMWF open data python interface has been acceptable. That said, in my own scripts I've been able to achieve much better performance by downloading up to 6 steps concurrently. However, I'm not yet confident about using this on a live server for several reasons. I've also tested with Herbie (that's why I'm here!) and found performance to be very similar, but I've not yet tried out FastHerbie which @williamhobs has suggested. |
|
This is good discussion. Side note: I just pushed a script to show download times for a model. If you come up with something better, please share it :) Downloads for IFS model$ uv run download_timer.py --model ifs --search ":t:"
Download Summary:
model='ifs', date=datetime.date(2026, 5, 4), search=':t:'
google █ 5.449 s (13 fields, 7.75 MB)
ecmwf ████████████████████▌ 14.629 s (13 fields, 7.75 MB)
aws █████████████████████▌ 15.036 s (13 fields, 7.75 MB)
azure ███████████████████████ 15.818 s (13 fields, 7.75 MB)
azure-waef ██████████████████████████████ 18.849 s (13 fields, 7.75 MB)
azure-scda ERROROf course, the download times are different every time you run the script and will vary by network. For IFS, the google source seems to be the quickest for the IFS model from what I've seen. For comparison, here is a benchmark for HRRR and GFS Downloads for HRRR model$ uv run download_timer.py --model hrrr --search ":TMP:"
Download Summary:
model='hrrr', date=datetime.date(2026, 5, 4), search=':TMP:'
nomads █ 2.338 s (7 fields, 5.27 MB)
aws █████▌ 2.766 s (7 fields, 5.27 MB)
azure ██████████ 3.221 s (7 fields, 5.27 MB)
google ██████████████████████▌ 4.368 s (7 fields, 5.27 MB)
pando2 ████████████████████████████ 4.903 s (7 fields, 5.27 MB)
pando ██████████████████████████████ 5.047 s (7 fields, 5.27 MB)Downloads for GFS model$ uv run download_timer.py --model gfs --search ":TMP:"
Download Summary:
model='gfs', date=datetime.date(2026, 5, 4), search=':TMP:'
azure █ 22.715 s (54 fields, 40.00 MB)
aws █████▌ 23.614 s (54 fields, 40.00 MB)
nomads ████████████████▌ 25.712 s (54 fields, 40.00 MB)
google ██████████████████████████████ 28.248 s (54 fields, 40.00 MB)
ncar_rda ERROR |
Uh oh!
There was an error while loading. Please reload this page.
Is anyone having issues getting data from ECMWF via AWS? I think it was working earlier today, but I've also been troubleshooting network issues all day...
For example,
(from https://herbie.readthedocs.io/en/stable/gallery/ecmwf_models/ecmwf.html)
returns a
JSONDecodeError: Expecting value: line 1 column 1 (char 0)error.Something more direct, like going after a grib file directly in my web browser, https://ecmwf-forecasts.s3.eu-central-1.amazonaws.com/20250802/00z/ifs/0p25/oper/20250802000000-0h-oper-fc.grib2, returns:
All reactions