Keka incident

We experienced a brief service disruption due to an unplanned Azure SQL Database availability event in the Central India region

Resolved after 8 minutes, affecting section-160684 (Attendance) and section-160684 (Payroll) and 1 more, on March 6, 2026.

resolved Mar 06, 2026, 12:41 AM UTC

The earlier database availability issue has been resolved. Azure reported a transient platform event that caused temporary unavailability between 06:03 AM and 06:11 AM IST. Our monitoring system alerted our team immediately, and services have been stable since recovery. The system is now fully operational.

Started: Mar 06, 2026, 12:33 AM UTC
Resolved: Mar 06, 2026, 12:41 AM UTC
Duration: 8m
Detected by Pingoru: Mar 06, 2026, 12:33 AM UTC

Affected components

section-160684 (Attendance)section-160684 (Payroll)section-160684 (Timesheet)section-160684 (Leave)section-160684 (Keka API)section-179897 (Dashboard)section-179897 (Core HR)section-179897 (Mobile API)section-179897 (ATS)section-160684 (Attendance)

Update timeline

investigating Mar 06, 2026, 12:33 AM UTC

Our proactive monitoring system immediately alerted our team, and we started investigating the issue. The service has recovered automatically and is currently operating normally. We are continuing to monitor the system to ensure stability.
resolved Mar 06, 2026, 12:41 AM UTC

The earlier database availability issue has been resolved. Azure reported a transient platform event that caused temporary unavailability between 06:03 AM and 06:11 AM IST. Our monitoring system alerted our team immediately, and services have been stable since recovery. The system is now fully operational.

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.