Localize Outage History

Localize is up right now

Localize had 1 outage in the last 2 years totaling 6h 35m of downtime — averaging 0 incidents per month.

There was 1 Localize outage since November 18, 2025 totaling 6h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://localizestatus.com

Major November 18, 2025

Upstream provider impacting Localize services

Detected by Pingoru
Nov 18, 2025, 01:06 PM UTC
Resolved
Nov 18, 2025, 07:42 PM UTC
Duration
6h 35m
Affected: Localize LibraryTranslation Management DashboardBackend APIPhrase IngestionTranslation Delivery NetworkRealtime Translation DeploymentDashboard File Import & ExportIn-Context EditorContent Delivery Provider
Timeline · 6 updates
  1. identified Nov 18, 2025, 01:06 PM UTC

    Localize is impacted by the Cloudflare Global Network Experiencing Issues: https://www.cloudflarestatus.com/

  2. identified Nov 18, 2025, 03:09 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Nov 18, 2025, 03:15 PM UTC

    We rerouted the majority of traffic around Cloudflare, bringing the system back to operational, but degraded. There are signs that Cloudflare is coming back to fully operational. When they are back to stable, we will re-route traffic back through Cloudflare. Degraded performance is related to the intermittent nature of all third-party services. We will continue to watch Cloudflare's status and adjust as necessary. An update will be sent around 11 AM Eastern.

  4. monitoring Nov 18, 2025, 04:11 PM UTC

    We've updated most of our statuses to operational. We are continuing to monitor the situation with Cloudflare and will post updates as they become available.

  5. monitoring Nov 18, 2025, 06:11 PM UTC

    Cloudflare, our upstream CDN provider, has resolved their delivery issues. We have began routing traffic through Cloudflare once again, and will continue to monitor the situation.

  6. resolved Nov 18, 2025, 07:42 PM UTC

    The upstream provider issue has been resolved and functionality is back to normal for all users.

Read the full incident report →