Keka Outage History
Keka is up right nowPingoru has recorded 84 incidents for Keka: 68 in the last 12 months and 14 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 28 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 5 | 1 of 720 (0%) |
| July 2026 | 13 | 0 of 744 (0%) |
| August 2026 | 9 | 2 of 744 (0%) |
| September 2026 | 4 | 2 of 720 (0%) |
| October 2026 | 1 | 18 of 591 (3%) |
Incidents, newest first
Minor March 6, 2026 We experienced a brief service disruption due to an unplanned Azure SQL Database availability event in the Central India region 8m section-160684 (Attendance), section-160684 (Payroll), section-160684 (Timesheet), section-160684 (Leave) and 14 more
Started Mar 06, 2026, 12:33 AM UTC· resolved Mar 06, 2026, 12:41 AM UTC
- 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.
Minor February 17, 2026 We are currently experiencing a service degradation affecting Storage Accounts in the Central India region. 20h 26m section-160684 (Attendance), section-160684 (Payroll), section-160684 (Timesheet), section-160684 (Leave) and 14 more
Started Feb 17, 2026, 07:41 AM UTC· resolved Feb 18, 2026, 04:08 AM UTC
- 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
Minor February 9, 2026 Loading Issue in CIN03 – section-160684 (Payroll), section-160684 (Payroll)
Started Feb 09, 2026, 07:01 AM UTC· resolved Feb 09, 2026, 07:01 AM UTC
- 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.
Minor February 3, 2026 Report Builder Issue in all Regions – section-179897 (ATS), section-179897 (ATS)
Started Feb 03, 2026, 10:15 AM UTC· resolved Feb 03, 2026, 10:15 AM UTC
- resolved Feb 03, 2026, 10:15 AM UTC
Current Status: The issue has been identified. The Hire team recently updated the API URL for Global Admin and Hire Admin, which inadvertently caused the Report Builder functionality to fail across all regions. The frontend logic missed handling this change, leading to the disruption. Impact: Users across all regions were unable to generate reports in all regions, affecting critical reporting workflows and operational decision-making. All backend systems are working and operational.
Minor October 29, 2025 Service Disruption Notice 1h 45m section-160679 (Login), section-160679 (Login)
Started Oct 29, 2025, 05:11 PM UTC· resolved Oct 29, 2025, 06:56 PM UTC
- investigating Oct 29, 2025, 05:11 PM UTC
We are currently experiencing intermittent service disruptions affecting parts of our website and application. The issue is related to an external content delivery network (CDN) provider experiencing a widespread outage, which is impacting content delivery and availability across multiple regions. Current Status: Root Cause: Our CDN provider is investigating a global service disruption that is affecting content delivery and network performance. Impact: Some users may experience slow loading times, intermittent access issues, or temporary unavailability of certain pages or resources. Scope: The issue is not localized — it may affect users across multiple regions, including India. What We’re Doing: Our engineering team is actively monitoring the incident and working with our CDN provider to ensure services are restored as quickly as possible. We’ll continue to update this page with new information as it becomes available. We sincerely apologize for the inconvenience and appreciate your patience while we work to restore full functionality.
- resolved Oct 29, 2025, 06:56 PM UTC
We’re pleased to inform you that our web application is now stable and functioning normally after rerouting traffic directly to the origin servers, effectively bypassing the CDN. This issue impacted only the web application, while the mobile app remained fully operational throughout the incident. We are continuing to monitor performance closely to ensure stability.
Minor October 13, 2025 Mobile API Services (CIN03) – section-179897 (Mobile API), section-179897 (Mobile API)
Started Oct 13, 2025, 05:49 AM UTC· resolved Oct 13, 2025, 05:49 AM UTC
- 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.
Minor October 8, 2025 Mobile API Intermittent Timeouts. –
Started Oct 08, 2025, 04:00 AM UTC· resolved Oct 08, 2025, 04:00 AM UTC
- resolved Oct 08, 2025, 04:00 AM UTC
The issue was resolved on Oct 8, 2025, at 9:56 AM. The Mobile API environment experienced intermittent timeouts and failures in displaying the Remote Clock-in card. Investigation revealed that the issue occurred during autoscaling, when new backend instances were being provisioned. Due to memory and storage limitations, these instances required a brief warm-up period, during which some requests were temporarily dropped for approximately two minutes.
Minor June 11, 2025 CDN Accessibility Issue – section-160679 (Login)
Started Jun 11, 2025, 01:30 AM UTC· resolved Jun 11, 2025, 01:30 AM UTC
- resolved Jun 11, 2025, 01:30 AM UTC
We are currently investigating an issue where certain clients are unable to access the Keka application due to a Content Delivery Network (CDN) caching and propagation anomaly. This appears to be affecting tenant-specific assets or login endpoints, causing partial or complete service disruption for impacted users. Our engineering team has identified that some edge nodes may be serving stale or corrupted content due to improper cache invalidation or TTL (time-to-live) configuration. 🛠 Next Steps: We are performing a CDN cache purge and forcing revalidation of content across all PoPs (Points of Presence). DNS-level inspection and propagation checks are underway to ensure edge resolution consistency. We will continue to provide updates as we mitigate the issue. Thank you for your patience and understanding.
Major February 5, 2025 CIN 02 services are unavailable 24m
Started Feb 05, 2025, 10:39 PM UTC· resolved Feb 05, 2025, 11:03 PM UTC
- investigating Feb 05, 2025, 10:39 PM UTC
We are currently experiencing an outage affecting several CIN 02 services. This includes the Dashboard, Core API, Attendance, Payroll, Timesheet, Leave, and Mobile API. Our team is investigating the root cause and working urgently to restore service. We apologize for the inconvenience and will provide updates as we work to resolve this issue.
- resolved Feb 05, 2025, 11:03 PM UTC
We have reinstated all affected applications and accessibility is restored across all instances of Keka HR app. We are monitoring the application as it attains stability. We thank you for your patience along the way and regret the inconvenience caused during this period of application outage.