- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Lokalise App
- Down Index
- 33of 100
What to do
Check whether you use Lokalise Lokalise App. 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 1h 57m it lasted.
Anything that failed between 2025-02-19 08:58 UTC and 2025-02-19 10:56 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 7
- investigating
Some actions like file import, bulk actions are not being processed. We are investigating this issue.
provider
- investigating
All functionality that is relying on background processes is affected. We are continuing to investigate this issue.
provider
- investigating
We have restored the functionality to unblock customers. We are continuing to investigate the root cause.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On February 19, 2025, our service experienced performance degradation in background tasks that impacted essential processes including file imports, synchronization with content integrations, and some bulk actions. **What happened?** A faulty release unintentionally caused our background tasks to stop working as expected. Although the issue did not appear immediately, it became noticeable the next morning. Our team promptly investigated and mitigated the problem, quickly restoring full service. **Impact** * 08:54 UTC to 09:23 UTC: Customers experienced slower performance. **What we are doing to prevent this in the future** We recognize the importance of this event, and we are taking steps to ensure it does not happen again. Our key actions include: * Additional monitoring of background tasks to quickly spot issues * Exploring options for our system to recover automatically from minor errors. We sincerely apologize for the inconvenience this incident caused. Thank you for your patience and understanding as we continue to improve Lokalise’s resilience and reliability. If you have any questions or require further assistance, please contact [hello@lokalise.com](mailto:hello@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-63025e56b2
Is Lokalise still down?
No, this incident was resolved 2025-02-19 10:56 UTC. For Lokalise's live state, see https://down.guide/lokalise.
How long did it last?
1h 57m, from 2025-02-19 08:58 UTC to 2025-02-19 10:56 UTC, by the times Lokalise posted.
What was affected?
Lokalise named Lokalise App.
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.