# Lokalise main application and API intermittent functionality

- Provider: [Lokalise](https://down.guide/providers/lokalise)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 28m
- started 2025-07-30 12:02 UTC
- Lokalise API, Lokalise App
- us
- id: DWN-1ed162392a
- Official page: https://stspg.io/p9kkb1q31d14

## Root cause
> Summary On July 30, 2025, Lokalise became unavailable and unstable at 11:55 UTC due to a new feature release.

Category: Deploy or config change. [Postmortem](https://stspg.io/p9kkb1q31d14)

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

### 2025-07-30 12:13 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2025-07-30 12:30 UTC: resolved
This incident has been resolved.

### 2025-08-13 15:29 UTC: postmortem
Summary
On July 30, 2025, Lokalise became unavailable and unstable at 11:55 UTC due to a new feature release. The new feature caused an unpredictable usage pattern with excessive memory usage and resulted in an ingress crash-looping. This was rectified and by 12:10 UTC, and Lokalise became fully operational again.
What happened?
During the update to one of our services, a configuration mismatch was introduced. The change, intended to increase the maximum allowed size, was not fully propagated across our infrastructure. This discrepancy between the service and the infrastructure layer led to excessive memory consumption, ultimately causing the service to become unstable and fully unavailable.
Our team identified the problem quickly, the expected configuration was correctly propagated and by 12:10 UTC the problem was resolved.
Impact
11:55 UTC: Lokalise's performance starts to degrade.
11:58 UTC: Lokalise is not available and an investigation is started.
12:05 UTC: Problem is identified and solution is applied.
12:10 UTC: Lokalise's performance is restored.
12:10 - 12:30 UTC: Performance is monitored and eventually the problem incident is resolved.
‌
We sincerely apologize for the disruption this caused. Thank you for your patience and continued trust in Lokalise. If you have any questions, feel free to contact us at \[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-1ed162392a), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.