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):
What we are doing to prevent this in the future
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 hello@lokalise.com.