Back to overview

Service restarted

May 16 at 11:42am CEST
Affected services
Websockets

Resolved
May 16 at 11:42am CEST

A service was automatically restarted after health checks, which caused the health check to fail. Chargers were still able to connect due to our failover configuration.