Is Bitwarden Down?

No — Bitwarden is up

Bitwarden's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 251 ms

Right now

We could not read Bitwarden's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

bitwarden.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: 251 ms
Checked: 48 minutes ago

By region

Ashburn reachable, 210 ms
Chicago reachable, 181 ms
Frankfurt reachable, 96 ms
Johannesburg reachable, 410 ms
London reachable, 223 ms
Los Angeles reachable, 296 ms
São Paulo reachable, 329 ms
Tokyo reachable, 269 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	50 ms	6 ms	9 ms	180 ms
Chicago	58 ms	0 ms	4 ms	173 ms
Frankfurt	17 ms	1 ms	5 ms	86 ms
Johannesburg	183 ms	1 ms	4 ms	400 ms
London	24 ms	16 ms	21 ms	154 ms
Los Angeles	152 ms	2 ms	6 ms	283 ms
São Paulo	127 ms	2 ms	6 ms	321 ms
Tokyo	106 ms	1 ms	5 ms	258 ms

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

History

Bitwarden website availability

Measured by FlareWarden · bitwarden.com

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

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

What Bitwarden does

Bitwarden is an open source password manager syncing an encrypted vault across browser extensions, mobile and desktop apps and a web vault, with self-hosting as an option. Individuals and teams depend on it to reach every other account they own, which makes reaching it during an incident feel more urgent than most outages.

What an outage looks like

The web vault fails to load and sign-in attempts hang, while clients already synced keep filling credentials from their local copy. New items saved on one device do not reach another. The identity service failing blocks authentication specifically, so existing sessions survive while new logins do not. The command line client returns errors against the API.

What to do about it

Check status.bitwarden.com, which separates the US and EU clouds and reports the Identity Service, RESTful API and Web Vault independently of the browser, mobile, desktop and CLI clients. Your vault is cached locally, so keep using the app you already have open and avoid logging out: signing back in needs the identity service that is currently unavailable.

Is it down for everyone, or just you?

If this page says Bitwarden 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

Bitwarden outage FAQ

Can I reach my passwords while Bitwarden is down?

Yes, on any client already signed in. Bitwarden keeps an encrypted local copy of the vault, so autofill and search continue without the server. Syncing new items, signing in on a new device and the web vault all fail. This is why logging out during an incident is the one action genuinely worth avoiding.

Does an outage affect the US and EU clouds equally?

No. Bitwarden reports the US and EU clouds separately, each with its own identity service, API and web vault, and your account lives in one of them. An incident in the region you do not use has no effect. Checking the wrong region is the usual reason people disagree about whether Bitwarden is working.

Is my vault secure during a Bitwarden outage?

An availability incident does not weaken the encryption. Vault data is encrypted with keys derived from your master password before it ever reaches Bitwarden, so the service being unreachable means you cannot sync, not that anything is exposed. The practical risk is losing access to a device you have not yet set up.

Why does my browser extension work when the web vault does not?

They are separate components. The extension holds a local encrypted copy and can operate from it, while the web vault must be fetched from Bitwarden on every visit. A web vault incident therefore leaves extension users unaffected and web-only users blocked entirely, which explains very different experiences of the same outage.

Does self-hosted Bitwarden go down with the cloud service?

No. A self-hosted instance runs on your own infrastructure and is independent of Bitwarden's cloud, so status.bitwarden.com does not describe it. The exceptions are features that reach Bitwarden-operated services, such as licence validation. If your self-hosted instance is failing, the cause is on your side rather than on the status page.

How we measure this

We request Bitwarden'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 Bitwarden 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 Bitwarden 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. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Bitwarden goes down

We check Bitwarden 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