- Level
- confirmed
- Worst impact
- Degraded
- Components
- Lokalise API, Lokalise App
- Down Index
- 24of 100
What to do
Check whether you use Lokalise Lokalise API, 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 35m it lasted.
Anything that failed between 2023-06-22 17:44 UTC and 2023-06-22 18:20 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 5
- investigating
Lokalise background operations are degraded. We are investigating the functionalities affected.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
The incident has been resolved. We apologise for any inconvenience. Please, in case you have some failed background jobs, retry them.
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-b4ba16d5ba
Is Lokalise still down?
No, this incident was resolved 2023-06-22 18:20 UTC. For Lokalise's live state, see https://down.guide/lokalise.
How long did it last?
35m, from 2023-06-22 17:44 UTC to 2023-06-22 18:20 UTC, by the times Lokalise posted.
What was affected?
Lokalise named Lokalise API, 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.