https://approjects-vendor-status-watch.static.hf.space/v/lokalise.htmlIncidents from Lokalise's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/z6bfr2khqswhlokalise:2026-09-14T12:22:18.627ZMon, 14 Sep 2026 12:22:18 +0000This incident has been resolved.https://stspg.io/1c40wl9dhs9hlokalise:2026-08-17T03:06:00.134ZMon, 17 Aug 2026 03:06:00 +0000This incident has been resolved.https://stspg.io/3h03yb8hkrcmlokalise:2026-02-04T16:18:38.000ZWed, 04 Feb 2026 16:18:38 +0000On February 4, 2026, Lokalise experienced a brief service interruption where both the application and API were unavailable for approximately 10 minutes. The incident began at 16:18 UTC and was fully resolved within 12 minutes as our engineering team restored service functionality. **What happened?** **The Cause:** A configuration update intended to enable new application metrics unexpectedly triggered a series of intensive, unoptimized database scans. This resulted in an immediate exhaustion of our backend processing capacity, preventing the web server from fulfilling incoming requests. **The Fix:** Our team identified the faulty configuration release and promptly initiated a rollback to the last known stable state. Once service was restored, a permanent fix was deployed to remove the phttps://stspg.io/vrysvtwtmy53lokalise:2026-01-26T15:52:09.000ZMon, 26 Jan 2026 15:52:09 +0000On 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 affectedhttps://stspg.io/rsfflzdggm96lokalise:2025-11-27T08:23:03.000ZThu, 27 Nov 2025 08:23:03 +0000This incident has been resolved.https://stspg.io/js6x7rc3b0srlokalise:2025-10-23T09:11:54.271ZThu, 23 Oct 2025 09:11:54 +0000This incident has been resolved.https://stspg.io/7swmg0qcqp5flokalise:2025-10-07T12:42:20.000ZTue, 07 Oct 2025 12:42:20 +0000This incident has been resolved.https://stspg.io/5snwjhfgfbbzlokalise:2025-09-17T15:20:33.789ZWed, 17 Sep 2025 15:20:33 +0000This incident has been resolved.https://stspg.io/yks1dy5r5t79lokalise:2025-09-08T10:08:56.546ZMon, 08 Sep 2025 10:08:56 +0000**What happened** On Sep 8, 2025 at 09:59 UTC, a change introduced in our system unexpectedly missed a Feature Toggle condition, which caused a spike in the number of requests to one of our internal services. This led to degraded performance and temporary unavailability of both the Lokalise App and API. Our monitoring and alerting systems immediately triggered the alerts, allowing us to quickly identify and restore the service. **Impact** The Lokalise App was unavailable for approximately **9 minutes**, and the API experienced downtime for about **6 minutes** within that window. No customer data was lost or corrupted. **What we are doing to prevent this in the future** We are implementing stricter safeguards around feature rollout validation, improving how our services handle spike