- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Lokalise. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.
Anything that failed between 2023-05-26 02:35 UTC and 2023-05-26 02:55 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 2
- investigating
There is an issue accessing Lokalise's OTA v3 service. We are currently working on identifying the root cause and will provide more information as soon as possible.
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-5b44917965
Is Lokalise still down?
No, this incident was resolved 2023-05-26 02:55 UTC. For Lokalise's live state, see https://down.guide/providers/lokalise.
How long did it last?
20m, from 2023-05-26 02:35 UTC to 2023-05-26 02:55 UTC, by the times Lokalise posted.
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.