Is 1Password Down Right Now? Check if there is a current outage ongoing.

We have identified an issue where account administrators are unable to load the "People" view when logging in to their account on 1Password.com, 1Password.ca, and 1Password.eu. Our engineers are actively working to deploy a fix for this issue.

While the third-party provider works to recover from the issues, users may experience the below scenarios. We will continue to relay updates on progress as they are made available. -Business account holders will not be able to link or unlink family accounts. -Users loading the "Manage Account" page in the web application will see an error message "There was an unexpected error loading your linked accounts. Contact us for assistance". -Some SCIM bridge connections to the Google Workspace identity provider could be impacted (this is limited to the Google Workspace IdP).

Kolide is experiencing some issues. Please refer to https://www.kolidestatus.com/ for more information and updates.

This incident has been resolved.

We are investigating degraded performance affecting loading on 1Password.ca. Requests are taking a long time to respond or timing out. Our team has deployed a fix and we are monitoring the results.

We are investigating degraded performance affecting loading on 1Password.ca. Requests are taking a long time to respond or timing out. Our team has deployed a fix and we are monitoring the results.

Performance has returned to normal levels following our mitigation.

We have identified and addressed an issue causing latency affecting sign-ins. Our team has resolved the issue and is monitoring.

We have identified and addressed an issue causing latency affecting sign-ins. Our team has resolved the issue and is monitoring.

A fix has been deployed, we've monitored the results and this incident is now resolved.

We have identified an issue that is causing account linking failures for users. Our engineers are engaged and working towards deploying a fix for this issue.

We have identified an issue that is causing account linking failures for users. Our engineers are engaged and working towards deploying a fix for this issue.

**Date of Incident:** 2025-05-21 **Time of Incident \(UTC\)** 16:06:40 - 16:48:10 **Service\(s\) Affected:** USA/Global [1Password.com](http://1password.com/) website, Sign in, Sign up, Admin console, SSO \(Single Sign On\), Command Line Interface \(CLI\)\). **Impact Duration:** 41 minutes ## Summary On May 21st, 1Password's web interface, APIs, browser extension, and CLI tools experienced significant latency and errors. These problems stemmed from a code change that triggered a spike in server requests, leading to increased memory usage and system load. As a result, customers were unable to access their vaults or sign in via SSO. This was not a result of a security incident and customer data was not affected. ## Impact on Customers During the duration of the incident: * **Web interface, Administration:** Customers experienced significant delays when accessing the 1Password web interface. Administrators could not access or use any administration tools. * **Single Sign-on \(SSO\), Multi-factor Authentication \(MFA\):** Users with SSO or MFA enabled could not sign in and received an "An unexpected error occurred" message. Customers may also have been required to re-authenticate to access 1Password once the issue was mitigated. * **Command Line Interface \(CLI\):** CLI users faced increased latency and timeouts when attempting to access our web APIs. * **Browser Extension:** Users requiring web interface authentication were unable to unlock their vaults. * **Number of Affected Users \(approximate\):** All users accessing the service in the US/Global \([1password.com](http://1password.com)\) region were affected * **Geographic Regions Affected \(if applicable\):** [1password.com](http://1password.com) \(US/Global\) ## What Happened? We deployed code changes that increased the number of queries to our Redis clusters. The increase in queries caused a spike in memory usage which in turn caused latency and errors across all endpoints. * **Timeline of Events \(UTC\):** * 2025-05-21 15:52 UTC: Deployment started * 2025-05-21 15:57 UTC: Deployment complete * 2025-05-21 16:00 UTC: Automated monitoring detects increased errors and latency * 2025-05-21 16:01 UTC: Automation pages the incident response team * 2025-05-21 16:06 UTC: The team activates our incident protocol and begins investigation * 2025-05-21 16:21 UTC: The team initiates a rollback to a previous version * 2025-05-21 16:23 Code change causing the issue identified * 2025-05-21 16:48 UTC: Incident mitigated—rollback completed and we see a significant improvement in error rates and latency. The team continues to monitor the system. * 2025-05-21 17:23:11 UTC: Incident resolved * **Root Cause Analysis:** We released a code change that caused a significant increase in data writes to our session store cluster. All operations, even those with a pre-established session depend on the session store for authenticating requests. The resulting resource contention led to increased latency and timeouts. The unplanned high volume of writes to this specific datastore also caused a portion sessions to be prematurely evicted, requiring customers to re-authenticate earlier than anticipated. ## How Was It Resolved? Our monitoring systems detected the issue and alerted the response team immediately after the release. The team quickly identified the problem and initiated a rollback. * **Resolution Steps:** The team identified the problematic code change and reverted to a previous version. As the rollback deployed, server functionality returned to normal. * **Verification of Resolution:** Our monitoring systems were closely observed for 2 hours after the rollback to ensure latency and errors were fully resolved. ## What We Are Doing to Prevent Future Incidents * Our team will implement longer testing periods in lower-traffic environments to improve monitoring and issue detection for similarly high-risk changes. * Our team is working to improve our deployment process to enhance our incremental deployments, which will allow us to detect system issues earlier and contain fallout. ## Next Steps and Communication * Some customers may need to re-authenticate in order to access 1Password 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

This incident has been resolved. We will publish a postmortem here as soon as one is available.

The changes have been rolled out, and systems are recovering. Latency and error rates have returned to normal levels. Engineers are continuing to monitor. Users may be required to reauthenticate.

Our engineering team continues to work on mitigating this incident. Please note that users may experience latency, timeouts or error messages when logging in to 1Password, loading vaults, using the CLI and APIs.

Our engineers have identified the issue and are deploying a change to mitigate it.

Our engineers have identified the issue and are deploying a change to mitigate it.

1Password services for the US/Global region are failing to respond to requests. Our teams are investigating the issue.

This incident has been resolved. We will publish a postmortem here as soon as one is available.

The changes have been rolled out, and systems are recovering. Latency and error rates have returned to normal levels. Engineers are continuing to monitor. Users may be required to reauthenticate.

Our engineering team continues to work on mitigating this incident. Please note that users may experience latency, timeouts or error messages when logging in to 1Password, loading vaults, using the CLI and APIs.

Our engineers have identified the issue and are deploying a change to mitigate it.

Our engineers have identified the issue and are deploying a change to mitigate it.

1Password services for the US/Global region are failing to respond to requests. Our teams are investigating the issue.

1Password services for the US/Global region are failing to respond to requests. Our teams are investigating the issue.

[Rescheduled – Updated Maintenance Window]Scheduled maintenance has been rescheduled. The new maintenance window is from May 12, 2025 between 4PM - 8PM ET. We apologize for any inconvenience and appreciate your understanding.

Please note that our previously scheduled maintenance for today has been rescheduled to May 12, 2025 between 4PM - 8PM ET. During the maintenance window, you may see increased latency and elevated error rates for Events API and 1Password reporting.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

**Date of Incident:** 2025-04-22 **Time of Incident \(EST\):** 8:51am - 9:31am **Service\(s\) Affected:** SSO, Web Sign In, Sign Up, Web Interface, CLI **Impact Duration:** 40 minutes ## Summary On April 22, 2025 1Password’s web interface and APIs were unavailable for all customers accessing the US region. This was not a result of a security incident and customer data was not affected. The database stopped committing changes to disk, causing queries to fail. As a result, requests to the web interface and to APIs in the region returned with an error. ## Impact on Customers During the duration of the incident: * **Web interface, Administration:** Customers were unable to log in to the web interface for 1Password. Users already logged in could not use the web application. Administrators were unable to use the administration tools. Users were presented with the error “upstream connect error or disconnect/reset before headers. reset reason: overflow.” * **Single Sign-on \(SSO\), Multi-factor Authentication \(MFA\):** Users on accounts with SSO or MFA enabled were unable to sign in and were presented with the error above, or “An unexpected error occurred.” * **Command Line Interface \(CLI\):** CLI users received the above errors when accessing our web APIs. * **Browser Extension:** Users who needed to authenticate via the web interface were unable to unlock their vaults. ## Scope * All users accessing services in the US/Global \(non-Canada and non-EU\) region were affected. ## What Happened? A problem with database infrastructure prevented services from reading or writing data. There were no recent changes to the infrastructure, but additional load from multiple operations contributed to the issue. * **Timeline of Events:** * **2025-04-22 08:51 AM ET**: Database performance began to degrade. * **2025-04-22 08:54 AM ET**: Automation detected the issue, and circuit broke requests to the database. The web app began returning errors. The system raised alerts. * **2025-04-22 08:58 AM ET**: Incident team began investigating. * **2025-04-22 09:18 AM ET**: Issue was identified. * **2025-04-22 09:25 AM ET**: Database connections were reset to enable recovery. * **2025-04-22 09:31 AM ET**: Monitors confirmed service was restored and database was operating normally. * **Root Cause Analysis:** The database stopped writing data to its underlying data store. We are continuing to investigate the cause of this fault. * **Update 2025-05-08**: Our investigation concluded that a long-running query combined with a routine database migration blocked reads and writes to a table required for all subsequent queries. During the migration, an internal lock occurred that was not visible to our monitoring systems. This lock prevented database operations from proceeding until the initial long-running query was interrupted. * **Contributing Factors:** * The incident happened during the peak of daily traffic. * Two subsystems were running database operations during or just before the incident. ## How Was It Resolved? * **Mitigation Steps:** We halted non-critical processes to reduce load on the database. * **Resolution Steps:** All database connections were routed to a healthy replica. This restored service. * **Verification of Resolution:** Monitoring systems were closely observed for 1 hour to ensure error rates returned to normal. ## What We Are Doing to Prevent Future Incidents * **Improving monitors:** We are updating our monitoring systems to better detect database issues like this before they can impact customers. * **Improve database performance:** We are tuning queries and refactoring services to improve performance and reduce load on the database. * **Review database configuration:** We are reviewing database size and configuration to optimize performance and enhance monitoring capabilities. * **Updates 2025-05-08** * We tuned the database table involved to reduce the duration of the problematic query. * We updated the application running the query use a read replica instead of the primary database. * We modified the application to run the query during off-peak hours. ## Next Steps * No action is needed from customers 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

This incident has been resolved. Our engineering team identified the cause of the incident, and made changes to prevent recurrence. We will share more information as soon as it is available.

We are continuing to monitor for any further issues.

We have recovered from a service disruption affecting our the 1Password web interface. Our engineering team has restored all services, with some slowness due to inbound traffic spikes as clients reconnect. The engineering team continues to investigate to determine the root cause.

We are continuing to investigate a service disruption affecting our the 1Password web interface. Our engineering team has restored some services, but some APIs are still returning errors. The engineering team is actively closing in on a root cause.

We are currently investigating a service disruption affecting our the 1Password web interface. Our engineering team is actively working to identify and resolve the issue.

The 1Password extension is once again available on the Microsoft Edge Add-on store.

We have temporarily unpublished 1Password extension from the Microsoft Edge Add-ons store to address a bug. Current users are unaffected, and our team is actively working on deploying a new version to the Edge store. This was a proactive measure to ensure the best user experience. The extension will be republished as soon as the corrected version is ready and approved. In the meantime, the Edge extension is available via the Chrome Web Store. We appreciate your patience and will post an update once it's available again.

We have temporarily unpublished 1Password extension from the Microsoft Edge Add-ons store to address a bug. Current users are unaffected, and our team is actively working on deploying a new version to the Edge store.This was a proactive measure to ensure the best user experience. The extension will be republished as soon as the corrected version is ready and approved. In the meantime, the Edge extension is available via the Chrome Web Store. We appreciate your patience and will post an update once it's available again.

We are currently investigating this issue.

We are continuing to monitor for any further issues.

We have recovered from a service disruption affecting our the 1Password web interface. Our engineering team has restored all services, with some slowness due to inbound traffic spikes as clients reconnect. The engineering team continues to investigate to determine the root cause.

We are continuing to investigate a service disruption affecting our the 1Password web interface. Our engineering team has restored some services, but some APIs are still returning errors. The engineering team is actively closing in on a root cause.

We are currently investigating a service disruption affecting our the 1Password web interface. Our engineering team is actively working to identify and resolve the issue.

We are currently investigating a service disruption affecting our the 1Password web interface. Our engineering team is actively working to identify and resolve the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We identified an issue affecting SSO for new devices in the 1Password app and browser extension. Users might not be able to sign in on a new device. Our team is working to resolve this as quickly as possible.

We identified an issue affecting SSO for new devices in the 1Password app and browser extension. Users might not be able to sign in on a new device. Our team is working to resolve this as quickly as possible.

For Trelica customers only: Scheduled maintenance this weekend may involve a short period of downtime on Saturday 5th April between 10AM EST (3PM UK) and 3PM EST (8PM UK) for the Trelica service.Watch https://status.trelica.com for status updates. Get help with Trelica at https://help.trelica.com/hc/en-us.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

This incident has been resolved.

After our configuration updates yesterday, the failure rate for this issue has returned to a normal level. We will continue to monitor the situation today.

We have identified an issue resolving DNS for some duosecurity.com subdomains. We have made some configuration changes to improve the issue and have seen error rates falling. We have made additional changes to our monitoring to provide more information and will continue to monitor this issue. This issue is intermittent and the authentication requests do eventually succeed upon retry.

We are actively investigating an issue that is causing authentication failures for some Duo SSO users. This issue is intermittent and the authentication requests do eventually succeed. Our engineers are engaged and working as quickly as possible to identify the issue towards resolution.

This incident has been resolved.

After our configuration updates yesterday, the failure rate for this issue has returned to a normal level. We will continue to monitor the situation today.

We have identified an issue resolving DNS for some duosecurity.com subdomains. We have made some configuration changes to improve the issue and have seen error rates falling. We have made additional changes to our monitoring to provide more information and will continue to monitor this issue. This issue is intermittent and the authentication requests do eventually succeed upon retry.

We are actively investigating an issue that is causing authentication failures for some Duo SSO users. This issue is intermittent and the authentication requests do eventually succeed. Our engineers are engaged and working as quickly as possible to identify the issue towards resolution.

This incident has been resolved.

We've deployed a fix and will continue to monitor it.

We are continuing work on a mitigation plan.

We have identified the issue and we are working on a mitigation plan.

We are investigating intermittent issues affecting sign-ins and loading sections in the 1Password app and browser extension. Users may see errors such as "Can't sign in. The request took too long." or "We're having trouble loading this section." Our team is working to resolve this as quickly as possible.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating intermittent issues affecting sign-ins and loading sections in the web application. Users may see errors such as "Can’t sign in. The request took too long." or "We're having trouble loading this section." Our team is working to resolve this as quickly as possible.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue and will update within 30 minutes.

1Password is experiencing a partial outage affecting authentication and syncing. We are investigating the issue and will report back as soon as we have more information.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results

We've identified an issue with our Billing Service. This is affecting: - Partnerships API - Apple Subscription events - Google Subscription events The cause of this incident has been identified and is under remediation

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified an issue impacting the browser extension (for users on the nightly channel) and accessing vaults on the web. A fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Business accounts will find the Activity Log via the Admin Console unavailable—403 (feature_disabled) error. Our engineering teams have identified the cause of this issue and are working on remediation.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are investigating an issue affecting our billing system and impacting our ability to process subscription events from Apple and Google.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

An issue is preventing us from sending account confirmation emails to SCIM-provisioned users after they accept their invitation. Users are still confirmed automatically by the 1Password SCIM Bridge and you can continue to provision users normally. You may want to proactively distribute communications to your teams letting them know they may not receive a confirmation email. They should be able to sign into their new 1Password account approximately five minutes after accepting their invitation. Members of the Owners or Administrators group in 1Password can check the status of provisioned users on the People page of your 1Password account. We are still investigating the cause and will provide an update when we have more information.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

There is an issue when upgrading from nightly versions 8.10.46-14 through 8.10.46-20 to 8.10.46-21 and higher, leaving the application unable to open and resulting in a "the database is newer version" error. To resolve, make sure you can access all your 1Password data on another device or on 1Password.com before you follow the steps under "To remove your 1Password data": Mac: https://support.1password.com/uninstall-1password/#to-remove-your-1password-data-mac Windows: https://support.1password.com/uninstall-1password/#to-remove-your-1password-data-windows Please reach out to support@1Password.com if you do not have another trusted device where you are signed in.

This incident has been resolved.

This incident has been resolved.

Issue remains partially mitigated. Data for the past 3 months is available. Older data is intact, but unavailable at the moment. We are working with support partners to resolve the issue and make all data available once more. We apologize for the inconvenience.

Issue remains partially mitigated. Data for the past 3 months is available. Older data is intact, but unavailable at the moment. We are working to resolve the issue and make all data available once more. Thank you for your patience. We will update again in 1 hour.

We are continuing to monitor for any further issues.

Issue remains partially mitigated. Data for the past 3 months is available. Older data is intact, but unavailable at the moment. We are working to resolve the issue and make all data available once more. Thank you for your patience. We will update again in 1 hour.

We have partially mitigated the issue. The Events API and admin console reporting are now operational, but please note that only three months of data is currently accessible. We are actively working to resolve the remaining issues and make older data accessible again. Thank you for your patience.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are currently experiencing issues with email delivery due to an outage with one of our upstream vendors. This is affecting the sending of emails by our Technical Support teams. Our team is actively monitoring the situation and working closely with the vendor to resolve the issue as quickly as possible. Add "CRITICAL" to support requests if applicable and one of our managers will contact you directly.

This incident has been resolved.

At approximately 8:28AM EDT, Microsoft reported an Azure issue that impacted Azure SSO login capabilities. We started to see resolution around 9:32AM EDT. We are continuing to actively monitor.

We have released version 8.10.44 which includes a fix to address SLS not working in Safari. This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

From approximately 8:58 PM CET until 9:19 PM CET 1Password's European region experienced elevated error rates, affecting users ability to sign in with SSO, sync across devices, or use other functionality on the 1Password.eu website.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue which is causing degraded performance for users trying to login using SSO and the 1Password web interface and app. Users may experience slowness or intermittent failures when trying to login. We will provide more information as it becomes available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

The issue has been identified and a fix is being implemented.

Our teams are currently investigating an issue causing authentications to fail.

This incident has been resolved.

The team has identified a fix for this issue.

The incident affects the admin console functionality for customers in various regions, including the USA, Canada, Europe, and Enterprise customers. The issue is causing a partial outage of the admin console, impacting users' ability to access key administrative features and functionalities, such as managing groups, users, and activity logs. The team has identified several customers who have reported encountering this issue, which appears to be affecting a subset of users.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating an issue where 1Password browser extensions are not able to fill on insecure http sites.

The incident response team have determined that the issue is now resolved.

The incident response team have mitigated the issue by deploying a fix and are continuing to monitor.

The issue has been identified and a fix is being worked on.

We are continuing to investigate intermittent login issues when logging in to the 1Password app or web interface. We will provide further updates as more information becomes available.

We are currently investigating this issue.

This incident has been resolved.

We’ve identified an incorrect configuration in the certificate that supports our website. At this time, the url https://www.1password.com will show a certificate error. https://1password.com continues to work as normal. We are working to resolve the configuration issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

Our engineers have rolled out some changes to mitigate the ongoing issue and sign-ons to 1Password.com. We will continue to monitor the situation and provide updates as necessary.

We are continuing to investigate this issue.

We are currently investigating reports of users having issues with trying to login and access the 1Password application. This is currently impacting sign-ins to the 1Password web interface. We will provide more information as it becomes available.

We have confirmed the new release (version 8.10.23) has fixed the issue.

We have released the fix in version 8.10.23, available in the App Store and for download.

We have put together a fix for the issues and are working on releasing an update to our Desktop and iOS Apps.

We have identified the issue and are testing a fix.

We are investigating cases where 1Password may sign users out of the SSO-enabled account entirely if it is locked while the user is prompted to sign back in. Our team is actively investigating and updates will follow accordingly.

This incident has been resolved.

Our iOS and iPad apps should now be updated in the App Store and available for download. We will continue to monitor for new reports.

We have verified our fixes and have submitted them to Apple for review. We have requested an expedited review from Apple. The release will go out as soon as Apple has reviewed it

We have put together a fix for the SSO/MFA issues and are working on releasing an update to our iOS and iPad apps

The issue has been identified and a fix is being implemented.

We have confirmed fixes for several issues with our development team and are proceeding to test with our QA team.

While investigating the issue we discovered certain scenarios that would occur when sending 1Password to the background, causing the sign-in and unlock process to be aborted. We are internally testing fixes to those scenarios at this time. We will provide another update within the next 60 minutes.

We continue to investigate this issue with our technical staff. We will provide another update within the next 60 minutes.

We believe we have identified the source of the ongoing MFA login issues and our engineers are working on testing and implementing a fix. We will provide another update within the next 60 minutes.

We continue to investigate and narrow down the issues some users are experiencing with MFA logins We will continue to provide updates as more information becomes available.

We are continuing to investigate the issue and will update accordingly.

We think we have identified the issue and are testing a fix.

We are aware of an issue with MFA logins impacting the ability to log into 1Password on iOS for some users. Our engineers are actively investigating and updates will follow accordingly.

This incident is resolved.

A fix has been implemented and we are monitoring the results.

The Billing service has returned to a degraded state, currently impacting all billing events. Engineers are working to restore full service. We are prioritizing restoring full billing capabilities to customers subscribed via Apple and directly in the web application via credit card and then will follow up with Google Play Store subscribers.

The issue blocking the processing of events was resolved. We are working through the backlog of billing events. We will continue to monitor and provide further updates.

We have identified the issue and we are working on deploying a fix.

We are currently experiencing a delay in processing all billing events, including adding payment methods, processing invoices and renewals. Our engineers are actively investigating and updates will follow accordingly.

We have resolved the issue which was causing users to experience intermittent errors.

We are currently investigating reports of intermittent errors with multiple 1Password websites. The issue is currently impacting users who access 1password.com, 1password.ca , 1password.eu and my.1password.com

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue where in-app links and redirects may not be resolving properly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Deployment is in process for affected environments.

A fix for the issue has been implemented and is presently being deployed.

Users can work around the issue by clearing the browser cache or using a browser they have not used before to continue recovery.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

Service has been fully restored and all pending billing events have been proceed. This incident is now resolved.

A fix has been implemented and we are monitoring the results.

The Engineering team has a resolution prepared and will begin the rollout to production shortly

The Engineering team is continuing to work on the resolution and a fix is underway.

The Engineering team has identified what we believe to be the source of the issue and are working on a remediation.

The issue has been identified and a fix is being implemented.

The automated workers that process billing and payment-related events are experiencing significantly degraded service, temporarily delaying all billing-related actions for customers. Investigation into the cause and remediation are underway.

We are currently investigating this issue.

This incident has been resolved.

A fix has been deployed for this issue. You should now be able to unlock the browser extension. If your extension already appears to be unlocked but you don't see any of your items, please lock the extension and then unlock it again.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved. We apologize for any inconvenience caused.

All 1Password functionality has been restored. Our team continues to monitor for additional service interruptions. We apologize for any inconvenience this may have caused.

We are aware that subset of customers is experiencing issues logging into our 1Password.com service and our team is investigating.

There are no longer any delays in processing any billing flows. We apologize for any inconvenience caused.

We're seeing recovery in processing of billing actions. Our team continue monitoring the overall behavior.

A subset of 1password.com, 1password.ca, 1password.eu customers could be experiencing delays in having their billing actions processed. Our engineers are actively investigating this behavior. Updates will follow accordingly.

This incident has been resolved. We apologise for any inconvenience caused.

We are continuing to monitor this issue. A very small subset of customers may still be experiencing errors - signing out of their applications will resolve these errors.

We are continuing to monitor this issue. A very small subset of customers may still be experiencing errors - signing out of their applications will resolve these errors.

We are continuing to monitor this issue. A very small subset of customers may still be experiencing errors - signing out of their applications will resolve these errors.

A workaround has been put in place for this issue and we are continuing to monitor for new errors. A very small subset of customers may still be experiencing errors - signing out of their applications will resolve these errors.

We are aware that a subset of customers may be experiencing errors while using the 1Password applications in our Canadian and European regions. The issue has been identified and a fix is currently in progress. Signing out of the application may help to mitigate any issues.

No service impact observed during the monitoring period. We apologize for any inconvenience caused.

Issue has been identified and corrected. Support engineers are currently monitoring the service availability.

Customers are unable to access the my.1password.ca website. The other existing websites(.com, .eu) and tenants remain unaffected.

This incident has been resolved. We apologize for any inconvenience caused.

We have detected reduced reliability in the ENT 1Password services and our team is investigating.

Incident has been resolved. There are no longer any delays in processing any billing flows.

We're seeing recovery in processing of billing actions. Our team continue monitoring the overall behavior.

The issue has been identified and a fix is currently being tested.

The issue has been identified and a fix is currently being tested.

The issue has been identified and a fix is currently being tested.

We're seeing recovery in processing of billing actions. Our team continue monitoring the overall behavior.

We're seeing recovery in processing of billing actions. Our team continue monitoring the overall behavior.

The issue has been identified and a fix is currently being tested. Updates will follow accordingly.

The issue has been identified and a fix is currently being tested. Updates will follow accordingly.

A subset of 1password.com customers could be experiencing delays in having their billing actions processed . All other customers remain unaffected. Our engineers are actively investigating this behavior. Updates will follow accordingly.

This incident has been resolved. We apologize for any inconvenience caused.

A fix has been implemented and we are monitoring the results.

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

The issue has been identified and a fix is currently in progress.

We are continuing to investigate this issue.

We have detected an issue impacting our beta customers for Service Accounts. We are investigating and will post another update as soon as we learn more.

This incident has been resolved. We apologize for any inconvenience caused.

A fix has been implemented and we are monitoring the results.

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

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

The issue has been identified and a fix is in progress.

Some customers may be experiencing issues when signing into our web application at https://start.1password.com if MFA is enabled for their account. Our team is investigating and will update this page with more information when available. Customers can continue to sign in through the mobile and desktop applications.

The team is investigating an incident affecting sign in. We'll follow-up with more information as it becomes available.

This incident has been resolved. Customers will no longer experience any delays in billing processing.

We're seeing recovery in processing of billing actions. Our team continues monitoring overall behavior.

A fix has been implemented and we are monitoring the results.

A subset of 1password.com customers could be experiencing delays in having their billing actions processed. All other customers remain unaffected. Our engineers are actively investigating this behavior. Updates will follow accordingly.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor the availability of 1password.eu services.

We are continuing to investigate this issue.

We have detected reduced reliability in 1password.eu services and our team is investigating.

This incident has been resolved.

We are continuing to monitor the recovery of the 1password.com marketing site. All capabilities, including search, contact, and chat, have recovered.

We are continuing to monitor the recovery of the 1password.com marketing site. Search, contact, and chat capabilities appear to be stabilizing.

We are monitoring recovery on the 1password.com marketing site. Some components such as search and contact forms have not yet recovered.

We have been notified of an issue at our cloud provider affecting multiple services that is impacting 1password.com availability.

We have detected reduced availability affecting 1password.com and are currently investigating.