Service Disruption Ongoing - AssureID Connect, ExpectID

Per AWS, the issue has been resolved:

"[RESOLVED] Increased Error Rates and Latencies
Oct 20 3:53 PM PDT Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours. We will share a detailed AWS post-event summary."

AssureID Connect and ExpectID is available. AWS are reporting service recovery across all AWS services. GBG Service to be monitored for stability. We are continuing to monitor for any further issues.

AssureID Connect and ExpectID is available. AWS are reporting service recovery across all AWS services. GBG Service to be monitored for stability.

Our teams are actively monitoring the situation and closely tracking AWS service status updates as we await full restoration.

https://health.aws.amazon.com/health/status - Amazon Health Status Page on AWS Services

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

Unfortunately, AWS is still experiencing issues with multiple services in their east region (N. Virginia) which continue to impact our services.
We continue to treat this matter as our top priority and all technical teams are working to determine the cause and resolution. We apologise that this issue is taking longer to resolve than we would like.

Please use this AWS Status Page to check on the progress of this global outage.
https://health.aws.amazon.com/health/status