Zaptec had 38 outages in the last 2 years totaling 175h 1m of downtime — averaging 1.6 incidents per month.
There were 38 Zaptec outages since February 6, 2025 totaling 175h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.
You may see your charging station appear as offline, even though it's online. We are currently looking into this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing intermittent issues with WebApi, which are under investigation.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently seeing some delays in WebApi affecting Portal
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Zaptec authentication is not working as intended. We are currently investigation the situation.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are back to normal, but we will keep monitoring the situation.
Things have been running stable since a fix were implemented, and incident is resolved. We will still use the upcoming days to find out what caused it to happen.
We are currently seeing drops in OCPP connections. We are investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently seeing a drop in connections for our charging stations. This seems to be an external issue, but we are investigating the issue.
Connections are already ramping up. We are still investigating what might have caused it.
Connections have stabilized at a normal level. We will keep monitor the situation.
Connections have been stable for a couple of hours now. This incident have been resolved.
On 11th of May around 03:15 (CET), the OCPP Bridge Proxy service, supporting the OCPP Bridge service, experienced a transient network issue causing parts of it to restart. The restarted instances had problems communicating with the backend service, resulting in approximately 25% of devices disconnecting across the board. As no direct root cause could be identified at the time, and with a 75% stable connection rate, it was decided to perform a full restart of the OCPP Bridge Proxy service at 08:18 (CET). This resolved the issue with the backend service, and we observed a steady recovery in connected devices, returning to 100% within 30 minutes. During this incident, there were issues with the internal alerting process responsible for notifying the team to update the status page. As a result, no status was created during the incident. This gap have been identified and addressed.
We are currently investigating this issue.
We are continuing to investigate this issue.
The Zaptec Portal is unresponsive, and the Zaptec app is running slowly. We are actively investigating the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results. You may still experience some delay.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On Friday 14th of February at 12:35 CET the cloud-based Sense service, which provides Automatic Power Management \(APM\) functionality to Zaptec installations, began running below normal capacity, leading to a disruption of functionality. The degradation was identified at 12:37 CET. Our engineers started investigating logs and metrics for the service. We identified the root cause as an overlooked manual configuration change. This was restored to original state and the service was again operational at 13:55 CET. We have updated our monitoring to identify similar problems much faster in the future, and are reviewing our processes to prevent manual configurations from persisting in our production environment.