Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 2 Next »

July 28th, 2022 3:00pm Eastern - Root Cause Analysis: The current disruption has been fully mitigated for Clarity production environments on AWS. A root cause analysis has been posted below:

July 28th, 2022 2:39pm Eastern: All production environments are back online and healthy. A small number of non-production environments remain affected. A root cause analysis will be posted to this page.

July 28th, 2022 2:04pm Eastern: Rego continues to note that a small number of customer environments remain affected. Rego is awaiting confirmation from AWS of full recovery. Rego will post a confirmation to this page we can confirm that all affected services are restored.

July 28th, 2022 1:49pm Eastern: AWS has confirmed the network recovery remains in progress, with an estimate of 30-45 minutes for recovery of any services that remain affected. Rego will post a confirmation to this page we can confirm that all affected services are restored.

July 28th, 2022 1:30pm Eastern: AWS has confirmed a power failure resulted in network disruption. Power has been restored and networking services are coming back online. Rego will post a confirmation to this page when affected services are restored.

July 28th, 2022 1:24pm Eastern: Rego has determined that new user logins to certain environments are affected, but the issue appears intermittent and related to networking. Rego will post updates to this status page as they become available.

July 28th, 2022 1:18pm Eastern: Amazon Web Services has confirmed a networking issue that may be impacting infrastructure. Rego continues to investigate which customers and environments may be affected and will post updates to this status page as they become available.

July 28th, 2022 1:05pm 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.

  • No labels