Is Zaptec down?
Last checked 1m agoNo incidents right now.
Zaptec is operational right now. Last checked 1m ago; the most recent incident resolved 4d ago.
Real-time Zaptec status, recent outages, and incident history — pulled directly from Zaptec's official status page at https://zaptec.statuspage.io every 5 minutes. Pingoru tracks 11 Zaptec services and has captured 7 incidents in the last 90 days (98.28% uptime). Get email, Slack, Discord, or webhook alerts the moment Zaptec reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- PortalPortal
Timeline · 4 updates
- investigating · Jun 10, 2026, 06:57 AM UTC
There are currently some issues saving changes on charger level in the Zaptec Portal. Changes on installation level still works as expected. We are investigating this issue.
- identified · Jun 10, 2026, 07:08 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jun 10, 2026, 07:29 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 10, 2026, 09:13 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- General
Timeline · 5 updates
- investigating · May 27, 2026, 09:47 AM UTC
We are currently investigating this issue.
- monitoring · May 27, 2026, 10:40 AM UTC
A fix has been implemented and we are monitoring the results.
- investigating · May 27, 2026, 11:04 AM UTC
We are currently investigating this issue.
- monitoring · May 28, 2026, 05:29 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 04, 2026, 06:47 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- General
Timeline · 12 updates
- investigating · May 18, 2026, 07:42 AM UTC
We are currently experiencing disruptions on our phone lines. In the meantime, we recommend reaching out to us via the web form or using our chat in the Zaptec Help Center: https://help.zaptec.com/
- identified · May 18, 2026, 10:12 AM UTC
The issue has been identified and a fix is being implemented.
- identified · May 18, 2026, 01:02 PM UTC
The issue has been identified and a fix is being implemented. In the meantime, we recommend reaching out to us via the web form or using our chat in the Zaptec Help Center: https://help.zaptec.com/
- identified · May 18, 2026, 06:05 PM UTC
We have identified the issue and are currently implementing a fix. Our support phone is still not operating at full capacity, so in the meantime, we recommend contacting us via the web form or using the chat in the Zaptec Help Center: https://help.zaptec.com/
- identified · May 19, 2026, 05:28 AM UTC
We have identified the issue and are currently implementing a fix. Our support phone is still not operating at full capacity, so in the meantime, we recommend contacting us via the web form or using the chat in the Zaptec Help Center: https://help.zaptec.com/
- monitoring · May 19, 2026, 07:32 AM UTC
A fix has been implemented, and we are monitoring the results on Phone support services. You can always reach us with a web form or using chat in the Zaptec Help Center: https://help.zaptec.com
- monitoring · May 20, 2026, 05:39 AM UTC
We are continuing to monitor for any further issues.
- investigating · May 20, 2026, 12:20 PM UTC
We are currently experiencing disruptions on our Support phone lines. In the meantime, we recommend reaching out to us via the web form or using our chat in the Zaptec Help Center: https://help.zaptec.com/
- identified · May 20, 2026, 01:20 PM UTC
The issue has been identified and a fix is being implemented.
- identified · May 20, 2026, 01:53 PM UTC
The issue has been identified, and a fix is being implemented. In the meantime, we recommend reaching out to us via the web form or using our chat in the Zaptec Help Center: https://help.zaptec.com/
- monitoring · May 21, 2026, 06:31 AM UTC
A fix has been implemented, and we are monitoring the results on Phone support services. You can always reach us with a web form or using chat in the Zaptec Help Center: https://help.zaptec.com
- resolved · May 22, 2026, 12:03 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- General
Timeline · 5 updates
- investigating · May 15, 2026, 10:30 AM UTC
We are currently investigating this issue.
- investigating · May 15, 2026, 11:30 AM UTC
We are currently experiencing disruptions on our phone lines. In the meantime, we recommend reaching out to us via the web form or using our chat in the Zaptec Help Center: https://help.zaptec.com/
- identified · May 15, 2026, 11:54 AM UTC
The problem has been identified, and the fix is being implemented. In the meantime, we recommend reaching out to us via the web form or using our chat in the Zaptec Help Center: https://help.zaptec.com/
- monitoring · May 15, 2026, 12:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · May 15, 2026, 12:46 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Charger backend
Timeline · 4 updates
- investigating · May 03, 2026, 09:07 PM UTC
The team is investigating the issue
- monitoring · May 03, 2026, 09:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · May 04, 2026, 05:57 AM UTC
This incident has been resolved.
- postmortem · May 04, 2026, 12:02 PM UTC
``` # Incident Report – Increased Latency in Charger Data Processing Pipeline # Description On the evening of 3 May 2026, our systems experienced increased latency in the internal pipeline that delivers charger data to downstream services. As a result, processing of the data was delayed. This led to: - Charging sessions starting with delays of up to approximately 20 minutes. - Our public charger-state API experiencing elevated error rates and timeouts for part of the incident window. The issue has since been resolved, and systems have returned to normal operation. # Timeline (Oslo time) ## May 3, 2026 21:00 – Internal monitoring detected that one of our downstream services was falling behind in processing incoming charger data, indicating increased delay in the data pipeline. 21:08 – An alert was triggered and the on-call engineer began investigation. 21:30 – The team identified increased latency in the internal data delivery path responsible for sending charger data to our processing services. 21:58 – A support case was opened with our infrastructure provider for further investigation of the upstream latency. 22:18 As a protective measure to reduce load and avoid excessive state-change events, one of our internal charger state services was temporarily scaled down. As a side effect, our public charger-state API, which depends on this service, started returning more HTTP 500 errors and timeouts as clients cancelled long-running requests. 22:43 – Internal metrics indicated that the downstream processing delay had returned to normal levels. 22:53 – Latency in the internal data delivery path decreased back to normal. 23:07 – Initial status update communicated internally. 23:15 – The previously scaled-down charger state service was restored to normal capacity. 23:16 – The public charger-state API returned to normal behaviour. 23:30 – Scope of the incident was refined and communicated. 23:39 – The backlog of delayed charger data was fully processed. ## May 4, 2026 7:57– The incident was marked as resolved. # Root Cause An internal messaging pipeline responsible for delivering charger data exhibited significantly increased latency. This caused many chargers to repeatedly switch between offline and online states in our systems, generating a high volume of state-change events for downstream components. The additional load from these state changes, combined with the bursty delivery of delayed data, led to further processing delays and directly impacted the charger-state API. # Follow-Up Actions Adding more targeted monitoring and alerting on the latency within our internal data pipeline, so we can identify and mitigate similar issues more quickly. Improving our charger state service so it can detect when there are delays in upstream data delivery and temporarily pause or adjust offline/online detection to avoid large numbers of false transitions. We are continuing to work with our infrastructure provider to better understand the underlying cause of the upstream latency and to reduce the likelihood of recurrence. ```
Latest: ``` # Incident Report – Increased Latency in Charger Data Processing Pipeline # Description On the evening of 3 May 2026, our systems experienced increased latency in the internal …
-
See the full Zaptec outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Zaptec outage history →Or sign up free to get alerts when Zaptec breaks · 10 free monitors · No credit card
- Started Jun 10, 2026, 06:57 AM UTC · Resolved Jun 10, 2026, 09:13 AM UTC · 2h 15m
- Support Phone service disruption ResolvedStarted May 27, 2026, 09:47 AM UTC · Resolved Jun 04, 2026, 06:47 AM UTC · 7d 20h
- Support Phone service disruption ResolvedStarted May 18, 2026, 07:42 AM UTC · Resolved May 22, 2026, 12:03 PM UTC · 4d 4h
- Support Phone service disruption ResolvedStarted May 15, 2026, 10:30 AM UTC · Resolved May 15, 2026, 12:46 PM UTC · 2h 16m
- Started May 03, 2026, 09:07 PM UTC · Resolved May 04, 2026, 05:57 AM UTC · 8h 50m
- Started Apr 29, 2026, 08:50 AM UTC · Resolved Apr 29, 2026, 10:14 AM UTC · 1h 24m