Requests to a published site were repeatedly responded with a 404. After purging the CDN cache, the responses were correct again.
The problem was caused by a backend service that was temporarily unavailable. Unfortunately it was internally handled as a 404, which got cached by the CDN. So even after the backend could render the site correctly again, it was still served as 404.
We will improve the internal error handling so that internal errors will not be cached.