Loading status…
1Password status · Security & Identity · checked (1m ago)
No — 1Password is not down. All 1Password systems are reported operational.
According to 1Password's official status page, 1Password was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, 1Password's feed reported no outage in 100.00% of our checks.
Everything above is read from 1Password's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported 1Password in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
1Password stores credentials, passkeys and secrets for individuals and teams, syncing them between apps, browser extensions and, through Connect and the Service Accounts API, into infrastructure. The apps hold a local copy of the vault, which shapes what an outage actually costs you.
The status page separates the sync service from the web app and the developer-facing Connect and CLI paths. The distinction that matters most is not on the page at all: because the desktop and mobile apps cache an encrypted vault locally, a sync outage stops changes propagating but does not lock you out of passwords you already have.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where 1Password's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days 1Password was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of 1Password's status endpoint.
1Password has published 40 incidents in the last 12 months, the 20 most recent shown here. Only what 1Password posted itself — not every problem users hit.
resolved · Sep 9, 08:43 PM (10d ago)
resolved · Jul 22, 05:55 PM (59d ago)
resolved · Jul 17, 06:52 PM (64d ago)
resolved · Jul 13, 06:59 PM (68d ago)
resolved · Jul 13, 02:30 PM (68d ago)
postmortem · Jul 2, 07:44 PM (79d ago)
resolved · Jun 29, 10:08 PM (82d ago)
resolved · Jun 24, 05:15 PM (87d ago)
resolved · Jun 18, 05:54 PM (93d ago)
resolved · Jun 16, 04:24 PM (95d ago)
resolved · Jun 11, 09:49 PM (100d ago)
resolved · May 16, 03:51 PM (126d ago)
resolved · May 4, 05:59 PM (138d ago)
postmortem · Apr 27, 02:54 PM (145d ago)
resolved · Apr 22, 03:18 PM (150d ago)
postmortem · Apr 14, 05:25 PM (158d ago)
resolved · Apr 13, 05:24 PM (159d ago)
resolved · Apr 1, 02:13 PM (171d ago)
resolved · Mar 31, 09:28 PM (172d ago)
resolved · Mar 16, 05:11 PM (187d ago)
If you cannot unlock at all, that is local — a forgotten account password or a Secret Key the device no longer has, neither of which a status page can help with. Browser extension failures after an update are common and are fixed by restarting the browser, not by waiting. SSO-provisioned accounts fail at the identity provider, which is a different vendor's outage entirely.
