- Detected by Pingoru
- Oct 09, 2026, 03:12 PM UTC
- Resolved
- Oct 10, 2026, 07:53 AM UTC
- Duration
- 16h 40m
Affected: APICharger backend
Timeline · 3 updates
-
investigating Oct 09, 2026, 03:12 PM UTC
We are investigating increased latency affecting communication between chargers and Zaptec Cloud Services.
-
monitoring Oct 09, 2026, 03:14 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 10, 2026, 07:53 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2026, 05:49 AM UTC
- Resolved
- Oct 08, 2026, 08:00 AM UTC
- Duration
- 2h 11m
Affected: Zaptec App
Timeline · 4 updates
-
investigating Oct 08, 2026, 05:49 AM UTC
The Zaptec app's charging history isn't working as intended. We are currently investigating this issue
-
identified Oct 08, 2026, 06:36 AM UTC
The charging history in the Zaptec app is currently not working as intended. A fix is being worked on, and this will be resolved in an upcoming app version.
-
monitoring Oct 08, 2026, 07:24 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 08, 2026, 08:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2026, 06:33 PM UTC
- Resolved
- Oct 03, 2026, 06:21 AM UTC
- Duration
- 11h 48m
Affected: Charger backendOCPP
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2026, 06:01 AM UTC
- Resolved
- Oct 02, 2026, 07:56 AM UTC
- Duration
- 1h 55m
Affected: General
Timeline · 5 updates
-
investigating Oct 02, 2026, 06:01 AM UTC
We are currently unable to receive phone calls to our Support department. We are investigating the issue and will provide updates as soon as more information is available. In the meantime, you can still contact us by email via our form https://www.zaptec.com/company/contact#hubspot-items We also have documents and self-help at our knowledge base https://help.zaptec.com/
-
investigating Oct 02, 2026, 06:28 AM UTC
We are continuing to investigate this issue.
-
identified Oct 02, 2026, 07:50 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 02, 2026, 07:51 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 02, 2026, 07:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 02:42 PM UTC
- Resolved
- Oct 02, 2026, 05:04 AM UTC
- Duration
- 14h 22m
Affected: Portal
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2026, 11:26 AM UTC
- Resolved
- Oct 01, 2026, 07:15 AM UTC
- Duration
- 6d 19h
Affected: OCPPPortal
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2026, 10:04 AM UTC
- Resolved
- Sep 11, 2026, 11:18 AM UTC
- Duration
- 1h 14m
Affected: Portal
Timeline · 3 updates
-
investigating Sep 11, 2026, 10:04 AM UTC
We are currently experiencing issues in Zaptec Portal where changing electrical settings under Power Management may not work as expected. Some logs may also fail to load. Our team is investigating and working on a resolution. We apologise for the inconvenience and will provide updates as soon as we have more information.
-
monitoring Sep 11, 2026, 10:47 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 11, 2026, 11:18 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 02:38 PM UTC
- Resolved
- Sep 04, 2026, 03:35 PM UTC
- Duration
- 56m
Affected: OCPP
Timeline · 2 updates
-
monitoring Sep 04, 2026, 02:38 PM UTC
We are recovering from an incident that caused delays in processing charger updates and affected some OCPP integrations. Our services are available, and delayed information is being processed. Some updates may continue to be delayed while the system catches up. We are monitoring the recovery closely and apologise for the inconvenience.
-
resolved Sep 04, 2026, 03:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 08:29 AM UTC
- Resolved
- Sep 11, 2026, 10:47 AM UTC
- Duration
- 7d 2h
Affected: Portal
Timeline · 4 updates
-
identified Sep 04, 2026, 08:29 AM UTC
We are currently experiencing an issue with charge report generation in the Zaptec Portal. When attempting to generate a charge report, the report may return no data. We have identified the cause of the issue and are actively working on a fix. The current expected resolution timeframe is early next week. We will provide another update as soon as we have more information.
-
identified Sep 07, 2026, 08:15 AM UTC
We are continuing to work on a fix for this issue.
-
identified Sep 10, 2026, 12:51 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Sep 11, 2026, 10:47 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2026, 04:16 PM UTC
- Resolved
- Aug 21, 2026, 11:30 AM UTC
- Duration
- 1d 19h
Affected: PortalZaptec App
Timeline · 7 updates
-
investigating Aug 19, 2026, 04:16 PM UTC
We are currently investigating this issue.
-
identified Aug 19, 2026, 06:20 PM UTC
The issue has been identified, and a fix is currently being implemented. If you attempt to authorise charging in the Zaptec app, the app may not update immediately. Charging may begin as expected, but the app could continue to show the status as “Authorising.” Navigating away from the charging view and then returning should refresh the status.
-
monitoring Aug 19, 2026, 07:36 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 19, 2026, 08:18 PM UTC
Some users may still experience delayed status updates in the Zaptec app when attempting to authorize charging. Charging may begin as expected, but the app could continue to show the status as “Authorizing.” If this occurs, navigating away from the charging view and then returning should refresh the status. We may continue to see intermittent occurrences overnight while we monitor the situation. Thank you for your patience.
-
monitoring Aug 20, 2026, 11:23 AM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 21, 2026, 11:30 AM UTC
This incident has been resolved.
-
postmortem Aug 21, 2026, 11:31 AM UTC
On 19th aug approx 17:30 CEST, we observed issues with chargers on OCPPCloud having trouble. This was caused by some services having communication issues with one of our messaging services, causing it to overflow and preventing new messages from being sent. The issue happens intermittently and throughout the period until mitigation. The service providing live updates to UI \(app and portal\) was scaled down roughly in the time periods below, pending investigation and for mitigation being prepared and applied. 19\.aug 18:00 - 20.aug 09:00 CEST 20\.aug 23:00 - 21.aug 09:00 CEST A fix has been implemented and services are now recovered and operational. The root cause is still unknown and we are still investigating what causes this to happen.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 08:58 AM UTC
- Resolved
- Aug 21, 2026, 08:20 AM UTC
- Duration
- 6d 23h
Affected: Zaptec App
Timeline · 3 updates
-
identified Aug 14, 2026, 08:58 AM UTC
We have identified an issue in the Zaptec app that causes the app language to be set to English for all users. Our team is implementing a fix, and we will provide an update as soon as it is available.
-
monitoring Aug 21, 2026, 08:19 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 21, 2026, 08:20 AM UTC
The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 02:31 PM UTC
- Resolved
- Jul 27, 2026, 04:18 PM UTC
- Duration
- 1h 46m
Affected: Cellular connection
Timeline · 4 updates
-
investigating Jul 27, 2026, 02:31 PM UTC
We are currently investigating this issue.
-
monitoring Jul 27, 2026, 02:53 PM UTC
Currently there is a drop of online chargers in Europe that is connected to LTE-M. This is out of our control, but we are monitoring the situation.
-
resolved Jul 27, 2026, 04:18 PM UTC
This incident has been resolved.
-
postmortem Jul 27, 2026, 04:18 PM UTC
Between approximately \*\*15:55 and 17:30 CEST\*\* today, some customers experienced charger connectivity issues, including chargers appearing offline and delayed updates. Service has now recovered and we are continuing to monitor closely. Some delayed updates may continue temporarily while devices replay buffered data. We are still investigating the underlying root cause together with relevant infrastructure/network providers. We're sorry for the disruption
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 10:59 AM UTC
- Resolved
- Jul 21, 2026, 01:12 PM UTC
- Duration
- 2h 13m
Affected: General
Timeline · 4 updates
-
investigating Jul 21, 2026, 10:59 AM UTC
We are currently investigating the issue. In the meantime, please visit our Help Center for guidance and support. https://help.zaptec.com/
-
identified Jul 21, 2026, 11:28 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 21, 2026, 12:30 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 21, 2026, 01:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 06:57 AM UTC
- Resolved
- Jun 10, 2026, 09:13 AM UTC
- Duration
- 2h 15m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 03, 2026, 09:07 PM UTC
- Resolved
- May 04, 2026, 05:57 AM UTC
- Duration
- 8h 50m
Affected: Charger backend
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 08:50 AM UTC
- Resolved
- Apr 29, 2026, 10:14 AM UTC
- Duration
- 1h 24m
Affected: General
Timeline · 3 updates
-
investigating Apr 29, 2026, 08:50 AM UTC
We are currently investigating this issue.
-
monitoring Apr 29, 2026, 09:21 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 29, 2026, 10:14 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 08:07 PM UTC
- Resolved
- Mar 13, 2026, 07:13 AM UTC
- Duration
- 11h 5m
Affected: Cellular connection
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 07:45 AM UTC
- Resolved
- Feb 16, 2026, 08:19 AM UTC
- Duration
- 34m
Affected: Portal
Timeline · 2 updates
-
investigating Feb 16, 2026, 07:45 AM UTC
We've received reports of issues creating new installations in the Zaptec Portal. We are investigating this issue.
-
resolved Feb 16, 2026, 08:19 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 11:30 PM UTC
- Resolved
- Feb 13, 2026, 11:30 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 09:29 AM UTC
- Resolved
- Feb 17, 2026, 02:19 PM UTC
- Duration
- 6d 4h
Affected: Zaptec App
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 07:53 AM UTC
- Resolved
- Jan 28, 2026, 09:15 AM UTC
- Duration
- 1h 21m
Affected: General
Timeline · 4 updates
-
investigating Jan 28, 2026, 07:53 AM UTC
We are currently investigation the issue, contact us here: https://forms.atender.com/form/b06xo3dlmls-copy-1768225820551?lang=en
-
identified Jan 28, 2026, 08:02 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jan 28, 2026, 08:10 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 28, 2026, 09:15 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 05:06 PM UTC
- Resolved
- Jan 17, 2026, 10:08 AM UTC
- Duration
- 17h 2m
Affected: OCPP
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:08 AM UTC
- Resolved
- Dec 05, 2025, 11:58 AM UTC
- Duration
- 2h 50m
Affected: General
Timeline · 3 updates
-
investigating Dec 05, 2025, 09:08 AM UTC
Due to 3rd party service being down, our support systems are currently unavailable. This means that our customers can't reach our support. This is currently out of our control and we are monitoring the situation. All other services are operational. https://www.cloudflarestatus.com/
-
monitoring Dec 05, 2025, 09:24 AM UTC
A fix has been implemented by the 3rd party service. We will continue to monitor.
-
resolved Dec 05, 2025, 11:58 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 11:45 AM UTC
- Resolved
- Dec 04, 2025, 01:38 PM UTC
- Duration
- 1h 52m
Affected: Cellular connection
Timeline · 3 updates
-
monitoring Dec 04, 2025, 11:45 AM UTC
Currently there is a drop of online chargers in Denmark that is connected to LTE-M. This is out of our control, but we are monitoring the situation.
-
monitoring Dec 04, 2025, 12:31 PM UTC
Connections are improving. We will still monitor the situation.
-
resolved Dec 04, 2025, 01:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 11:49 AM UTC
- Resolved
- Nov 18, 2025, 02:01 PM UTC
- Duration
- 2h 11m
Affected: PortalZaptec App
Timeline · 4 updates
-
investigating Nov 18, 2025, 11:49 AM UTC
Due to 3rd party services being down, users are unable to log in to Zaptec Portal and app. This is a 3rd party issue, and it is currently out of our control. We are monitoring for updates.
-
investigating Nov 18, 2025, 01:26 PM UTC
The issue appears to be resolved from the 3rd party, and users are able to log in to our services. We will continue to monitor for now.
-
monitoring Nov 18, 2025, 01:26 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 18, 2025, 02:01 PM UTC
This incident has been resolved.
Read the full incident report →