Is Lokalise Down?

No — Lokalise is up

Lokalise's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 860 ms

Right now

The verdict is the worse of these two. How we decide

Lokalise's status page

status.lokalise.com · read 3 minutes ago · checked every 3 minutes

Operational

Lokalise's components, as its status page reports them
Component	Status
Lokalise.com the service itself	Operational
Lokalise API	Operational
Lokalise App	Operational
Lokalise OTA	Operational
Lokalise Messages	Operational

Open their status page

FlareWarden checks

lokalise.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 860 ms
Checked: 3 hours ago

By region

Amsterdam reachable, 288 ms
Chicago reachable, 475 ms
San Jose reachable, 590 ms
Singapore reachable, 1391 ms
Stockholm reachable, 295 ms
Sydney reachable, 1747 ms
Tokyo reachable, 1533 ms
Toronto reachable, 562 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	35 ms	20 ms	24 ms	178 ms
Chicago	102 ms	1 ms	5 ms	452 ms
San Jose	59 ms	7 ms	7 ms	565 ms
Singapore	79 ms	137 ms	139 ms	601 ms
Stockholm	78 ms	1 ms	4 ms	186 ms
Sydney	139 ms	163 ms	164 ms	806 ms
Tokyo	126 ms	102 ms	103 ms	950 ms
Toronto	171 ms	8 ms	9 ms	512 ms

We check that lokalise.com loads, not every feature behind it. Test it yourself

History

Incidents Lokalise reported

Since Oct 22, 15 days · from status.lokalise.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Lokalise website availability

Measured by FlareWarden · lokalise.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 777ms

Last 30 days

57-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of lokalise.com from multiple regions every 6 hours. Lokalise's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 57 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Lokalise does

Lokalise is a localization platform where product teams manage translated strings for apps, websites and documentation. Developers sync keys from their repositories, translators work in the web editor, and the finished strings are pulled back into a build or pushed to released mobile apps over the air, so the platform sits between the engineering workflow and the words users read.

What an outage looks like

The web editor fails to load or translators cannot save their work, so a translation round stalls without anything visibly breaking in the product. Builds and pipelines that pull strings through the API fail at the download step. Over-the-air translation updates stop reaching released mobile apps, which keep running on whatever they last received rather than showing an error.

What to do about it

Read status.lokalise.com, which reports Lokalise.com, Lokalise API, Lokalise App, Lokalise OTA and Lokalise Messages as separate components. Match the symptom to the row. If only OTA is affected, your team's work in the editor continues normally and the impact sits in shipped apps instead. Avoid re-running a failed string sync repeatedly during an incident, and do not merge a partial download into a release branch.

Is it down for everyone, or just you?

If this page says Lokalise is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

GitHub

GitLab

AWS

Cloudflare

Lokalise outage FAQ

Will my released mobile app break if Lokalise OTA is down?

No, and the fallback is the useful part to know. Lokalise mobile SDKs fall back to the last translations successfully fetched and stored on the device, or to the translations bundled into the app at build time. So an OTA incident freezes copy at its last known version rather than producing missing strings. Users of an already-running app are unlikely to notice anything at all.

Why is a fresh install showing older wording than my own phone?

Because the two devices have different fallbacks. A device that has used the app before holds the last translations it fetched, while a fresh install has only what shipped inside the bundle. During an OTA incident neither can update, so a new install can show wording from the release build while an existing install shows something newer. Both recover on the next successful fetch.

My build failed pulling strings from Lokalise. What should I do?

Stop the pipeline rather than shipping what it managed to download. A partial or failed download during an incident can produce a string file missing keys, and merging that into a release replaces working translations with gaps that reach users. Check the Lokalise API row on status.lokalise.com, keep the last known good string files, and re-run the sync once the component recovers.

Will translation work saved during an outage be lost?

Work that the editor confirmed as saved before an incident is stored. The risk is in-flight edits: text typed while the connection was failing may never have reached Lokalise, even where the interface still appeared to accept it. Lokalise does not publish behaviour for every failure mode, so translators should copy anything substantial elsewhere before refreshing, since refreshing is what discards unsaved local state.

Is it Lokalise or my API token?

Compare scope and the error. An expired or revoked token, a project permission change or a hit rate limit affects one integration and usually returns a specific authorisation or quota message. A Lokalise incident affects every project at once and shows on the status page. Check the status page before you rotate a token, because rotating during an incident leaves you unsure which change fixed it.

How we measure this

We request Lokalise's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Lokalise publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Lokalise itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Lokalise goes down

We check Lokalise every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required