Lokalise Outage History
8 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Lokalise Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Emergency Platform MaintenanceScheduled maintenance is still in progress. We will provide updates as necessary. | 3h 0m | Scheduled |
| Sep 14, 2026 | Lokalise application is experiencing partial email delivery issuesThis incident has been resolved. | 3h 0m | Resolved |
| Aug 17, 2026 | Lokalise search service outageThis incident has been resolved. | 42 min | Resolved |
| Aug 11, 2026 | Scheduled Maintenance for Content IntegrationsThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 4, 2026 | Lokalise application and API are unavailableOn 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… | 48 min | Resolved |
| Jan 26, 2026 | Lokalise application is unavailableOn 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… | 40 min | Resolved |
| Nov 27, 2025 | Lokalise application is unavailableThis incident has been resolved. | 20 min | Resolved |
| Nov 8, 2025 | Lokalise application and API maintenance (1 hour downtime)The scheduled maintenance has been completed with less than 3 minutes downtime. | 1h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Lokalise incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Lokalise Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Lokalise acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Lokalise outage in this window ran 3h, against a mean recovery of 1h 26m. If you depend on Lokalise in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.