Previous incidents
Auto-restart of services
Resolved Mar 31 at 03:00am CEST
The internal health checks of the service discovered an error and restarted the service as a precaution. The underlaying problem is identified and a solution is being worked on.
Release
Resolved Feb 08 at 12:57pm CET
The service was released which caused a few seconds of downtime. The new zero-downtime deployments are being introduced which will solve this issue.
Infrastructure upgrade
Resolved Jan 25 at 09:02am CET
Our cloud infrastructure provider has been upgrading services which causes a restart of services.
Infrastructure upgrade
Resolved Jan 24 at 08:02am CET
There was an upgrade in the cloud infrastructured which triggered a restart of the service. This caused about 5 minutes of downtime.
Unhealthy services
Resolved Jan 20 at 08:08am CET
Our hub service was restarted, which caused websockets to disconnect. The underlying infrastructure was rebooted as part of an upgrade. Failover was working properly and the services was available immediatly after the disconnect.
Cloud infrastructure refresh
Resolved Jan 11 at 02:10am CET
Our cloud environment experienced a infrastructure update which caused downtime of about 10 seconds. We added a monitor on our dashboard to see if this happens and mitigate when necessary.