Resolved after 10 minutes, affecting APIs (AP South) and Webapp, on August 13, 2026.
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
Update timeline
- 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.
- 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.
- 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.
- 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.
Your product runs on more than Zuper
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services