Lokalise Outage History

Lokalise is up right now

Lokalise had 5 outages in the last 2 years totaling 6h 0m of downtime — averaging 0.2 incidents per month.

There were 5 Lokalise outages since October 23, 2025 totaling 6h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lokalise.com

Major September 14, 2026

Lokalise application is experiencing partial email delivery issues

Detected by Pingoru
Sep 14, 2026, 12:22 PM UTC
Resolved
Sep 14, 2026, 03:22 PM UTC
Duration
3h
Affected: Lokalise APILokalise App
Timeline · 5 updates
  1. investigating Sep 14, 2026, 12:22 PM UTC

    We are currently investigating this issue.

  2. identified Sep 14, 2026, 01:28 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 14, 2026, 03:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Sep 14, 2026, 03:14 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Sep 14, 2026, 03:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 17, 2026

Lokalise search service outage

Detected by Pingoru
Aug 17, 2026, 03:06 AM UTC
Resolved
Aug 17, 2026, 03:48 AM UTC
Duration
42m
Affected: Lokalise.com
Timeline · 2 updates
  1. investigating Aug 17, 2026, 03:06 AM UTC

    We are currently investigating this issue.

  2. resolved Aug 17, 2026, 03:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 23, 2025

Issues with content integrations exports to Lokalise application

Detected by Pingoru
Oct 23, 2025, 09:11 AM UTC
Resolved
Oct 23, 2025, 10:00 AM UTC
Duration
48m
Affected: Lokalise App
Timeline · 3 updates
  1. investigating Oct 23, 2025, 09:11 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 23, 2025, 09:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 23, 2025, 10:00 AM UTC

    This incident has been resolved.

Read the full incident report →