Zuper Outage History

Started Sep 16, 2026, 01:50 AM UTC· resolved Sep 16, 2026, 01:50 AM UTC

1. resolved Sep 16, 2026, 01:50 AM UTC

   SUMMARY On September 16, 2026, between 01:50 UTC and 03:50 UTC (7:20 AM – 9:20 AM IST), customers in the us-east-1 region experienced intermittent 502 errors while using Workflow Builder. Timeline September 16, 2026, 01:50 AM UTC | 7:20 AM IST We are aware of an issue affecting Workflow Builder in the us-east-1 region, where API requests are intermittently returning 502 errors. Our engineering team is investigating and will provide an update shortly. Thank you for your patience. September 16, 2026, 02:15 AM UTC | 7:45 AM IST This has been classified as an incident. Our team has identified a sudden increase in MySQL database connections in the us-east-1 region, exceeding the configured maximum connection limit, which is causing the intermittent 502 errors. We are working on a fix. September 16, 2026, 03:00 AM UTC | 8:30 AM IST The maximum connection limit on the MySQL database has been increased to accommodate the higher connection demand. We are monitoring database connections and Workflow Builder API performance to confirm recovery. September 16, 2026, 03:30 AM UTC | 9:00 AM IST The Engineering team identified the root cause and implemented a hotfix to address the issue September 16, 2026, 03:50 AM UTC | 9:20 AM IST We are pleased to confirm that Workflow Builder API performance has returned to normal and intermittent 502 errors have been resolved. Our team will continue monitoring to ensure service stability. Root Cause Analysis An event trigger configured in a table within the Workflow Builder database encountered an edge case that caused a table lock. Subsequent queries were left in a waiting state, leading to database connection thread exhaustion. This resulted in database connection failures and intermittent 502 errors on Workflow Builder API requests. Resolution The Engineering team identified the root cause and implemented a hotfix to address the issue. Additionally, the maximum connection limit on the MySQL database was increased to accommodate the elevated connection demand and help prevent similar issues. Remediation Items Review and adjust the MySQL maximum connection limit to better accommodate peak request volume in us-east-1. Set up proactive alerting on MySQL active connection count to notify the team before connections approach exhaustion.

2. resolved Sep 16, 2026, 01:50 AM UTC

   SUMMARY On September 16, 2026, between 01:50 UTC and 03:50 UTC (7:20 AM – 9:20 AM IST), customers in the us-east-1 region experienced intermittent 502 errors while using Workflow Builder. Timeline September 16, 2026, 01:50 AM UTC | 7:20 AM IST We are aware of an issue affecting Workflow Builder in the us-east-1 region, where API requests are intermittently returning 502 errors. Our engineering team is investigating and will provide an update shortly. Thank you for your patience. September 16, 2026, 02:15 AM UTC | 7:45 AM IST This has been classified as an incident. Our team has identified a sudden increase in MySQL database connections in the us-east-1 region, exceeding the configured maximum connection limit, which is causing the intermittent 502 errors. We are working on a fix. September 16, 2026, 03:00 AM UTC | 8:30 AM IST The maximum connection limit on the MySQL database has been increased to accommodate the higher connection demand. We are monitoring database connections and Workflow Builder API performance to confirm recovery. September 16, 2026, 03:30 AM UTC | 9:00 AM IST The Engineering team identified the root cause and implemented a hotfix to address the issue September 16, 2026, 03:50 AM UTC | 9:20 AM IST We are pleased to confirm that Workflow Builder API performance has returned to normal and intermittent 502 errors have been resolved. Our team will continue monitoring to ensure service stability. Root Cause Analysis An event trigger configured in a table within the Workflow Builder database encountered an edge case that caused a table lock. Subsequent queries were left in a waiting state, leading to database connection thread exhaustion. This resulted in database connection failures and intermittent 502 errors on Workflow Builder API requests. Resolution The Engineering team identified the root cause and implemented a hotfix to address the issue. Additionally, the maximum connection limit on the MySQL database was increased to accommodate the elevated connection demand and help prevent similar issues. Remediation Items Review and adjust the MySQL maximum connection limit to better accommodate peak request volume in us-east-1. Set up proactive alerting on MySQL active connection count to notify the team before connections approach exhaustion.

Read the full incident report →

Started Aug 25, 2026, 02:26 PM UTC· resolved Aug 25, 2026, 02:40 PM UTC

1. investigating Aug 25, 2026, 02:26 PM UTC

   14:26 UTC | 06:26 AM PST We are aware of an issue affecting the Zuper Web App, Mobile App, and API services in the us-east-1 region, where customers are experiencing intermittent slowness. Our engineering team is investigating and will provide an update shortly. Thank you for your patience.

2. identified Aug 25, 2026, 02:30 PM UTC

   14:30 UTC | 06:30 AM PST This has been classified as an incident. Our team has identified elevated database CPU utilization in the us-east-1 region following a recent deployment to one of our backend services. We are working on a fix.

3. resolved Aug 25, 2026, 02:40 PM UTC

   14:40 UTC | 06:40 AM PST The recent deployment has been rolled back and database utilization has returned to normal levels. API performance has returned to normal and the slowness has been resolved. Our team will continue monitoring to ensure service stability. Root Cause Analysis A recent deployment to one of the backend services resulted in elevated DB CPU utilization in the us-east-1 region. The increased database utilization affected API performance, resulting in intermittent slowness and performance degradation. Resolution The Engineering team identified the deployment as the source of the elevated database utilization and rolled it back to reduce the database load. DB CPU utilization returned to normal levels and API performance recovered. The system was monitored after recovery and no further degradation was observed.

4. resolved Aug 25, 2026, 02:40 PM UTC

   14:40 UTC | 06:40 AM PST The recent deployment has been rolled back and database utilization has returned to normal levels. API performance has returned to normal and the slowness has been resolved. Our team will continue monitoring to ensure service stability. Root Cause Analysis A recent deployment to one of the backend services resulted in elevated DB CPU utilization in the us-east-1 region. The increased database utilization affected API performance, resulting in intermittent slowness and performance degradation. Resolution The Engineering team identified the deployment as the source of the elevated database utilization and rolled it back to reduce the database load. DB CPU utilization returned to normal levels and API performance recovered. The system was monitored after recovery and no further degradation was observed.

Read the full incident report →

Started Aug 13, 2026, 12:15 PM UTC· resolved Aug 13, 2026, 12:25 PM UTC

1. investigating Aug 13, 2026, 12:15 PM UTC

   12:15 UTC | 04:15 AM PST We are aware of an issue affecting the Zuper Web App API services in the ap-south-1 region, where customers are experiencing intermittent API failures and slowness. Our engineering team is investigating and will provide an update shortly. Thank you for your patience.

2. identified Aug 13, 2026, 12:17 PM UTC

   12:17 UTC | 04:17 AM PST This has been classified as an incident. Our team has identified a sudden spike in database activity resulting in elevated database CPU utilization in the ap-south-1 region, which is causing the intermittent API failures. We are working on a fix.

3. resolved Aug 13, 2026, 12:25 PM UTC

   12:25 UTC | 04:25 AM PST Corrective action has been taken to reduce the database load, and database utilization has returned to normal levels. API performance has returned to normal and the intermittent failures have been resolved. Our team will continue monitoring to ensure service stability. Root Cause Analysis A sudden spike in database activity resulted in elevated DB CPU utilization in the ap-south-1 region. The increased database utilization affected API performance, resulting in intermittent API failures and service degradation. Resolution The Engineering team identified the source of the elevated database utilization and took immediate corrective action to reduce the database load. DB CPU utilization returned to normal levels and API performance recovered. The system was monitored after recovery and no further degradation was observed.

4. resolved Aug 13, 2026, 12:25 PM UTC

   12:25 UTC | 04:25 AM PST Corrective action has been taken to reduce the database load, and database utilization has returned to normal levels. API performance has returned to normal and the intermittent failures have been resolved. Our team will continue monitoring to ensure service stability. Root Cause Analysis A sudden spike in database activity resulted in elevated DB CPU utilization in the ap-south-1 region. The increased database utilization affected API performance, resulting in intermittent API failures and service degradation. Resolution The Engineering team identified the source of the elevated database utilization and took immediate corrective action to reduce the database load. DB CPU utilization returned to normal levels and API performance recovered. The system was monitored after recovery and no further degradation was observed.

Read the full incident report →