- Level
- confirmed
- Worst impact
- Degraded
- Components
- Lokalise App
- Down Index
- 16of 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 4m it lasted.
Anything that failed between 2024-04-01 15:11 UTC and 2024-04-01 15:15 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
- identified
There is an issue affecting the performance of the Lokalise Github, GitLab and Bitbucket apps. We are currently working on identifying the root cause and fixing it. We will provide more information as soon as possible.
provider
- monitoring
A fix has been implemented and we are monitoring the results and performance of the the Lokalise Github, GitLab and Bitbucket apps.
provider
- resolved
Lokalise Github, GitLab and Bitbucket are fully operational.
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-e55d73d21b
Is Lokalise still down?
No, this incident was resolved 2024-04-01 15:15 UTC. For Lokalise's live state, see https://down.guide/lokalise.
How long did it last?
4m, from 2024-04-01 15:11 UTC to 2024-04-01 15:15 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.