1Password incident: Elevated API Errors

1. postmortemSep 10, 2025, 21:59 UTC

   # Performance Degradation **Date of Incident:** 2025-09-03 **Time of Incident \(UTC\):** 11:06 - 12:07 **Service\(s\) Affected:** All APIs **Impact Duration:** 61 minutes ## Summary For 61 minutes on the morning of September 3rd, 2025, all 1Password APIs in the US/Global environment had degraded performance or returned an error for approximately 20% of requests. 92% of the impact was mitigated within 13 minutes at 11:19 by automation scaling up infrastructure. By 12:06 a manual restart of the remaining infrastructure completed mitigation. A permanent fix was implemented and deployed to prevent the issue from reoccurring. ## Impact on Customers * **APIs:** High latency, or a 500 Internal Server Error. * **Number of Affected Customers:** 20% of all requests returned errors for 13 minutes, 1% thereafter. * **Geographic Regions Affected \(if applicable\):** 1Password USA/Global ## What Happened? * **Timeline of Events \(UTC\):** * 11:05: A customer started a stream of an

2. resolvedSep 3, 2025, 11:00 UTC

   This incident has been resolved.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in 1Password's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Pinecone: [Serverless][AWS][us-east-1] 5xx errors on read operations for some indexesMajor · Sep 2, 2025, 22:46 UTC

How often does 1Password have incidents?

1Password reported 4 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 42 min. See 1Password's uptime and incident history