Lokalise logo

Is Lokalise Down?

SaaSLive status, outages, and incident history

No. Lokalise is up right now.

Every monitored Lokalise system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 6m agoLive · 60s while moving

Know the moment Lokalise breaks

Lokalise is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Lokalise status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Lokalise Component Status

The main Lokalise systems on this page. All 5 are operational right now.

5operational
Lokalise API
Operational
Lokalise App
Operational
Lokalise Messages
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Lokalise OTA, Lokalise.com.

See all of them free

Component statuses may change independently during partial outages.

Recent Lokalise Outages & Incidents

Incident history from the official Lokalise status page, including resolution updates.

Lokalise application is experiencing partial email delivery issuesResolved Sep 14, 2026 · 3h 0mResolved

This incident has been resolved. --- [2026-09-14T15:14:17.163Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-09-14T15:14:10.473Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-14T13:28:00.653Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-14T12:22:18.689Z] (investigating) We are currently investigating this issue.

Lokalise search service outageResolved Aug 17, 2026 · 42 minResolved

This incident has been resolved. --- [2026-08-17T03:06:00.217Z] (investigating) We are currently investigating this issue.

Scheduled Maintenance for Content IntegrationsScheduled for Aug 11, 2026 · 2h 0mScheduled

The scheduled maintenance has been completed. --- [2026-08-11T10:26:26.490Z] (verifying) Verification is currently underway for the maintenance items. --- [2026-08-11T09:42:43.639Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-08-11T09:30:07.350Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-08-07T16:18:14.749Z] (scheduled) On Tuesday, August 11, between 10:30 and 12:30 UTC, we will be performing scheduled maintenance to upgrade the underlying infrastructure that powers several of our content integrations. During this 2-hour window, the affected integrations will be temporarily unavailable, and data synchronization for these specific apps will be paused. The core Lokalise web application and API will remain fully operational during this time. Please note that this maintenance only impacts these specific integrations: - Braze CE - CleverTap - Contentful Native - Customer.io - Ditto - Freshdesk - Iterable - Marketo - Storyblok CE - Webflow We recommend pausing any automated workflows or manual syncs connected to these integrations during the maintenance window to prevent any failed actions. We appreciate your patience and understanding as we work to improve the performance and reliability of our services. If you have any questions or concerns, please reach out to our Support team at hello@lokalise.com.

Lokalise Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Lokalise incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

Live Lokalise Outage Reports

Problems reported by engineers using Lokalise. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Lokalise problems reported yet.

Something wrong with Lokalise on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Lokalise

Lokalise publishes a public status page at status.lokalise.com covering 5 components, including Lokalise.com, Lokalise API and Lokalise App. PulsAPI tracks Lokalise outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Lokalise uptime at 100.00%. Response times, incident history, and SLA tracking for Lokalise are available on the PulsAPI dashboard.

Lokalise Status FAQ

Is Lokalise down right now?

The verdict at the top of this page comes from the latest poll of the official Lokalise status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Lokalise is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Lokalise recovers.

How do I check Lokalise uptime history?

PulsAPI tracks Lokalise uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Lokalise changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Lokalise outages?

PulsAPI reads the official Lokalise status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Lokalise components?

Yes. PulsAPI monitors 5 individual Lokalise components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Lokalise goes down?

Yes. Create a free account and subscribe to Lokalise: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Lokalise to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Lokalise problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Lokalise?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Lokalise plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Lokalise with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services