Back to overview
Maintenance

502, 503 and 504 error on container

Feb 05 at 10:30am CET  –  Feb 07 at 10:00am CET
Affected services
DASHBOARD

Resolved
Feb 07 at 10:40am CET

The root cause of this issue has been identified and successfully resolved. As a result, all containers have been back online since last night, and services are operating as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding while we worked on the resolution. Please do not hesitate to reach out if you experience any further issues or require additional information.

Updated
Feb 06 at 05:45pm CET

A fix is currently being deployed across multiple containers. Some containers are coming back online, and we aim to resolve the root cause as soon as possible, which has already been identified.

Updated
Feb 06 at 12:02pm CET

We are currently identifying the root cause of these issues. A fix has been found and is already being rolled out to some containers. We appreciate your patience. At the moment there is no ETA yet.

Created
Feb 05 at 10:30am CET

At the moment, some of our containers are experiencing a 502, 503, or 504 error. We are aware of the issue and are working hard to resolve it. We appreciate your patience!