- Level
- confirmed
- Worst impact
- Major outage
- Components
- Lokalise API, Lokalise App, Lokalise OTA
- Down Index
- 51of 100
What to do
Check whether you use Lokalise Lokalise API, Lokalise App, Lokalise OTA. 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 51m it lasted.
Anything that failed between 2025-02-10 12:38 UTC and 2025-02-10 13:29 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 9
- investigating
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We are investigating the slowness of application and Lokalise OTA service unavailable.
provider
- monitoring
We are investigating the slowness of application and Lokalise OTA service unavailable.
provider
- monitoring
We have applied the fix and monitoring for issues.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On February 10, 2025, our service experienced a 16-minute outage followed by 39 minutes of degraded functionality due to an issue with a system configuration. What happened? While improving our disaster recovery process, a misconfiguration in the system was introduced unintentionally. Initially, this did not cause issues, but when we attempted to roll back the change, it led to unexpected complications. As a result, our service platform became temporarily unavailable, requiring the reconstruction of certain system components to restore full functionality. Impact * 12:30 – 12:46 UTC: Service outage. * 12:46 – 13:25 UTC: Service degradation—APP and API were operational. Some services remained unavailable \(OTA, Workflows, Connectors, Review Center\). What we are doing to prevent this in the future We recognize the importance of this event, and we have taken steps to ensure it does not happen again. Our key actions include: * Improving validation and monitoring processes to identify configuration issues before deployment. * Enhancing our tools and automations for faster services restoration. * Implementing blue-green deployment techniques, or equivalent, for seamless system upgrades. We sincerely apologize for the disruption this caused and appreciate your patience as we work to make our systems more resilient. If you have any questions, please reach out to [support@lokalise.com](mailto:support@lokalise.com).
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-cff4843265
Is Lokalise still down?
No, this incident was resolved 2025-02-10 13:29 UTC. For Lokalise's live state, see https://down.guide/lokalise.
How long did it last?
51m, from 2025-02-10 12:38 UTC to 2025-02-10 13:29 UTC, by the times Lokalise posted.
What was affected?
Lokalise named Lokalise API, Lokalise App, Lokalise OTA.
What caused it?
Lokalise hasn't published a root cause. If it does, it shows here.
Where does this come from?
Lokalise's official status page, https://status.lokalise.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.