OCPP disconnections

This incident has been resolved.

OCPP connections have now been recovered. We are now monitoring the results.

We are still working on restoring the OCPP connections.

Earlier today we deployed an update to our API. After a short time it was noticed that this carried an issue, and we decided to roll back the API to a previous version. Unfortunately and accidentally, the rollback was done to a version of the API that carried the issue seen a couple of weeks ago, which caused the issue to repeat.

The API has now been reverted to the correct version (i.e. the one running the morning, before today’s deployment). This makes the API endpoints behave as normal, without leading to data loss. Unfortunately some data might have been corrupted if the endpoints were used between 14:00 and 15:20 CEST. We are working to restore this now using the same procedure as the one used last time. Since we know exactly what happened and how to address the situation, we expect a faster turnaround on this problem.

There have been a data corruption incident today that led some customers' installations to lose the URL specifying connectivity to their OCPP central system. We are currently working on restoring this data.
If you have the ability of re-setting the OCPP URL, this will also re-establish the OCPP connection.