When trying a potential fix for the 502 errors, one of the workers got stuck in an unexpected state, which made it return 404 errors.
This is now fixed.