Skip to content

Outage tracker / Bitwarden

Is Bitwarden down?

I'm having a problem

Vendor reports no incidentWhat Bitwarden reports

Bitwarden reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:13 UTC.

Bitwarden's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Bitwarden pass from all 4 regions we check.

As of Nov 5, 2026, 2:13 PM UTC, RealUptime's checks of Bitwarden passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:13 PM UTC
US-East565 msChecks passing
US-West6199 msChecks passing
Europe819 msChecks passing
Asia-Pacific1543 msChecks passing
their status pagetheir claim, not our reading

Bitwarden publishes no status feed we can read, so the only reading here is our check reading on the left.

Bitwarden response time, by region

US-East
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 923ms2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 636ms2026-11-03 UTC: p95 910ms2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5

Check your own site while you wait on Bitwarden

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Bitwarden. It cannot diagnose Bitwarden's own systems.

What we measured, function by function

Bitwarden answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region

Email me when Bitwarden reports an incident on its status page, and again when it reports it resolved.

Get an email when Bitwarden reports an incident

Email me when Bitwarden reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Bitwarden's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 565msstatus code: 200checked: Nov 5, 2026, 2:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Bitwarden normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 6199msstatus code: 200checked: Nov 5, 2026, 2:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Bitwarden normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionBitwarden is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionBitwarden is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionBitwarden is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 819msstatus code: 200checked: Nov 5, 2026, 2:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Bitwarden normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionBitwarden is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1543msstatus code: 200checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Bitwarden normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionBitwarden is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionBitwarden is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Bitwarden, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Bitwarden yet, which is not evidence that nothing is wrong.

Recent probe events

Maintenance Window: US Identity Service (US Cloud Services) and 5 others, 29h 59mdeclared on their status page2026-10-26
Maintenance Window: US Identity Service (US Cloud Services) and 5 others, 29h 59mdeclared on their status page2026-10-12

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Bitwarden since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Bitwarden covering any window you pick, with our check readings and Bitwarden's own claim at the time, side by side.

Full check history for Bitwarden: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Bitwarden uptime by RealUptime's checksLive, from this page's own readings.
[![Bitwarden uptime by RealUptime's checks](https://realuptime.io/outages/bitwarden/badge.svg?days=30)](https://realuptime.io/outages/bitwarden)
<a href="https://realuptime.io/outages/bitwarden"><img src="https://realuptime.io/outages/bitwarden/badge.svg?days=30" alt="Bitwarden uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Bitwarden down?", https://realuptime.io/outages/bitwarden. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.bitwarden.com/alive
secondary
https://bitwarden.com/

What our check can and cannot see

A pass means the service's own health route reported that it is up. It does not show that pages, sign-in or the features people use work; a health route can stay green while they fail.

Host checked: api.bitwarden.com

RealUptime is not affiliated with Bitwarden; the name identifies what we checked, and nothing here speaks for Bitwarden's own team. We send a single web request to Bitwarden from 4 regions on our own schedule and time the response. We do not see inside Bitwarden's systems, do not use an account or real transaction, and are not the same signal Bitwarden's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Bitwarden is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Bitwarden operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 2498 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.