Is 1Password Down?

No — 1Password is up

Reachable from all 8 checked regions

Average response time: 249ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.1password.com

1Password uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

254ms

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

21-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.

ams

122ms

DNS 32ms TCP 1ms TLS 10ms TTFB 104ms

arn

349ms

DNS 45ms TCP 77ms TLS 10ms TTFB 241ms

bom

353ms

DNS 159ms TCP 3ms TLS 17ms TTFB 309ms

cdg

187ms

DNS 28ms TCP 1ms TLS 9ms TTFB 161ms

dfw

236ms

DNS 71ms TCP 2ms TLS 12ms TTFB 216ms

ewr

161ms

DNS 38ms TCP 2ms TLS 10ms TTFB 140ms

fra

180ms

DNS 22ms TCP 1ms TLS 18ms TTFB 158ms

gru

285ms

DNS 128ms TCP 3ms TLS 12ms TTFB 252ms

iad

243ms

DNS 82ms TCP 2ms TLS 7ms TTFB 222ms

What 1Password does

1Password stores passwords, passkeys and secrets for individuals and companies, syncing an encrypted vault between browser extensions, desktop and mobile apps. Teams also use it to share credentials and to feed secrets into infrastructure, so an outage can affect both a person signing in and a deployment pipeline reading a service account.

What an outage looks like

Sign-in to a new device fails, while apps already signed in keep filling passwords normally. Items saved on one device do not appear on another, because syncing is affected rather than storage. The admin console will not load, blocking access changes. Service accounts and 1Password Connect return errors, so automated systems reading secrets fail alongside people.

What to do about it

Check status.1password.com, which reports Sign in, Syncing, Access to passwords, the Admin console, Service Accounts and 1Password Connect separately, across USA, Canada and Europe sections. Your vault is cached locally on devices already signed in, so avoid signing out or removing the app during an incident: that is what turns a sync problem into being locked out.

Is it down for everyone, or just you?

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

1Password outage FAQ

Can I still get my passwords if 1Password is down?

Yes, on any device where the app is already set up and signed in. 1Password caches an encrypted copy of the vault locally, so autofill and manual lookup keep working without the service. What fails is syncing new items, adding a new device, and sharing. This is the strongest reason not to sign out during an incident.

Should I sign out and back in to fix a sync problem?

No, and during an outage this is the single most damaging thing you can do. Signing out clears the local cache, and signing back in requires the service that is currently unavailable, which leaves you genuinely locked out of your own vault. Wait for the status page to clear before touching account setup.

Is my vault at risk during a 1Password outage?

An availability incident does not affect the encryption or the stored data; it affects reaching the service. Items are encrypted with keys derived from your account password and secret key, neither of which is involved in an outage. The practical risk is being unable to add a device, not exposure of what is stored.

Why do my secrets fail in CI when 1Password looks fine?

Service Accounts and 1Password Connect are separate components from the consumer sign-in path, and they fail independently. A pipeline reading secrets can break while people continue using the browser extension without noticing anything. Check those components specifically rather than concluding from working autofill that 1Password is entirely healthy.

Does 1Password report status by region?

The status page separates USA and Global, Canada and Europe sections, and accounts are hosted in one of them. An incident in a region you do not use has no effect on you. If your team is spread across regions, colleagues can legitimately have different experiences of the same incident, which is worth confirming before escalating.

How we measure this

We request 1Password'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 1Password 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 1Password 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