We started checking 1Password on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when 1Password reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what 1Password's own status page declared. Below it, any public chatter we saw about 1Password and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what 1Password's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about 1Password in the last 24 hours, which is not evidence that nothing is wrong.
1Password's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is 1Password's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention 1Password next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
432
US-West
100.00%
343
Europe
100.00%
313
Asia-Pacific
100.00%
190
Their declared record
1Password's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
High error rate on 1Password.comPartial outage
Oct 16, 2026, 11:45 PM UTC to Oct 20, 2026, 7:48 PM UTC (3d 20h)postmortem published
their latest update (Oct 29, 2026, 7:35 PM UTC): # Incident Postmortem - High error rates on 1Password.com when syncing data and provisioning users.
**Date of Incident:** 16 October 2026
**Time of Incident \(UTC\):** 23:00 - 00:11 \(Oct 17\)
**Service\(s\) Affected:** Admin Console, Item Syncing, Provisioning
**Impact Du…
Some users are unable to view vault profiles using the web interfaceMinor incident
Oct 16, 2026, 5:31 PM UTC to Oct 16, 2026, 5:42 PM UTC (11 min)resolved
their latest update (Oct 16, 2026, 5:42 PM UTC): A fix has been deployed and this issue is now resolved.
Device Trust Service DisruptionPartial outage
Sep 9, 2026, 8:43 PM UTC to Sep 9, 2026, 9:11 PM UTC (27 min)resolved
their latest update (Sep 9, 2026, 9:11 PM UTC): This incident has been resolved.
Account governance functions are unavailable in SaaS ManagerPartial outage
Jul 22, 2026, 5:55 PM UTC to Jul 22, 2026, 7:20 PM UTC (1h 26m)resolved
their latest update (Jul 22, 2026, 7:20 PM UTC): A fix has been deployed and this issue is now resolved.
SaaS Manager Workflows are not running as expectedMinor incident
Jul 17, 2026, 6:52 PM UTC to Jul 17, 2026, 6:57 PM UTC (5 min)resolved
their latest update (Jul 17, 2026, 6:57 PM UTC): This incident has been resolved.
Degraded user-related operations for individual and family accountsMinor incident
Jul 13, 2026, 6:59 PM UTC to Jul 13, 2026, 7:57 PM UTC (58 min)resolved
their latest update (Jul 13, 2026, 7:57 PM UTC): A fix has been deployed and this issue is now resolved.
Password Manager Update Server OutageAll systems operational
Jul 13, 2026, 2:30 PM UTC to Jul 13, 2026, 2:30 PM UTC (0 min)resolved
their latest update (Jul 13, 2026, 2:30 PM UTC): A fix for this issue has been implemented, and our teams are monitoring. During the outage, GitHub Actions might have failed to pull the latest CLI version, causing the pipeline to fail.
Device Trust OutageMajor outage
Jul 2, 2026, 7:44 PM UTC to Jul 2, 2026, 8:30 PM UTC (47 min)postmortem published
their latest update (Jul 11, 2026, 1:05 AM UTC): # Incident Postmortem - Device Trust Authentication Outage
**Date of Incident:** 2026-07-02
**Time of Incident \(UTC\):** 19:28 - 20:28
**Service\(s\) Affected:** This incident affected: USA/Global \(Device Trust Authentication Service, Device Trust Checks Server, Device Tru…
Provisioned users with SSO enforcement encounter a 403 error when accepting their invitationMinor incident
Jun 29, 2026, 10:08 PM UTC to Jun 30, 2026, 2:09 PM UTC (16h 1m)resolved
their latest update (Jun 30, 2026, 2:09 PM UTC): This incident has been resolved.
Restoring Access with a Recovery Code Is Failing for Some UsersMinor incident
Jun 24, 2026, 5:15 PM UTC to Jun 24, 2026, 7:01 PM UTC (1h 47m)resolved
their latest update (Jun 24, 2026, 7:01 PM UTC): The issue is now resolved, and access to 1Password services should be fully restored.
Showing the 10 most recent of 50 incidents 1Password has declared in the history we hold.
These entries are 1Password's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
1Password's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.