Is LastPass Down?

No — LastPass is up

Reachable from all 8 checked regions

Average response time: 1808ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://lastpass.statuspage.io

LastPass uptime

100%

Last 7 days

99.89%

Last 30 days

99.90%

Last 90 days

1605ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 31 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

1879ms

DNS 39ms TCP 2ms TLS 7ms TTFB 1867ms

lhr

1794ms

DNS 324ms TCP 2ms TLS 7ms TTFB 1778ms

nrt

1771ms

DNS 225ms TCP 1ms TLS 6ms TTFB 1762ms

ord

1488ms

DNS 50ms TCP 1ms TLS 6ms TTFB 1480ms

sin

1737ms

DNS 262ms TCP 1ms TLS 15ms TTFB 1729ms

sjc

1659ms

DNS 91ms TCP 1ms TLS 6ms TTFB 1650ms

syd

2206ms

DNS 351ms TCP 1ms TLS 9ms TTFB 2197ms

yyz

1935ms

DNS 165ms TCP 13ms TLS 29ms TTFB 1881ms

What LastPass does

LastPass keeps passwords, passkeys and secure notes in an encrypted vault reached through a browser extension, a mobile app or the web vault. Companies run it as the shared credential store for staff and often wire it to an identity provider for single sign-on. When it is unreachable, people cannot retrieve the credentials they need to sign in to everything else.

What an outage looks like

The browser extension shows a spinner or reports that it cannot reach the server, and autofill stops offering saved logins. Web vault sign-in hangs after the master password is accepted, which points at the multifactor step rather than the password. Admins lose the Admin Console while ordinary users keep whatever the extension has already cached. Logins federated through an identity provider fail separately from direct logins.

What to do about it

lastpass.statuspage.io splits the service into 33 components, with Login and Federated Login tracked apart and separate rows for the United States, Europe and Australia, so read the region your account sits in. An extension that is already signed in keeps serving cached entries, so avoid signing out mid-incident. Note that status.lastpass.com answers automated clients with HTTP 403; the statuspage host is the one that responds.

Is it down for everyone, or just you?

If this page says LastPass 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

LastPass outage FAQ

I cannot log in to my vault. Is LastPass down or is my master password wrong?

A wrong master password is rejected immediately with an error. An outage looks different: the page accepts the password and then hangs, or the extension reports that it cannot reach the server. LastPass tracks Login and MFA as separate components, so a sign-in that stalls after the password is accepted usually means the multifactor step, not the password itself.

Can I still get to my passwords during a LastPass outage?

Often yes. The browser extension holds a local encrypted copy of the vault, so entries you have already synced stay available while the extension remains signed in. Signing out or restarting the browser clears that state and forces a server round trip that will fail. Keep the session open until the incident clears.

Does a LastPass outage affect single sign-on to other apps?

It can, if your organisation uses LastPass SSO or its federated login. LastPass tracks Federated Login as its own component group alongside integrations with Okta, Microsoft Entra, Ping One, Ping Federate, OneLogin and ADFS. If sign-in to a downstream app breaks at the same time, check whether that app authenticates through LastPass before treating it as a separate outage.

Is it down for everyone or only my region?

LastPass reports its vault infrastructure per region, with distinct components for the United States, Europe and Australia. An incident confined to one of those leaves users elsewhere unaffected, which is why colleagues in another office may report no problem at all. Check the row matching where your account was provisioned rather than the overall headline.

Do my saved passwords stay safe during an outage?

An availability incident is not a disclosure of data. Vault contents are encrypted with a key derived from your master password before they leave the device, so a service that is unreachable is a service that cannot serve your data, not one that is handing it out. Treat outage and breach as separate events with separate notifications.

How we measure this

We request LastPass's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
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. We only change the 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 LastPass publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when LastPass goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required