- Detected by Pingoru
- Aug 26, 2026, 11:11 AM UTC
- Resolved
- Aug 26, 2026, 11:16 AM UTC
- Duration
- 5m
Affected: Keka Central US Region (Mobile API)
Timeline · 2 updates
-
investigating Aug 26, 2026, 11:11 AM UTC
We are aware of an issue affecting India 01 — Mobile API and our team is actively working to resolve it. We apologize for the inconvenience and will keep you updated here.
-
resolved Aug 26, 2026, 11:16 AM UTC
We are pleased to inform you that the issue has been resolved and all systems are back to normal. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2026, 01:21 PM UTC
- Resolved
- Aug 25, 2026, 01:56 PM UTC
- Duration
- 35m
Affected: Keka UAE North Region (Attendance)
Timeline · 2 updates
-
investigating Aug 25, 2026, 01:21 PM UTC
We are aware of an issue affecting India 03 — Attendance and our team is actively working to resolve it. We apologize for the inconvenience and will keep you updated here.
-
resolved Aug 25, 2026, 01:56 PM UTC
We are pleased to inform you that the issue has been resolved and all systems are back to normal. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 09:45 AM UTC
- Resolved
- Aug 24, 2026, 10:17 AM UTC
- Duration
- 31m
Affected: Keka Central US Region (Mobile API)
Timeline · 2 updates
-
investigating Aug 24, 2026, 09:45 AM UTC
We are aware of an issue affecting India 03 — Mobile API and our team is actively working to resolve it. We apologize for the inconvenience and will keep you updated here.
-
resolved Aug 24, 2026, 10:17 AM UTC
We are pleased to inform you that the issue has been resolved and all systems are back to normal. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 08:01 AM UTC
- Resolved
- Aug 20, 2026, 08:31 AM UTC
- Duration
- 29m
Affected: Keka Central US Region (Mobile API)
Timeline · 2 updates
-
investigating Aug 20, 2026, 08:01 AM UTC
We are aware of an issue affecting India 02 — Mobile API and our team is actively working to resolve it. We apologize for the inconvenience and will keep you updated here.
-
resolved Aug 20, 2026, 08:31 AM UTC
We are pleased to inform you that the issue has been resolved and all systems are back to normal. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 10:21 AM UTC
- Resolved
- Aug 14, 2026, 10:21 AM UTC
- Duration
- —
Timeline · 1 update
-
investigating Aug 14, 2026, 10:14 AM UTC
Mobile API went down
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 06:52 AM UTC
- Resolved
- Jul 27, 2026, 06:52 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 27, 2026, 06:52 AM UTC
Keka API recovered
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 03:39 AM UTC
- Resolved
- Jul 17, 2026, 03:39 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 17, 2026, 03:39 AM UTC
Keka API CUS recovered
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 04:53 PM UTC
- Resolved
- Jul 11, 2026, 04:53 PM UTC
- Duration
- —
Timeline · 1 update
-
investigating Jul 11, 2026, 04:37 PM UTC
Core HR went down
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 04:53 PM UTC
- Resolved
- Jul 11, 2026, 04:53 PM UTC
- Duration
- —
Timeline · 1 update
-
investigating Jul 11, 2026, 04:28 PM UTC
Attendance went down
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 04:53 PM UTC
- Resolved
- Jul 11, 2026, 04:53 PM UTC
- Duration
- —
Timeline · 1 update
-
investigating Jul 11, 2026, 04:40 PM UTC
Leave went down
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 04:52 PM UTC
- Resolved
- Jul 11, 2026, 04:52 PM UTC
- Duration
- —
Timeline · 1 update
-
investigating Jul 11, 2026, 04:38 PM UTC
Payroll went down
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 04:52 PM UTC
- Resolved
- Jul 11, 2026, 04:52 PM UTC
- Duration
- —
Timeline · 1 update
-
investigating Jul 11, 2026, 04:37 PM UTC
Timesheet went down
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 04:51 PM UTC
- Resolved
- Jul 11, 2026, 04:51 PM UTC
- Duration
- —
Timeline · 1 update
-
investigating Jul 11, 2026, 04:36 PM UTC
Dashboard went down
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2026, 03:30 AM UTC
- Resolved
- Jun 20, 2026, 04:03 AM UTC
- Duration
- 33m
Timeline · 1 update
-
investigating Jun 20, 2026, 03:30 AM UTC
Mobile API went down
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 10:08 AM UTC
- Resolved
- Jun 17, 2026, 10:24 AM UTC
- Duration
- 16m
Timeline · 1 update
-
investigating Jun 17, 2026, 10:08 AM UTC
Timesheet went down
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 10:07 AM UTC
- Resolved
- Jun 17, 2026, 10:24 AM UTC
- Duration
- 17m
Timeline · 1 update
-
investigating Jun 17, 2026, 10:07 AM UTC
Core HR went down
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 10:07 AM UTC
- Resolved
- Jun 17, 2026, 10:24 AM UTC
- Duration
- 17m
Timeline · 1 update
-
investigating Jun 17, 2026, 10:07 AM UTC
Attendance went down
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 06:47 AM UTC
- Resolved
- Apr 15, 2026, 06:47 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 15, 2026, 06:47 AM UTC
ATS recovered
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 06:38 AM UTC
- Resolved
- Apr 15, 2026, 06:38 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 15, 2026, 06:38 AM UTC
Attendance recovered
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 06:35 AM UTC
- Resolved
- Apr 15, 2026, 06:35 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 15, 2026, 06:35 AM UTC
Payroll recovered
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 06:26 AM UTC
- Resolved
- Apr 15, 2026, 06:26 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 15, 2026, 06:26 AM UTC
keka API recovered
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 05:50 AM UTC
- Resolved
- Apr 15, 2026, 05:50 AM UTC
- Duration
- —
Affected: Keka UAE North Region (Attendance)Keka UAE North Region (Payroll)Keka UAE North Region (Timesheet)Keka UAE North Region (Leave)Keka UAE North Region (Keka API)Keka Central US Region (Dashboard)Keka Central US Region (Core HR)Keka Central US Region (Mobile API)Keka Central US Region (ATS)
Timeline · 1 update
-
resolved Apr 15, 2026, 05:50 AM UTC
The Keka application is currently experiencing significant slowness, with pages taking an unusually long time to load. We have identified the issue related to Redis configuration changes.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 12:33 AM UTC
- Resolved
- Mar 06, 2026, 12:41 AM UTC
- Duration
- 8m
Affected: Keka UAE North Region (Attendance)Keka UAE North Region (Payroll)Keka UAE North Region (Timesheet)Keka UAE North Region (Leave)Keka UAE North Region (Keka API)Keka Central US Region (Dashboard)Keka Central US Region (Core HR)Keka Central US Region (Mobile API)Keka Central US Region (ATS)
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 07:41 AM UTC
- Resolved
- Feb 18, 2026, 04:08 AM UTC
- Duration
- 20h 26m
Affected: Keka UAE North Region (Attendance)Keka UAE North Region (Payroll)Keka UAE North Region (Timesheet)Keka UAE North Region (Leave)Keka UAE North Region (Keka API)Keka Central US Region (Dashboard)Keka Central US Region (Core HR)Keka Central US Region (Mobile API)Keka Central US Region (ATS)
Timeline · 2 updates
-
investigating Feb 17, 2026, 07:41 AM UTC
We are currently experiencing a service degradation impacting Azure Storage Accounts in the Central India region, which may cause increased latency, intermittent timeouts, and occasional HTTP 500 errors. This issue is due to an ongoing Azure platform incident, and no ETA for resolution has been provided yet. There is no evidence of data loss, and we are actively monitoring the situation and will share updates as they become available.
-
resolved Feb 18, 2026, 04:08 AM UTC
All resources are restored
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 07:01 AM UTC
- Resolved
- Feb 09, 2026, 07:01 AM UTC
- Duration
- —
Affected: Keka UAE North Region (Payroll)
Timeline · 1 update
-
resolved Feb 09, 2026, 07:01 AM UTC
CIN03 environment is not loading due to partial slowness,the issue has been mitigated, and the CIN03 environment is now functioning normally.
Read the full incident report →