Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 35 Next »

October 24th, 2022 1:16pm Eastern: Rego believes a full recovery has been achieved. We are working with Amazon Web Services to develop a root cause analysis. We will continue to diligently investigate and post updates to this page as they become available. A full root cause analysis will be posted to this page once available.

October 24th, 2022 1:01pm Eastern: Significant recovery of the Amazon Web Services login processing has occurred. We do not have confidence in a full recovery status, but we expect to post a full recovery notification shortly. We are continuing to investigate and will continue to post updates to this page.

October 24th, 2022 12:52pm Eastern: Rego is seeing signs of broad recovery, but continued instability for Clarity logins. We are continuing to investigate and will continue to post updates to this page. As we determine a timeline for full recovery, it will be posted to this page.

October 24th, 2022 12:32pm Eastern: Rego is seeing signs of broad recovery for Clarity logins. We are continuing to investigate and will continue to post updates to this page.

October 24th, 2022 12:22pm Eastern: Rego continues to investigate the issue with AWS unable to process logins for Clarity. As we determine a timeline for recovery, it will be posted to this page.

October 24th, 2022 11:55am Eastern: Rego has detected an unexpected issue in the AWS infrastructure processing logins to the Clarity application. This event is related an outage at Amazon Web Services. Rego is investigating which customers and environments may be affected and will post updates to this status page as they become available.

Archive of historical events

  • No labels