We started checking Lokalise on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Lokalise reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Lokalise's own status page declared. Below it, any public chatter we saw about Lokalise and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Lokalise's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Lokalise in the last 24 hours, which is not evidence that nothing is wrong.
Lokalise's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Lokalise's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Lokalise next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
421
US-West
99.68%
316
Europe
100.00%
290
Asia-Pacific
100.00%
177
Their declared record
Lokalise's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Lokalise application is experiencing partial email delivery issuesPartial outage
Sep 14, 2026, 12:22 PM UTC to Sep 14, 2026, 3:22 PM UTC (3h 1m)resolved
their latest update (Sep 14, 2026, 3:22 PM UTC): This incident has been resolved.
Lokalise search service outageMajor outage
Aug 17, 2026, 3:06 AM UTC to Aug 17, 2026, 3:48 AM UTC (43 min)resolved
their latest update (Aug 17, 2026, 3:48 AM UTC): This incident has been resolved.
Lokalise application and API are unavailableMajor outage
Feb 4, 2026, 4:18 PM UTC to Feb 4, 2026, 5:07 PM UTC (48 min)postmortem published
their latest update (Feb 13, 2026, 3:49 PM UTC): On 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…
Lokalise application is unavailableMajor outage
Jan 26, 2026, 3:52 PM UTC to Jan 26, 2026, 4:32 PM UTC (40 min)postmortem published
their latest update (Feb 2, 2026, 4:59 PM UTC): On 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?**
**…
Lokalise application is unavailableMajor outage
Nov 27, 2025, 8:23 AM UTC to Nov 27, 2025, 8:43 AM UTC (20 min)resolved
their latest update (Nov 27, 2025, 8:43 AM UTC): This incident has been resolved.
Issues with content integrations exports to Lokalise applicationPartial outage
Oct 23, 2025, 9:11 AM UTC to Oct 23, 2025, 10:00 AM UTC (49 min)resolved
their latest update (Oct 23, 2025, 10:00 AM UTC): This incident has been resolved.
Workflows are not running and feature is unaccessibleMinor incident
Oct 7, 2025, 12:42 PM UTC to Oct 7, 2025, 1:23 PM UTC (41 min)resolved
their latest update (Oct 7, 2025, 1:23 PM UTC): This incident has been resolved.
Workflows are not running and feature is unaccessibleMinor incident
Sep 17, 2025, 3:20 PM UTC to Sep 17, 2025, 4:14 PM UTC (54 min)resolved
their latest update (Sep 17, 2025, 4:14 PM UTC): This incident has been resolved.
Lokalise main application outageMajor outage
Sep 8, 2025, 10:08 AM UTC to Sep 8, 2025, 10:18 AM UTC (10 min)postmortem published
their latest update (Sep 26, 2025, 11:16 AM UTC): **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…
Lokalise main application and API intermittent functionalityPartial outage
Jul 30, 2025, 12:02 PM UTC to Jul 30, 2025, 12:30 PM UTC (28 min)postmortem published
their latest update (Aug 13, 2025, 3:29 PM UTC): **Summary**
On July 30, 2025, Lokalise became unavailable and unstable at 11:55 UTC due to a new feature release. The new feature caused an unpredictable usage pattern with excessive memory usage and resulted in an ingress crash-looping. This was rectified and by 12:10 UTC, and …
Showing the 10 most recent of 50 incidents Lokalise has declared in the history we hold.
These entries are Lokalise's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Lokalise's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.