Resolved after 14 minutes, affecting APIs (US East) and Webapp, on August 25, 2026.
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
Update timeline
- 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.
- 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.
- 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.
- 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.
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