Lokalise main application and API intermittent functionality

What to do

• Check whether you use Lokalise Lokalise API, Lokalise App in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 28m it lasted.

  Anything that failed between 2025-07-30 12:02 UTC and 2025-07-30 12:30 UTC may need a replay.

• Subscribe to Lokalise's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=lokalise works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Lokalise 4

1. investigatingJul 30, 2025, 12:02 PM UTC

   We are currently investigating this issue.

   provider

2. monitoringJul 30, 2025, 12:13 PM UTC

   A fix has been implemented and we are monitoring the results.

   provider

3. resolvedJul 30, 2025, 12:30 PM UTC

   This incident has been resolved.

   provider

4. postmortemAug 13, 2025, 3:29 PM UTC

   **Summary** On July 30, 2025, Lokalise became unavailable and unstable at 11:55 UTC due to a new feature release. The new feature caused an unpredictable usage pattern with excessive memory usage and resulted in an ingress crash-looping. This was rectified and by 12:10 UTC, and Lokalise became fully operational again. **What happened?** During the update to one of our services, a configuration mismatch was introduced. The change, intended to increase the maximum allowed size, was not fully propagated across our infrastructure. This discrepancy between the service and the infrastructure layer led to excessive memory consumption, ultimately causing the service to become unstable and fully unavailable. Our team identified the problem quickly, the expected configuration was correctly propagated and by 12:10 UTC the problem was resolved. **Impact** 11:55 UTC: Lokalise's performance starts to degrade. 11:58 UTC: Lokalise is not available and an investigation is started. 12:05 UTC: Problem is identified and solution is applied. 12:10 UTC: Lokalise's performance is restored. 12:10 - 12:30 UTC: Performance is monitored and eventually the problem incident is resolved. ‌ We sincerely apologize for the disruption this caused. Thank you for your patience and continued trust in Lokalise. If you have any questions, feel free to contact us at [support@lokalise.com](mailto:support@lokalise.com).

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.