Lokalise Outage History

Lokalise is up right now

Lokalise had 15 outages in the last 2 years totaling 58h 10m of downtime — averaging 0.6 incidents per month.

There were 15 Lokalise outages since December 20, 2024 totaling 58h 10m 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 →

Minor October 7, 2025

Workflows are not running and feature is unaccessible

Detected by Pingoru
Oct 07, 2025, 12:42 PM UTC
Resolved
Oct 07, 2025, 01:23 PM UTC
Duration
40m
Affected: Lokalise App
Timeline · 3 updates
  1. investigating Oct 07, 2025, 01:13 PM UTC

    We are currently investigating this issue.

  2. monitoring Oct 07, 2025, 01:22 PM UTC

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

  3. resolved Oct 07, 2025, 01:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 23, 2025

Async exports aren't processing

Detected by Pingoru
May 23, 2025, 05:57 AM UTC
Resolved
May 23, 2025, 07:38 AM UTC
Duration
1h 40m
Affected: Lokalise API
Timeline · 3 updates
  1. investigating May 23, 2025, 05:57 AM UTC

    We are currently investigating this issue.

  2. monitoring May 23, 2025, 07:17 AM UTC

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

  3. resolved May 23, 2025, 07:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 7, 2025

Async exports weren't processing

Detected by Pingoru
May 07, 2025, 07:15 AM UTC
Resolved
May 07, 2025, 07:15 AM UTC
Duration
—
Timeline · 1 update
  1. resolved May 07, 2025, 01:18 PM UTC

    Async export processes that have been triggered between 07:15 and 08:15 UTC time today got stuck and didn’t complete. We will share more details in the postmortem message.

Read the full incident report →

Major March 17, 2025

Lokalise main application performance degradation

Detected by Pingoru
Mar 17, 2025, 01:33 PM UTC
Resolved
Mar 17, 2025, 02:45 PM UTC
Duration
1h 11m
Affected: Lokalise App
Timeline · 3 updates
  1. investigating Mar 17, 2025, 01:33 PM UTC

    Lokalise application is experiencing issues with processing search, filtering and statistics in the UI. We are currently investigating this issue.

  2. monitoring Mar 17, 2025, 02:29 PM UTC

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

  3. resolved Mar 17, 2025, 02:45 PM UTC

    This incident has been resolved.

Read the full incident report →