Lokalise application is unavailable

What to do

• Check whether you use Lokalise Lokalise API, 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 40m it lasted.

  Anything that failed between 2026-01-26 15:52 UTC and 2026-01-26 16:32 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 4

1. investigatingJan 26, 2026, 3:52 PM UTC

   We are currently investigating this issue.

   provider

2. investigatingJan 26, 2026, 4:06 PM UTC

   We are continuing to investigate this issue.

   provider

3. resolvedJan 26, 2026, 4:32 PM UTC

   This incident has been resolved.

   provider

4. postmortemFeb 2, 2026, 4:59 PM UTC

   On January 26, 2026, Lokalise experienced a service outage and performance degradation between 15:52 UTC and 16:32 UTC. During this time, the Lokalise application was unavailable, and users of the API experienced intermittent connectivity and high latency. What happened? The Cause: The incident was triggered during a migration of our monitoring systems. A configuration mismatch caused a high volume of internal network requests to fail, which subsequently overwhelmed our internal DNS services. This prevented various parts of our infrastructure from communicating with one another, including our primary databases and application services. The Fix: Our engineering team identified the source of the traffic and disabled the legacy monitoring configuration. We also rotated affected infrastructure nodes and adjusted our service scaling to alleviate pressure on our databases. These actions restored normal communication between our services, bringing the platform back to full operational status. Timeline \(UTC\): * 15:52: Service degradation and unavailability detected and investigation initiated. * 16:24: Root cause identified as internal network congestion impacting service connectivity. * 16:27: Corrective actions implemented; service begins to stabilize. * 16:32: Full service restored and performance monitored for stability. What we are doing to prevent this in the future * Enhancing scaling capabilities: We are upgrading our internal DNS services to scale horizontally, ensuring they can handle unexpected spikes in traffic without impacting the wider platform. * Improving resource monitoring: We are implementing additional alerting for resource exhaustion to identify and mitigate infrastructure bottlenecks before they impact service availability. * Refining deployment procedures: We are updating our internal documentation and validation steps to ensure infrastructure dependencies are strictly coordinated during system migrations. We sincerely apologize for the disruption this incident caused to your workflow. We understand how critical Lokalise is to your operations and are committed to improving our system's resilience to prevent a recurrence. If you have any questions or require further assistance, please contact us at [hello@lokalise.com](mailto:hello@lokalise.com).

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.