Zuper Outage History
Zuper is up right nowZuper had 3 outages in the last 2 years totaling 24m of downtime, averaging 0.1 incidents per month.
There were 3 Zuper outages since August 13, 2026 totaling 24m of downtime. Each is summarised below. Incident details, duration, and resolution information.
API performance degradation in us-east-1
Affected: US EastWebapp
Timeline · 3 updates
- investigating Aug 25, 2026, 02:26 PM UTC
Status: Investigating 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. Affected components Webapp (Degraded performance) US East (Degraded performance)
- identified Aug 25, 2026, 02:30 PM UTC
Status: Identified 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. Affected components Webapp (Degraded performance) US East (Degraded performance)
- resolved Aug 25, 2026, 02:40 PM UTC
Status: Resolved 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. Affected components Webapp (Operational) US East (Operational)
API performance degradation in ap-south-1
Affected: AP SouthWebapp
Timeline · 3 updates
- investigating Aug 13, 2026, 12:15 PM UTC
Status: Investigating 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. Affected components Webapp (Degraded performance) AP South (Degraded performance)
- identified Aug 13, 2026, 12:17 PM UTC
Status: Identified 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. Affected components Webapp (Degraded performance) AP South (Degraded performance)
- resolved Aug 13, 2026, 12:25 PM UTC
Status: Resolved 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. Affected components Webapp (Operational) AP South (Operational)