Zaptec Outage History

Started Oct 15, 2026, 08:41 PM UTC· resolved Oct 19, 2026, 06:18 AM UTC

1. investigating Oct 15, 2026, 08:41 PM UTC

   We are investigating increased latency affecting communication between chargers and Zaptec Cloud Services. You may experience that live updates in both Zaptec Portal and App is not working as intended.

2. investigating Oct 15, 2026, 09:21 PM UTC

   We have made changes to help keep services running as smoothly as possible overnight while we continue investigating increased latency affecting charger communication with Zaptec Cloud Services. At this time, live updates in Zaptec Portal and the Zaptec App may still be delayed or not work as intended. Charging behavior itself is expected to remain unaffected. We are sorry for the inconvenience this may cause. We will continue the investigation tomorrow morning and provide a further update then.

3. investigating Oct 16, 2026, 06:00 AM UTC

   We are continuing to investigate this issue.

4. monitoring Oct 16, 2026, 10:08 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Oct 19, 2026, 06:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 13, 2026, 08:00 PM UTC· resolved Oct 13, 2026, 11:55 PM UTC

1. resolved Oct 13, 2026, 08:00 PM UTC

   **Status:** Resolved **Duration:** 13 October 2026, 20:00 – 23:55 UTC (22:00 – 01:55 CEST) **Affected:** Zaptec chargers connected to a third-party charging operator or app (via OCPP) ## What happened On the evening of 13 October, a delay in Zaptec Cloud caused session-start messages to reach third-party charging operators 10–15 minutes late. Many operators rejected these late messages, and the affected charging sessions were stopped shortly after they began. Chargers managed only through the Zaptec app and portal could still charge. During the same period, live charger status in the Zaptec app and portal may have been delayed or outdated. ## Current status The issue is resolved. Service returned to normal at 23:55 UTC, and no action is needed from customers. If a charging session was stopped during the incident, starting a new session will work as usual. ## What we are doing We are working with our cloud provider to confirm the root cause. To prevent this from happening again, we are: - Adding monitoring to detect delays like this sooner We apologise for the disruption and for not updating this page during the incident. A further update will be posted when the investigation is complete.

Read the full incident report →

Started Oct 13, 2026, 02:00 PM UTC· resolved Oct 16, 2026, 10:00 AM UTC

1. identified Oct 13, 2026, 02:00 PM UTC

   Some users may currently experience incomplete or changed charging history in the app under Account / Charging history following recent backend improvements. This may affect Zaptec Pro users in shared installations who have access to a charger, but not to the full installation. In some cases, charging history may currently only be available through the Portal. We are reviewing this behavior and working to improve the experience in the app.

2. resolved Oct 16, 2026, 10:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2026, 03:12 PM UTC· resolved Oct 10, 2026, 07:53 AM UTC

1. investigating Oct 09, 2026, 03:12 PM UTC

   We are investigating increased latency affecting communication between chargers and Zaptec Cloud Services.

2. monitoring Oct 09, 2026, 03:14 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 10, 2026, 07:53 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 08, 2026, 05:49 AM UTC· resolved Oct 08, 2026, 08:00 AM UTC

1. 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

2. 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.

3. monitoring Oct 08, 2026, 07:24 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 08, 2026, 08:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2026, 06:33 PM UTC· resolved Oct 03, 2026, 06:21 AM UTC

1. investigating Oct 02, 2026, 06:33 PM UTC

   We’re currently experiencing delay in the message processing due to the cloud provider issues

2. monitoring Oct 02, 2026, 07:03 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 03, 2026, 06:21 AM UTC

   This incident has been resolved.

4. postmortem Oct 03, 2026, 06:22 AM UTC

   On October 2, 2026, Zaptec identified an issue affecting a subset of OCPP Cloud chargers. The issue caused delays in message processing between cloud services, which led to some charging sessions stopping shortly after they began. The incident primarily affected customers using OCPP Cloud integrations. The issue was investigated by the on-call engineering team and was resolved once cloud message-processing latency returned to normal. \## Customer Impact Some customers experienced interrupted charging sessions for OCPP Cloud chargers. The main symptoms were - Charging sessions started from an app stopped shortly after beginning. - Some sessions ended after delivering little or no energy. - Affected sessions were not able to continue normally once the backend transaction response was rejected. Based on the initial customer report, the issue may have affected a significant number of sessions from October 1 to October 2, 2026. \## Timeline - October 2, 2026, 19:46: Support escalated a customer-reported issue involving OCPP Cloud chargers. - October 2, 2026, 20:03: The on-call engineer began investigating the issue. - October 2, 2026, 20:09: Monitoring showed increased delay in message handling between cloud services. This indicated that the issue was likely related to delayed processing rather than charger behavior. - October 2, 2026, 20:15: Further investigation confirmed unusually high message-processing latency in one of the cloud messaging components. This caused downstream services to process charging events more slowly than normal. - October 2, 2026, 20:20: Support was informed that a customer-facing status update should be prepared, communicating that Zaptec was experiencing delays in message processing due to cloud infrastructure issues. - October 2, 2026, 20:22: The engineering team agreed to attempt a mitigation by resizing the affected messaging component in order to move processing to healthier infrastructure. - October 2, 2026, 20:24: The mitigation was performed, but it did not immediately improve the situation. - October 2, 2026, 20:26: The on-call engineer began escalating the issue through the cloud infrastructure support path. - October 2, 2026, 20:48: Message-processing latency returned to normal, and charging-related messages were again being processed as expected. - October 2, 2026, 21:13: The cloud support partner confirmed that a ticket was being created for further investigation by the underlying cloud provider. \## Root Cause Analysis The issue was caused by elevated latency in a cloud message-processing component used by Zaptec's backend services. This delay affected the flow of charging-session messages between systems. As a result, transaction-related messages were not processed within the expected time window. For affected OCPP Cloud sessions, this could cause the backend response to arrive too late or result in the transaction being rejected, after which the charger stopped the session. The investigation found no indication that the chargers themselves were behaving incorrectly. The chargers followed the expected behavior after receiving a response that the transaction was not accepted. The issue was also not caused by general database saturation or a broad platform outage. The impact was isolated to the delayed message-processing path used by the affected charging-session flow. \## Resolution The incident was resolved when the delayed cloud message-processing returned to normal operation at approximately 20:48 on October 2, 2026. An attempted infrastructure resize did not have an immediate observable effect. The issue normalized shortly afterward, and the support path with the cloud infrastructure provider was used to request further investigation. \## Current Status The affected message-processing path is currently operating normally. Zaptec has requested further investigation from the relevant infrastructure support channels to determine why the latency increased and whether additional preventive measures are needed. \## Follow-Up Actions Zaptec will take the following actions: - Add improved alerting for message-processing latency to reduce time to detection and root-cause analysis. - Review the affected OCPP Cloud message-processing flow to reduce dependency on components that may introduce significant delays. - Prioritize architectural improvements to reduce the risk of similar disruptions.

Read the full incident report →

Started Oct 02, 2026, 06:01 AM UTC· resolved Oct 02, 2026, 07:56 AM UTC

1. 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/ You can also follow updates on our phone service provider’s status page: https://www.atender.com/status

2. investigating Oct 02, 2026, 06:28 AM UTC

   We are continuing to investigate this issue.

3. identified Oct 02, 2026, 07:50 AM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Oct 02, 2026, 07:51 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Oct 02, 2026, 07:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2026, 02:42 PM UTC· resolved Oct 02, 2026, 05:04 AM UTC

1. investigating Oct 01, 2026, 02:42 PM UTC

   Loading charger settings may take some time. We are currently investigating this issue.

2. investigating Oct 01, 2026, 03:53 PM UTC

   Charger settings in the Zaptec Portal are not responding. We are continuing to investigate the issue.

3. investigating Oct 01, 2026, 04:37 PM UTC

   Charger settings in the Zaptec Portal are not responding. We are continuing to investigate the issue.

4. identified Oct 01, 2026, 04:55 PM UTC

   The issue has been identified and a fix is being implemented.

5. monitoring Oct 01, 2026, 05:01 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Oct 02, 2026, 05:04 AM UTC

   This incident has been resolved.

7. postmortem Oct 02, 2026, 09:00 AM UTC

   On October 1, 2026, an internal shared service became unavailable to several dependent applications. This affected multiple API endpoints and reduced availability of the charger page in the customer portal. The incident primarily impacted users trying to access charger-related information through the portal. The issue was mitigated by restoring the affected service and deploying an additional safeguard to prevent dependent applications from waiting indefinitely on slow service responses. \## Impact - Several API endpoints experienced degraded availability or timeouts. - The charger page in the customer portal was unavailable or intermittently failing for affected users during the incident. - No data loss has been identified as part of this incident. \## Timeline All times are in CEST on October 1, 2026. - 15:21: Support reported slowness in the portal. - 15:24: Engineers identified that one of the APIs was experiencing timeouts when calling an internal shared service. - 16:00: The affected API was rolled back to the previous version to restore access to a previous fallback mechanism. - 17:05: The fallback mechanism was enabled, but the charger page continued to fail. - 18:35: Engineers identified that another API was calling the same internal shared service without a timeout. - 18:51: The affected internal service instance was restarted, after which the charger page started working again. - 19:00: A production fix was deployed to add a timeout for requests from the portal API to the internal shared service. \## Root Cause The immediate cause of the incident was that dependent APIs were affected by slow or unavailable responses from a shared internal service. The underlying cause of the service instability is still under investigation. During the incident, service health metrics showed significantly elevated memory-management activity, which indicates that the service was under heavy load at the time. The affected shared service currently handles both resource-intensive background processing and real-time request serving in the same runtime environment. This makes it vulnerable to resource contention. When heavy processing occurs, real-time requests can be delayed or fail, which can then affect applications that depend on the service. \## Resolution The incident was mitigated in two steps. First, engineers rolled back one affected API to a previous version that still supported a fallback mechanism. Second, the affected shared service instance was restarted, which restored functionality for the charger page. A production fix was then deployed to add a timeout to one of the dependent APIs. This reduces the risk of the portal becoming unavailable when the shared service is slow or unresponsive. \## Current Status The charger page functionality was restored on October 1, 2026 at approximately 18:51 CEST. A production fix was deployed at 19:00 CEST to reduce the risk of similar cascading failures. Further investigation is ongoing to determine the exact cause of the shared service instability and to define longer-term architectural improvements.

Read the full incident report →

Started Oct 01, 2026, 01:23 PM UTC· resolved Oct 01, 2026, 02:12 PM UTC

1. investigating Oct 01, 2026, 01:23 PM UTC

   Loading charger settings may take some time. We are currently investigating this issue.

2. identified Oct 01, 2026, 01:35 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Oct 01, 2026, 01:35 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 01, 2026, 02:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 11:26 AM UTC· resolved Oct 01, 2026, 07:15 AM UTC

1. investigating Sep 24, 2026, 11:26 AM UTC

   We are currently working on improving cloud stability. This is an unscheduled maintenance. During this time, some users may experience delays in device status updates. Device operation is not expected to be affected, but the displayed status may take longer than usual to refresh. We apologise for the inconvenience and will provide an update when the situation has improved.

2. investigating Sep 24, 2026, 01:12 PM UTC

   We're declaring incident. Cloud functions, but there might be some issues due to delayed processing. We will give updates around every hour.

3. investigating Sep 24, 2026, 02:20 PM UTC

   We are still investigating the root cause, from what we see charging in Zaptec mode should not be affected, but OCPP bridge could be.

4. investigating Sep 24, 2026, 03:33 PM UTC

   We are continuing to investigate this issue.

5. investigating Sep 24, 2026, 04:43 PM UTC

   We are continuing to investigate this issue.

6. monitoring Sep 24, 2026, 06:35 PM UTC

   A fix has been implemented and we are monitoring the results.

7. monitoring Sep 25, 2026, 07:13 AM UTC

   We are continuing to monitor for any further issues.

8. resolved Oct 01, 2026, 07:15 AM UTC

   This incident has been resolved.

9. postmortem Oct 01, 2026, 11:07 AM UTC

   ## Incident summary On September 24, 2026, we identified a delay in one of our telemetry-processing services. The service was receiving data faster than it could process it, which created a growing backlog. Core charging functionality and primary communication services continued to operate normally. However, delayed telemetry processing affected the responsiveness of the Solar feature for some APM devices. The backlog was fully processed by October 1, 2026, and the incident was subsequently resolved. ## Customer impact The incident had a limited impact on customers: * Core charging operations remained available. * Primary device communication services were not affected. * The Solar feature for some APM devices experienced delays because it depends on timely telemetry data. * No permanent loss of service was identified. ## Incident timeline September 24, 13:13 — Monitoring detected a growing difference between the amount of telemetry received and the amount processed. The team began investigating and initiated incident communications. September 24, 15:06 — An internal incident was declared. The service appeared healthy according to the available monitoring, but its processing capacity was insufficient to keep up with incoming data. September 24, 15:19 — The team identified oversized telemetry records that could cause groups of messages to be processed repeatedly. A change was deployed to isolate and discard invalid records rather than retrying the entire group. September 24, 15:22 — The change improved resilience but did not resolve the processing delay. The investigation found that the service's limited monitoring made it difficult to identify the main performance constraint. September 24, 15:57 — Further analysis indicated that the issue was within the application's processing method rather than the underlying data-storage service. September 24, 17:12 — An updated version of the service was prepared for testing. Because core services remained operational, the team prioritized careful validation over an immediate production deployment to avoid introducing additional risk. September 24, 21:41 — The updated service was running successfully in the development environment. Testing continued to confirm that all processing scenarios worked as expected. September 30, 17:01 — The updated service was deployed to production. Processing performance improved immediately, and the telemetry backlog began decreasing. October 1, 00:30 — The telemetry backlog was fully processed. October 1, 08:30 — The incident was declared resolved. ## Root cause The affected service processed data-storage operations one at a time. As the volume of telemetry increased, this sequential approach could no longer provide sufficient throughput, causing the backlog to grow. The service was also based on an older application design with limited performance monitoring. This made the underlying bottleneck difficult to identify and extended the investigation. Oversized telemetry records contributed to unnecessary reprocessing but were not the primary cause of the incident. ## Resolution We replaced the affected service with an updated version that can safely process multiple storage operations concurrently. This substantially increased processing capacity and allowed the service to clear the backlog. We also improved the handling of oversized records so that a single invalid record no longer causes a larger group of telemetry messages to be reprocessed. ## Preventive actions To reduce the likelihood and duration of similar incidents, we have: Modernized the affected service and aligned it with our current application standards. Added improved monitoring for service health, processing performance, and backlog growth. Introduced controlled parallel processing to support higher telemetry volumes. Improved the handling of oversized or invalid telemetry records. Begun reviewing the wider telemetry-processing architecture to simplify data flows and make service dependencies and customer impact easier to identify. This was the final application using the relevant legacy architecture. Its modernization removes a significant source of technical debt and improves our ability to detect, diagnose, and resolve future performance issues.

Read the full incident report →

Started Sep 21, 2026, 12:36 PM UTC· resolved Sep 21, 2026, 12:56 PM UTC

1. investigating Sep 21, 2026, 12:36 PM UTC

   We are currently investigating this issue.

2. monitoring Sep 21, 2026, 12:38 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 21, 2026, 12:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2026, 10:04 AM UTC· resolved Sep 11, 2026, 11:18 AM UTC

1. 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.

2. monitoring Sep 11, 2026, 10:47 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 11, 2026, 11:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 08, 2026, 07:14 AM UTC· resolved Sep 08, 2026, 01:26 PM UTC

1. investigating Sep 08, 2026, 07:14 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 help.zaptec.com.

2. monitoring Sep 08, 2026, 07:40 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 08, 2026, 01:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 04, 2026, 02:38 PM UTC· resolved Sep 04, 2026, 03:35 PM UTC

1. 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.

2. resolved Sep 04, 2026, 03:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 04, 2026, 08:29 AM UTC· resolved Sep 11, 2026, 10:47 AM UTC

1. 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.

2. identified Sep 07, 2026, 08:15 AM UTC

   We are continuing to work on a fix for this issue.

3. identified Sep 10, 2026, 12:51 PM UTC

   We are continuing to work on a fix for this issue.

4. resolved Sep 11, 2026, 10:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 19, 2026, 04:16 PM UTC· resolved Aug 21, 2026, 11:30 AM UTC

1. investigating Aug 19, 2026, 04:16 PM UTC

   We are currently investigating this issue.

2. 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.

3. monitoring Aug 19, 2026, 07:36 PM UTC

   A fix has been implemented and we are monitoring the results.

4. 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.

5. monitoring Aug 20, 2026, 11:23 AM UTC

   We are continuing to monitor for any further issues.

6. resolved Aug 21, 2026, 11:30 AM UTC

   This incident has been resolved.

7. 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 →

Started Aug 14, 2026, 08:58 AM UTC· resolved Aug 21, 2026, 08:20 AM UTC

1. 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.

2. monitoring Aug 21, 2026, 08:19 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 21, 2026, 08:20 AM UTC

   The incident has been resolved.

Read the full incident report →

Started Aug 10, 2026, 08:55 AM UTC· resolved Aug 10, 2026, 09:56 AM UTC

1. investigating Aug 10, 2026, 08:55 AM UTC

   Loading charger settings may take some time. We are currently investigating this issue.

2. identified Aug 10, 2026, 08:58 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Aug 10, 2026, 08:59 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Aug 10, 2026, 09:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 27, 2026, 02:31 PM UTC· resolved Jul 27, 2026, 04:18 PM UTC

1. investigating Jul 27, 2026, 02:31 PM UTC

   We are currently investigating this issue.

2. 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.

3. resolved Jul 27, 2026, 04:18 PM UTC

   This incident has been resolved.

4. 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 →

Started Jul 21, 2026, 10:59 AM UTC· resolved Jul 21, 2026, 01:12 PM UTC

1. 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/

2. identified Jul 21, 2026, 11:28 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 21, 2026, 12:30 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jul 21, 2026, 01:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 17, 2026, 08:56 AM UTC· resolved Jun 17, 2026, 01:15 PM UTC

1. investigating Jun 17, 2026, 08:56 AM UTC

   We are currently investigating this issue.

2. monitoring Jun 17, 2026, 09:15 AM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Jun 17, 2026, 12:24 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jun 17, 2026, 01:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2026, 06:57 AM UTC· resolved Jun 10, 2026, 09:13 AM UTC

1. 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.

2. identified Jun 10, 2026, 07:08 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jun 10, 2026, 07:29 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jun 10, 2026, 09:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 27, 2026, 09:47 AM UTC· resolved Jun 04, 2026, 06:47 AM UTC

1. investigating May 27, 2026, 09:47 AM UTC

   We are currently investigating this issue.

2. monitoring May 27, 2026, 10:40 AM UTC

   A fix has been implemented and we are monitoring the results.

3. investigating May 27, 2026, 11:04 AM UTC

   We are currently investigating this issue.

4. monitoring May 28, 2026, 05:29 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Jun 04, 2026, 06:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 18, 2026, 07:42 AM UTC· resolved May 22, 2026, 12:03 PM UTC

1. 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/

2. identified May 18, 2026, 10:12 AM UTC

   The issue has been identified and a fix is being implemented.

3. 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/

4. 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/

5. 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/

6. 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

7. monitoring May 20, 2026, 05:39 AM UTC

   We are continuing to monitor for any further issues.

8. 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/

9. identified May 20, 2026, 01:20 PM UTC

   The issue has been identified and a fix is being implemented.

10. 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/

11. 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

12. resolved May 22, 2026, 12:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Started May 15, 2026, 10:30 AM UTC· resolved May 15, 2026, 12:46 PM UTC

1. investigating May 15, 2026, 10:30 AM UTC

   We are currently investigating this issue.

2. 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/

3. 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/

4. monitoring May 15, 2026, 12:01 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved May 15, 2026, 12:46 PM UTC

   This incident has been resolved.

Read the full incident report →