Yeah, occasionally the throughput of SciHub is having issues and a backlog happens therefore. Sentinel-1 ingestion comes after Sentinel-2 is complete, so issues show there first.

We are looking into it and trying to mitigate it, but not fully in our hands…

Note that situation has improved quite a bit in the last 24 hours. It seems our tweaks helped… until next time…

Note that the roda end-point is tied to CloudFront and there is quite some caching there. But if you go to
https://roda.sentinel-hub.com/sentinel-s1-l1c/GRD/2020/3/18/

you will see some products.

Indeed the backlog seems to have been absorbed, thanks!

Just to make sure I understand correctly your comment, you mean that since roda is tied to CloudFront, calls such as https://roda.sentinel-hub.com/sentinel-s1-l1c/GRD/2020/3/ may not be up to date due to caching, but if I hit directly this kind of URL https://roda.sentinel-hub.com/sentinel-s1-l1c/GRD/2020/3/18/IW/DV/S1A_IW_GRDH_1SDV_20200318T005526_20200318T005556_031723_03A878_20EF/, caching should not be an issue? Or did I misunderstand?

I’m asking because I wrote a script that goes on Scihub to get the names of the latest SAFEs, and then for each SAFE builds a URL such as the one above and queries it to check if the SAFE is available on AWS or not. However if you tell me that the response of this endpoint might lag behind AWS S3 due to caching, this would be an issue in my approach.

I am not an expert in CloudFront, but I think you are right - if you go to URL directly, it should be there.

The best option obviously would be to go directly to S3 API - this would be certain.