Live

Degraded Device Trust Authentication Experience

0

1Password had a degraded Device Trust Authentication Service. The incident affected the USA/Global and Europe regions. 1Password reports that the incident is resolved, and it lasted 56 minutes.

State

Resolved

Started

Lasted

56 min

Worst impact

Partial outage

Timeline

3 updates
17:2517:3917:5318:0718:21
Partial outageUpdate postedTimes in UTC

Investigating

35 min 62%

Monitoring

22 min 38%

Updates

Times in UTC

As posted by 1Password

Resolved

This incident has been resolved.

Monitoring

We are seeing signs of recovery and are monitoring service levels.

Investigating

We are seeing an increase in errors and latency for some authentication requests. Our engineering team is actively investigating.

Affected components

3
Device Trust Authentication ServiceUSA/Global - Device Trust Authentication ServiceEurope - Device Trust Authentication Service

1Password in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

7

Median duration

42 min

This incident

1.3× the median

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

4 days
median 42 min
90 days agoToday

Other 1Password incidents

All incidents

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.live/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.live/feed.xml?providers=onepassword
Slack
/feed subscribe https://outages.live/feed.xml?providers=onepassword

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane