Resolved -
This incident has been resolved, postmortem will be posted when ready.
Mar 25, 12:16 CET
Update -
We are still monitoring the situation.
Mar 25, 09:39 CET
Update -
There is still full functionality. You may experience some minor delays, but all operations should work as expected. We are still monitoring the situation.
Mar 24, 15:26 CET
Monitoring -
Full functionality have been enabled to OCPP Bridge, and systems are running fine. You may experience some minor delays, but all operations should work as expected. We are still monitoring the situation.
Thank you for your patience.
Mar 24, 09:30 CET
Update -
After the rollback at 10:00, we do see improvements, but we are still operating with limited functionality. With this, all charging stations that are connected, will work as expected. But, if there are done any changes on installation level - updates from installations, circuits, and chargers, OCPP messages will not be received. This includes changes such as change to authentication mode, and the addition or removal of installations, circuits, or chargers from OCPP.
We are still working on a solution to this incident.
Mar 21, 11:48 CET
Investigating -
After enabling full functionality at 09:15, we do see some issues. We will roll back to limited functionality at 10:00 and keep investigating the issue.
Mar 21, 09:57 CET
Update -
As our systems have been running as expected since last update, we are going to enable full functionality to OCPP at 09.15.
Mar 21, 09:08 CET
Monitoring -
We are seeing improvements to OCPP bridge, and our systems are stable again after our latest deployment. However, OCPP have been deployed with limited functionality. With this, all charging stations that are connected, will work as expected. But, if there are done any changes on installation level - updates from installations, circuits, and chargers, OCPP messages will not be received. This includes changes such as change to authentication mode, and the addition or removal of installations, circuits, or chargers from OCPP.
We are actively monitoring the situation, working on a solution, and expect full functionality to be restored by tomorrow morning, with further improvements ongoing.
Mar 20, 17:10 CET
Update -
We still don't know the root cause, and will continue the investigation through the evening. Thank you for your patience.
Mar 20, 15:32 CET
Update -
Our development team is fully focused on identifying the root cause and working towards a resolution. While we are still investigating and do not yet have a definitive explanation, please rest assured that we have our best people on the case.
We will provide an update as soon as we have more clarity on the situation. Thank you for your patience and understanding.
Mar 20, 12:14 CET
Update -
It is still unclear what's causing the issues. We are continuing to investigate.
Mar 20, 10:20 CET
Update -
At this stage, we are still investigating the root cause of the issue and don’t have a definitive explanation yet. We will provide an update as soon as we have more clarity.
Mar 20, 09:06 CET
Update -
We will continue to investigate this issue today.
Mar 20, 07:39 CET
Update -
We will keep investigating this issue over the night.
Mar 19, 23:45 CET
Update -
We are continuing to investigate this issue.
Mar 19, 21:03 CET
Update -
We can see improvements on our systems as of now. But we are still investigating the issue.
Mar 19, 20:07 CET
Update -
We are continuing to investigate this issue.
Mar 19, 19:44 CET
Update -
We are continuing to investigate this issue.
Mar 19, 18:54 CET
Update -
We are continuing to investigate this issue.
Mar 19, 17:37 CET
Update -
More logging have been activated to track down the issue. We will continue to investigate.
Mar 19, 16:54 CET
Update -
We are still on top of this issue, and we will continue to investigate. As of now we have no ETA on when we expect the problem to be fixed, but we will update frequently.
Mar 19, 16:00 CET
Update -
We are still investigating this issue.
Mar 19, 15:02 CET
Update -
We are continuing to investigate this issue.
Mar 19, 13:27 CET
Update -
At 13:00 we will do a reboot of the OCPP Proxy. You will see chargers disconnect from the OCPP backend, but should recover shortly after.
Mar 19, 12:54 CET
Update -
We are continuing to investigate this issue.
Mar 19, 12:42 CET
Update -
We are still investigating this issue.
Mar 19, 11:14 CET
Update -
We are continuing to investigate this issue.
Mar 19, 10:07 CET
Investigating -
We are seeing an increase of BootNotifications being sent from our charging stations without any clear reason. We are currently investigating this issue.
Mar 19, 09:03 CET