Is Bitwarden Down?

No — Bitwarden is up

Reachable from all 8 checked regions

Average response time: 138ms

Last checked 59 minutes ago · checks run every 6 hours

Official status page: https://status.bitwarden.com

Bitwarden uptime

99.54%

Last 7 days

99.85%

Last 30 days

99.85%

Last 90 days

203ms

Avg response, 30 days

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

30-day history

4-day clean streak

Jul 19 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.

dfw

99ms

DNS 45ms TCP 0ms TLS 4ms TTFB 75ms

ewr

118ms

DNS 24ms TCP 6ms TLS 10ms TTFB 80ms

fra

113ms

DNS 40ms TCP 0ms TLS 4ms TTFB 96ms

gru

231ms

DNS 159ms TCP 3ms TLS 8ms TTFB 201ms

iad

138ms

DNS 32ms TCP 7ms TLS 17ms TTFB 93ms

jnb

248ms

DNS 15ms TCP 23ms TLS 27ms TTFB 126ms

lax

112ms

DNS 35ms TCP 1ms TLS 6ms TTFB 83ms

lhr

74ms

DNS 21ms TCP 0ms TLS 4ms TTFB 56ms

nrt

75ms

DNS 23ms TCP 1ms TLS 5ms TTFB 52ms

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 all 18 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 — 8 of them answered the most recent check.
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 Bitwarden 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 Bitwarden goes down

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

Start Free Monitoring

Free plan available No credit card required