Previous incidents

Our cloud infrastructure provider has been upgrading services which causes a restart of services.

There was an upgrade in the cloud infrastructured which triggered a restart of the service. This caused about 5 minutes of downtime.

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.

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.

A new version of the portal was released. Zero-downtime deployments for the portal are planned.

Due to a change of the specific health endpoint of our API service, it was marked as offline which was not the case. We changed the health endpoint and it is showing the correct status again.