- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Lokalise API
- Down Index
- 36of 100
What to do
Check whether you use Lokalise Lokalise API. 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 6h 14m it lasted.
Anything that failed between 2025-05-08 07:13 UTC and 2025-05-08 13:27 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 3
- investigating
We are currently investigating this issue.
provider
- identified
We have identified the issue, and new async exports are now processing fine. We are implementing a fix to allow stuck processes to finish.
provider
- resolved
This incident has been resolved.
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-d91df3d758
Is Lokalise still down?
No, this incident was resolved 2025-05-08 13:27 UTC. For Lokalise's live state, see https://down.guide/lokalise.
How long did it last?
6h 14m, from 2025-05-08 07:13 UTC to 2025-05-08 13:27 UTC, by the times Lokalise posted.
What was affected?
Lokalise named Lokalise API.
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.