Last checked
Continuous localization platform for faster shipping of localized products.
Experiencing an issue?

Is Lokalise down?
Status unavailable
Share your experience to help others stay informed.
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
| Component name | Status |
|---|---|
| Lokalise Lokalise.com status | Up |
| Lokalise API status | Up |
| Lokalise App status | Up |
| Lokalise OTA status | Up |
| Lokalise Messages status | Up |
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 3h 1m | Yes | Major | ||
| 43m | Yes | Critical | ||
| 48m | Yes | Critical | ||
| 40m | Yes | Critical | ||
| 20m | Yes | Critical | ||
| 49m | Yes | Major | ||
| 41m | Yes | Minor | ||
| 54m | Yes | Minor |
Uptimus monitors Lokalise through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 5 monitored components, 52 indexed incidents, 28 maintenance windows and 4 days of known history.
Uptimus is an independent monitoring service and is not affiliated with Lokalise. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when Lokalise or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 52 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Lokalise application is experiencing partial email delivery issues”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 5 Lokalise components: Lokalise.com, Lokalise API, Lokalise App, Lokalise OTA. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Planned work published by the official provider.
On October 21, we had to take Lokalise offline for 1 hour and 30 minutes at short notice to apply an emergency security fix. We apologize for any disruptions that may have been caused. **What happened.** On October 21 at 14:00 UTC the PHP project released fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619 \(CVSS 9.2\). Both allow unauthenticated remote code execution, meaning an attacker could run code on an unpatched server without any credentials. Details leaked publicly on October 20, before a fix was available, and widespread exploitation was expected as soon as the fix was released. Parts of the Lokalise platform run on PHP, so these vulnerabilities applied to us. **What we did.** As soon as the advance notice was published, we prepared the upgrade and scheduled an emergency maintenance window to begin at 14:00 UTC, when the patched versions became available. We took the Lokalise application, API and Lokalise Messages offline, updated PHP to the fixed versions across all affected systems, verified the deployment, and restored service at 15:30 UTC. Delaying would have left a known critical vulnerability open while attacks were already being reported elsewhere. A short service downtime was the lower risk. **More information** PHP advisory: [https://www.php.net/archive/2026.php#2026-10-21-5](https://www.php.net/archive/2026.php#2026-10-21-5) If your security team would like a summary for your vendor risk records, or wants to discuss this with us, please contact your Customer Success Manager or [[email protected]](mailto:[email protected]). Magnus Slind-Naslund CTO at Lokalise
Started Oct 21, 2026, 02:00 PM UTC · Resolved Oct 21, 2026, 04:00 PM UTC
The scheduled maintenance has been completed.
Started Aug 11, 2026, 10:30 AM UTC · Resolved Aug 11, 2026, 10:31 AM UTC
The scheduled maintenance has been completed with less than 3 minutes downtime.
Started Nov 8, 2025, 10:00 AM UTC · Resolved Nov 8, 2025, 01:10 PM UTC
The scheduled maintenance has been completed.
Started Jul 26, 2025, 09:00 AM UTC · Resolved Jul 26, 2025, 12:20 PM UTC
The scheduled maintenance for the Lokalise application and API, originally planned for July 19th, 2025 between 09:00 - 12:00 UTC, has been cancelled. The Lokalise application and API will remain fully operational during this time. We are postponing this work to a later date and will announce the new schedule once it is confirmed. We apologize for any inconvenience this change may cause. If you have any questions, please reach out to our team at [email protected].
Started Jul 14, 2025, 04:06 PM UTC · Resolved Jul 18, 2025, 02:04 PM UTC
The scheduled maintenance has been completed.
Started Feb 22, 2025, 09:00 AM UTC · Resolved Feb 23, 2025, 03:36 PM UTC
The scheduled maintenance has been completed.
Started Aug 17, 2024, 09:00 AM UTC · Resolved Aug 17, 2024, 10:20 AM UTC
The scheduled maintenance has been completed.
Started Apr 15, 2023, 11:00 AM UTC · Resolved Apr 15, 2023, 11:40 AM UTC
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for Lokalise | Included | Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
| 24-hour report activity and regional outage view | Included | Included |
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
| Email, push and webhook alerts from the same workspace | Included | Separate product |
| Official incident updates and status timeline for Lokalise | Included | User-report led |
| Component health and maintenance windows kept separate | Included | Limited on public pages |
The current official status of Lokalise cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Lokalise in the last 24 hours. Last official check: .
Share your thoughts about Lokalise
Be the first to comment!
Rate this service
No reviews yet
Discover other popular services and their current status