Keka incident

Mobile API Services (CIN03)

Resolved on October 13, 2025, affecting section-179897 (Mobile API) and section-179897 (Mobile API).

resolved Oct 13, 2025, 05:49 AM UTC

The root cause was database connection pool exhaustion triggered by a sudden increase in concurrent requests to the Mobile and Web API services. The devops team scaled up the database connections to handle the increased load. System performance stabilized after the scale-up completed. Continuous monitoring was enabled to validate stability. Actions Taken: Short-term - Verified successful scale-up and confirmed service recovery. - Enabled real-time monitoring on database connection utilization. - Validated API stability post scale-up using Better Stack Long-term - Optimize database pooling configuration to better handle high concurrency. - Implement proactive alerts for connection pool exhaustion and sudden traffic spikes. - Fine-tune auto-scaling thresholds to trigger earlier under high load. - Review and upgrade service plan or database tier to improve responsiveness during scaling events.

Started
Oct 13, 2025, 05:49 AM UTC
Resolved
Oct 13, 2025, 05:49 AM UTC
Duration
–
Detected by Pingoru
Oct 13, 2025, 05:49 AM UTC

Affected components

section-179897 (Mobile API)section-179897 (Mobile API)

Update timeline

  1. resolved Oct 13, 2025, 05:49 AM UTC

    The root cause was database connection pool exhaustion triggered by a sudden increase in concurrent requests to the Mobile and Web API services. The devops team scaled up the database connections to handle the increased load. System performance stabilized after the scale-up completed. Continuous monitoring was enabled to validate stability. Actions Taken: Short-term - Verified successful scale-up and confirmed service recovery. - Enabled real-time monitoring on database connection utilization. - Validated API stability post scale-up using Better Stack Long-term - Optimize database pooling configuration to better handle high concurrency. - Implement proactive alerts for connection pool exhaustion and sudden traffic spikes. - Fine-tune auto-scaling thresholds to trigger earlier under high load. - Review and upgrade service plan or database tier to improve responsiveness during scaling events.

Your product runs on more than Keka

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →