# Major service outage

- Provider: [Lokalise](https://down.guide/lokalise)
- Level: confirmed
- Impact: Major outage
- lasted 51m
- started 2025-02-10 12:38 UTC
- Lokalise API, Lokalise App, Lokalise OTA
- id: DWN-cff4843265
- Official page: https://stspg.io/lkzdkgn61q6q

## Updates from Lokalise
### 2025-02-10 12:38 UTC: investigating
We are currently investigating this issue.

### 2025-02-10 12:40 UTC: investigating
We are continuing to investigate this issue.

### 2025-02-10 12:50 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2025-02-10 12:52 UTC: monitoring
We are continuing to monitor for any further issues.

### 2025-02-10 13:04 UTC: monitoring
We are investigating the slowness of application and Lokalise OTA service unavailable.

### 2025-02-10 13:13 UTC: monitoring
We are investigating the slowness of application and Lokalise OTA service unavailable.

### 2025-02-10 13:20 UTC: monitoring
We have applied the fix and monitoring for issues.

### 2025-02-10 13:29 UTC: resolved
This incident has been resolved.

### 2025-02-14 08:59 UTC: postmortem
On February 10, 2025, our service experienced a 16-minute outage followed by 39 minutes of degraded functionality due to an issue with a system configuration.
What happened? 
While improving our disaster recovery process, a misconfiguration in the system was introduced unintentionally. Initially, this did not cause issues, but when we attempted to roll back the change, it led to unexpected complications. As a result, our service platform became temporarily unavailable, requiring the reconstruction of certain system components to restore full functionality.
Impact
\* 12:30 – 12:46 UTC: Service outage.
\* 12:46 – 13:25 UTC: Service degradation—APP and API were operational. Some services remained unavailable \\(OTA, Workflows, Connectors, Review Center\\).
What we are doing to prevent this in the future 
We recognize the importance of this event, and we have taken steps to ensure it does not happen again. Our key actions include:
\* Improving validation and monitoring processes to identify configuration issues before deployment.
\* Enhancing our tools and automations for faster services restoration.
\* Implementing blue-green deployment techniques, or equivalent, for seamless system upgrades.
We sincerely apologize for the disruption this caused and appreciate your patience as we work to make our systems more resilient. If you have any questions, please reach out to \[support@lokalise.com\](mailto:support@lokalise.com).

From the builder: does your app depend on Lokalise? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=lokalise) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Lokalise.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-cff4843265), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.