3 ms·

I got the same. Three minutes later it suddenly worked. The content was then served by Fastly, so I guess it was their f-up.