outages.live
Live
1PasswordIncident · 2026-09-09 20:43 UTC

Device Trust Service Disruption

ResolvedOfficial update

This incident has been resolved.

The latest update from 1Password.

State

Resolved

Started

53 d ago

2026-09-09 20:43 UTC

Lasted

27 min

until 2026-09-09 21:11 UTC

Worst impact

Partial outage

Timeline

3 updates
20:4320:5020:5721:0421:11
Partial outageUpdate postedTimes in UTC

Investigating

10 min 36%

Monitoring

17 min 64%

Updates

Times in UTC

As posted by 1Password

Resolved2026-09-09 21:11 UTC

This incident has been resolved.

Monitoring2026-09-09 20:53 UTC

We have identified the triggering change and have rolled it back. We are monitoring to confirm that this has completely resolved the issue.

Investigating2026-09-09 20:43 UTC

We are currently investigating reports of an incident affecting Device Trust. Some customers may experience delays in device posture checks or authentication failures. We will provide an update as soon as we have more information.

Affected components

2
Device Trust Authentication ServiceUSA/Global - Device Trust Authentication Service

1Password in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

6

Median duration

27 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 days
median 27 min
90 days agoToday

Other 1Password incidents

All incidents

1Password·High error rate on 1Password.com

# 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 Duration:** 1hr10m ## Summary **What happened:** On Friday, October 16, 2026, from 4:00 to 5:10 p.m. Pacific \(23:00–00:10 UTC\), some requests to 1Password web services failed. Earlier that day, we deployed an infrastructure change meant to improve efficiency. The change caused one of our backend systems to hold on to resources longer than expected, and the system eventually ran out of capacity. **Impact:** About 2% of requests to 1Password web services in the US failed during the 70-minute window. The issue happened during a period of low traffic, which limited the number of people affected. **Resolution:** We increased the affected system’s capacity and applied configuration changes so resources are recycled more qui

Resolvedresolved 12 d ago

1Password·Some users are unable to view vault profiles using the web interface

A fix has been deployed and this issue is now resolved.

Resolvedresolved 16 d ago

Follow 1Password

Your coding agent knows when 1Password is down, and tells you when a failure is theirs, not yours. You can also get 1Password incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "onepassword" and tell me if 1Password has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=onepassword
Slack
/feed subscribe https://outages.cc/feed.xml?providers=onepassword

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane