- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Lokalise App
- Regions
- us
- Down Index
- 32of 100
What to do
Check whether you use Lokalise Lokalise App in us. 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 39m it lasted.
Anything that failed between 2025-02-05 13:05 UTC and 2025-02-05 14:44 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
We are seeing issues with import and export functionality of the Lokalise app. We are investigating the issue.
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 5, 2025, we experienced a major service degradation affecting our Import functionality. The incident began at 11:00 UTC and during this time, customers were unable to perform imports in the UI or utilize Git integrations, which may have disrupted their workflows. Services have been fully restored by 13:26 UTC. The outage was caused by a misconfiguration during our migration to a new infrastructure system. To resolve the issue, our team rolled back to the previous system. In response to this incident, we are implementing several measures to prevent similar occurrences in the future: * We will enhance our deployment health checks to cover a previously missing set of dependencies, so that we can catch misconfiguration before newly deployed instances start to be used. * Additional monitoring and alerting systems will be established to quickly identify and address issues as they arise. * We are increasing coverage of our automated tests to ensure all the critical functionality is covered. We sincerely apologize for the inconvenience this incident caused to our customers. We understand how crucial these services are for your operations, and we appreciate your patience as we work to improve our systems and ensure reliable service in the future. Your trust is important to us, and we are committed to enhancing our processes to prevent such occurrences. Thank you for your understanding.
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-6e8562ba68
Is Lokalise still down?
No, this incident was resolved 2025-02-05 14:44 UTC. For Lokalise's live state, see https://down.guide/lokalise.
How long did it last?
1h 39m, from 2025-02-05 13:05 UTC to 2025-02-05 14:44 UTC, by the times Lokalise posted.
What was affected?
Lokalise named Lokalise App in us.
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.