Lokalise Status Page

Feb 4, 2026 · resolved Feb 4

On February 4, 2026, Lokalise experienced a brief service interruption where both the application and API were unavailable for approximately 10 minutes. The incident began at 16:18 UTC and was fully resolved within 12 minutes as our engineering team restored service functionality. **What happened?** **The Cause:** A configuration update intended to enable new application metrics unexpectedly triggered a series of intensive, unoptimized database scans. This resulted in an immediate exhaustion of our backend processing capacity, preventing the web server from fulfilling incoming requests. **The Fix:** Our team identified the faulty configuration release and promptly initiated a rollback to the last known stable state. Once service was restored, a permanent fix was deployed to remove the problematic configuration entirely. **Timeline \(UTC\):** * **16:18:** Automated alerts reported service unavailability; investigation initiated. * **16:20:** The root cause was identified as a recent configuration deployment. * **16:27:** Rollback to a stable version was initiated. * **16:30:** Application and API functionality were fully restored. * **17:07:** System verified as stable after a final hotfix deployment. **What we are doing to prevent this in the future** * **Enhancing pre-deployment validation:** We are updating our automated review agents to flag potential performance issues in legacy code or dormant features before they are activated via configuration changes. * **Optimizing metric design:** We are transitioning to a system that pre-computes application metrics in isolated processes to ensure that monitoring activities never compete with core application resources. * **Refactoring database interactions:** Our team is reviewing and refactoring resource-intensive database queries to improve overall platform stability and response times. * **Consolidating internal alerting:** We are refining our monitoring workflows to consolidate overlapping alerts, allowing our engineers to focus even more quickly on resolution during critical events. We sincerely apologize for the disruption this incident caused to your work and your automated workflows. We recognize the trust you place in Lokalise for your daily operations, and we are committed to enhancing our processes to prevent similar occurrences. If you have any questions or require further assistance regarding this incident, please reach out to us at [**[email protected]**](mailto:[email protected]).

Jan 26, 2026 · resolved Jan 26

On January 26, 2026, Lokalise experienced a service outage and performance degradation between 15:52 UTC and 16:32 UTC. During this time, the Lokalise application was unavailable, and users of the API experienced intermittent connectivity and high latency. **What happened?** **The Cause:** The incident was triggered during a migration of our monitoring systems. A configuration mismatch caused a high volume of internal network requests to fail, which subsequently overwhelmed our internal DNS services. This prevented various parts of our infrastructure from communicating with one another, including our primary databases and application services. **The Fix:** Our engineering team identified the source of the traffic and disabled the legacy monitoring configuration. We also rotated affected infrastructure nodes and adjusted our service scaling to alleviate pressure on our databases. These actions restored normal communication between our services, bringing the platform back to full operational status. **Timeline \(UTC\):** * **15:52:** Service degradation and unavailability detected and investigation initiated. * **16:24:** Root cause identified as internal network congestion impacting service connectivity. * **16:27:** Corrective actions implemented; service begins to stabilize. * **16:32:** Full service restored and performance monitored for stability. **What we are doing to prevent this in the future** * **Enhancing scaling capabilities:** We are upgrading our internal DNS services to scale horizontally, ensuring they can handle unexpected spikes in traffic without impacting the wider platform. * **Improving resource monitoring:** We are implementing additional alerting for resource exhaustion to identify and mitigate infrastructure bottlenecks before they impact service availability. * **Refining deployment procedures:** We are updating our internal documentation and validation steps to ensure infrastructure dependencies are strictly coordinated during system migrations. We sincerely apologize for the disruption this incident caused to your workflow. We understand how critical Lokalise is to your operations and are committed to improving our system's resilience to prevent a recurrence. If you have any questions or require further assistance, please contact us at [[email protected]](mailto:[email protected]).

Nov 27, 2025 · resolved Nov 27

This incident has been resolved.

Oct 23, 2025 · resolved Oct 23

This incident has been resolved.

Oct 7, 2025 · resolved Oct 7

This incident has been resolved.