Activity Log fails to load or return errors for some users

What to do

• Check whether you use 1Password Events API and Reporting. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 19h 39m it lasted.

  Anything that failed between 2025-07-22 23:21 UTC and 2025-07-23 19:00 UTC may need a replay.

• Subscribe to 1Password's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=1password works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from 1Password 4

1. identifiedJul 22, 2025, 11:21 PM UTC

   There is an issue affecting the Activity Log, which may fail to load or return errors for some users. Our team is actively working to restore full functionality as soon as possible.

   provider

2. identifiedJul 22, 2025, 11:22 PM UTC

   We are continuing to work on a fix for this issue.

   provider

3. resolvedJul 23, 2025, 7:00 PM UTC

   This incident has been resolved.

   provider

4. postmortemJul 25, 2025, 4:04 PM UTC

   **Date of Incident:** 2025-07-22 **Time of Incident \(UTC\):** 10:40 - 06:30 **Services Affected: Admin Console Activity log and User Details page** **Impact Duration:** 43 hrs ## Summary A change to our internal data model that removed an unused type definition led to multiple failures in the Reports system. ## Impact on Customers * **Events API and Reporting:** The activity log widget failed to display activities. * Admin console: User details page failed to display user details ## What Happened? A software update introduced an API change that caused a mismatch between client and server. The Audit log page in the admin console was still collecting data but was not able to render it. * **Timeline of Events \(UTC\):** * 10:40 : Detected by 1Password personnel and root cause identified * 10:42: Issue Identified * 13:38 Fix created and testing initiated * 06:30: Fix released, Service fully restored * **Root Cause Analysis:** A User State was removed from the [1Password.com](http://1Password.com) server but not the client. This was a breaking API change. ## How Was It Resolved? * **Resolution Steps:** The user state in the 1Password client was removed to get the server and client back into parity. * **Verification of Resolution:** 1Password engineering tested the changes and validated that full system functionality was restored. ## What We Are Doing to Prevent Future Incidents * **User State change process: 1Password is investigating how to catch breaking API changes by implementing additional end-to-end tests in the CI pipeline.** * Audit log architecture change: Engineering is investigating a rework of the audit log page to change how it aggregates data so that it is not reliant on an endpoint. This would mitigate future occurrences that caused this issue. ## Next Steps and Communication * No action is required from our customers at this time. * If you are still experiencing issues, please contact our support team at [support@1password.com](mailto:support@1password.com). We are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding. Sincerely, The 1Password Team

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.