Previous incidents

The services were restarted and caused a few moments of downtime.

The service used to show the status has issues, the websocket service was working correctly.

As mentioned previously, we experience some downtime during a release. That's why those are scheduled at off-peek moments. This was one of those releases.

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.

After the deployment of one of our services that service did not start correctly. After restarting this service it worked again.

Because of the release of another dependent service the API was briefly unavailable.

The OCPI service was down for a brief second. The service was back up immediately after. This was resolved automatically.

A peek load of API calls was received and handled, although the auto-scaling took a few seconds to kick in. In those seconds the health check was performed and received an error.