Vendor Status Watch

← all vendors

Lokalise status history

Current state: operational — “All Systems Operational” per https://status.lokalise.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
2incidents, last 90 days
9incidents on record
Incidents per week, last 12 weeks:

How long do Lokalise incidents last?

42 minmedian incident duration9 measured
54 min90th percentile1 in 10 ran longer
42 minmedian, major/critical only7 incidents

From 9 incidents with a vendor-posted start and resolve time. Longest on record: Lokalise application is experiencing partial email delivery issues — 3.0 h (2026-09-14 12:22 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (9)

StartedIncidentStatusImpactDuration
2026-09-14 12:22 UTCLokalise application is experiencing partial email delivery issuesresolvedmajor3 h 00 min
2026-08-17 03:06 UTCLokalise search service outageresolvedcritical42 min
2026-02-04 16:18 UTCLokalise application and API are unavailablepostmortemcritical48 min
2026-01-26 15:52 UTCLokalise application is unavailablepostmortemcritical40 min
2025-11-27 08:23 UTCLokalise application is unavailableresolvedcritical20 min
2025-10-23 09:11 UTCIssues with content integrations exports to Lokalise applicationresolvedmajor48 min
2025-10-07 12:42 UTCWorkflows are not running and feature is unaccessibleresolvedminor40 min
2025-09-17 15:20 UTCWorkflows are not running and feature is unaccessibleresolvedminor54 min
2025-09-08 10:08 UTCLokalise main application outagepostmortemcritical9 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Lokalise with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "lokalise"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}