Earthdata Forum

I have been downloading 12 months of level-3 binned files for various products on July 12 and 13.  I first use wget to download a list with sha1sums, then extract the filenames for each product into a list.  Using the (normally reliable) obdaac_download.py, Whoopsed on a few files for some products.  For example:

% obdaac_download.py --filelist SNPP_VIIRS.2019.PAR.list
Whoops...problem retrieving V20192132019243.L3b_MO_SNPP_PAR.nc (received status 404)
Whoops...problem retrieving V20192442019273.L3b_MO_SNPP_PAR.nc (received status 404)
% obdaac_download.py V20192442019273.L3b_MO_SNPP_PAR.nc
Whoops...problem retrieving V20192442019273.L3b_MO_SNPP_PAR.nc (received status 404)
% obdaac_download.py V20192442019273.L3b_MO_SNPP_PAR.nc
Whoops...problem retrieving V20192442019273.L3b_MO_SNPP_PAR.nc (received status 404)
% obdaac_download.py V20192442019273.L3b_MO_SNPP_PAR.nc
% sha1sum -c V20192442019273.L3b_MO_SNPP_PAR.sha1sum
V20192442019273.L3b_MO_SNPP_PAR.nc: OK
Downloading some of the files with "(received status 404)" using the level-3 browser was also successful.

Both of those files are available (just pulled them down with that reliable script :grin:)
Those files reside on two different storage devices, but it's possible there was an intermittent networking issue.

BTW, all data access is via the getfile API, so the download  working for the L3 browser but not a prior attempt with the obdaac_download script strongly suggests a temporary whoops.
If it happens more than irregularly, or is persistent, definitely let us know. 

Sean