ML Consumer/Opening - Socure Report Issues Related to AWS

Socure has provided the following update:

We’re pleased to share that all Socure services have now fully recovered and are operating normally. We are currently serving 100% of traffic without any issues, and all system latencies and performance metrics have returned to expected levels.

Our engineering and operations teams will continue to work closely with AWS to conduct a comprehensive root cause analysis (RCA) of the incident. We will share the RCA publicly within the next few days once this review is complete.

We appreciate your patience and understanding throughout this event and thank you for your continued trust in Socure.

Socure has provided the following update:

We continue to work closely with AWS as their service recovery progresses and are seeing significant improvements across all Socure services. Overall system availability and performance have continued to improve steadily throughout the day.

At this time, we have successfully restored 99% of all traffic, and latencies across our services continue to improve. Our systems are stable, and our teams are actively monitoring performance to ensure continued reliability and responsiveness.

Our DocV service has also shown strong recovery and should now be mostly restored, with only minimal residual impact observed. While AWS Secrets Manager and Security Token Service (STS) continue to experience intermittent networking issues on the AWS side, these are no longer materially affecting our operations.

We will continue to monitor system performance closely and work with AWS to validate complete recovery.
Thank you for your continued patience and understanding throughout this incident. We remain committed to ensuring full stability and optimal performance across all Socure services.

Socure has provided the following update:

We continue to work closely with AWS to address the issues impacting system performance. AWS has reported that approximately 97 of their services remain impacted, though they are showing steady signs of recovery across multiple regions.

We are now seeing improved service availability across all Socure services, with overall traffic and response rates continuing to stabilize. Our systems remain performant, and our engineering teams are closely monitoring service health to ensure consistent reliability and full recovery.

Our DocV service continues to experience some authentication failures, primarily due to ongoing issues within AWS Secrets Manager and AWS Security Token Service (STS). While the underlying AWS services are now functional, they continue to be affected by networking issues on the AWS side, intermittently impacting authentication and credential access. These issues are gradually dissipating as AWS continues to recover.

To further mitigate impact, we have implemented targeted workarounds, including bypassing certain problematic AWS services that previously caused HMAC authentication failures, which has helped improve stability and reduce errors.

AWS continues to make steady progress toward full restoration across their infrastructure, and we are actively validating improvements in real time.

We appreciate your continued patience and understanding as AWS completes its recovery. Our teams remain fully engaged and are treating this matter with the highest urgency to ensure all Socure services return to full operational stability.

Socure has provided the following update:

We continue to work closely with AWS to address the underlying issues impacting system performance. AWS has reported that over 105 of their services remain affected, extending beyond EC2, Lambda, and other core infrastructure components. These widespread disruptions have contributed to intermittent service degradation across multiple AWS regions.
Despite these challenges, we have made significant progress and have successfully restored service availability to approximately 97% of all traffic. Our systems are stable, and our engineering teams continue to closely monitor performance while implementing targeted mitigations.
With AWS’s support, we have allocated the necessary GPU resources in the US-EAST-2 region to support our DocV service. However, DocV remains partially degraded due to ongoing issues with AWS Secrets Manager and AWS Security Token Service (STS), both of which continue to affect authentication and credential access.
To reduce the remaining impact, our teams have implemented additional mitigations, bypassing certain problematic AWS services that were causing HMAC authentication failures. These measures are resulting in steady improvements to DocV performance and overall system stability.
AWS has communicated that they expect most affected services to be fully restored within the next hour, and we are beginning to see continued signs of recovery across our platform. We remain in constant contact with AWS to validate progress and ensure all services return to full operational status as quickly as possible.
We understand how critical reliability is for our customers and continue to treat this issue with the highest priority. We will provide further updates as AWS confirms full recovery.

Socure has provided the following update:

We continue to work closely with AWS to address the underlying issues impacting system performance. AWS has reported that over 105 of their services are currently impacted, extending beyond EC2, Lambda, and other previously affected components. These disruptions are contributing to intermittent service degradations across multiple AWS regions.
Despite these challenges, we have made substantial progress and have successfully restored service availability to approximately 97% of all traffic. Our systems remain stable, and our teams continue to monitor performance and optimize recovery efforts.
With AWS’s support, we were able to allocate the necessary GPU resources in the US-EAST-2 region to support our DocV service. However, DocV remains partially degraded due to ongoing issues within AWS Secrets Manager and AWS Security Token Service (STS), both of which are critical for authentication and secure access to service credentials. These dependencies are continuing to affect DocV’s ability to fully recover.
AWS has informed us that they expect most affected services to return to full availability within the next two hours. We are in constant communication with their engineering teams to validate recovery progress and expedite the full restoration of all impacted Socure services.
We understand the importance of reliability and uptime for our customers and are treating this situation with the highest urgency. We will continue to provide timely updates as AWS progresses toward complete service restoration.

Socure has provided the following update:

We are actively working in close partnership with AWS to address the underlying issues currently impacting system performance. At this time, approximately 79 AWS services remain in a degraded state. The primary cause stems from issues within AWS’s Identity and Access Management (IAM), Security Token Service (STS), and Secrets Manager — all of which are critical dependencies for secure authentication and service operations.
We have made substantial progress and have now successfully restored service availability to approximately 97% of all traffic. Our teams continue to monitor performance and stability closely while working toward full recovery.
Our DocV service remains partially degraded due to GPU instance availability limitations in the US-EAST-2 region, which are required to support document verification workloads. We are working closely with AWS engineers to secure additional GPU capacity and resolve the issue as quickly as possible.
AWS has also reported that several customers are experiencing similar challenges in US-EAST-2, where EC2, Lambda, and other core services are being throttled. These broader regional limitations continue to affect our ability to perform a full failover to our disaster recovery (DR) region.
We remain in constant communication with AWS and are treating this matter with the highest urgency. Our teams are committed to achieving full service restoration as quickly as possible and will continue to share updates as more information becomes available.

Socure has provided the following update:

We are actively working in close partnership with AWS to address the underlying issues currently impacting system performance. At this time, approximately 79 AWS services remain in a degraded state. The primary cause stems from issues within AWS’s Identity and Access Management (IAM), Security Token Service (STS), and Secrets Manager — all of which are critical dependencies for secure authentication and service operations.
Despite these challenges, we have made significant progress and have successfully restored service availability to approximately 90% of overall traffic. Our engineering teams continue to optimize and stabilize affected components to further improve performance and reliability.
Our AWS support team has informed us that several other customers are also experiencing difficulties switching over to the US-EAST-2 region, as EC2, Lambda, and several other services are currently being throttled in that region. These limitations are contributing to our inability to perform a full failover to our disaster recovery (DR) region at this time.
We remain in continuous communication with AWS engineers and are collaborating closely to expedite resolution and achieve full service restoration as quickly as possible. We understand the critical importance of reliability for our customers and are treating this issue with the highest urgency. We will continue to provide timely updates as more information becomes available from AWS.

Socure has provided the following update:

We are actively working in close partnership with AWS to address the underlying issues currently impacting system performance. At this time, approximately 79 AWS services remain in a degraded state. The primary cause stems from issues within AWS’s Identity and Access Management (IAM), Security Token Service (STS), and Secrets Manager — all of which are critical dependencies for secure authentication and service operations.
Despite these challenges, we have made significant progress and have successfully restored service availability to approximately 90% of overall traffic. Our engineering teams continue to optimize and stabilize affected components to further improve performance and reliability.
Due to the ongoing AWS service disruptions, we are still unable to perform a complete failover to our disaster recovery (DR) region. However, we remain in continuous communication with AWS engineers and are collaborating closely to expedite resolution and full restoration of normal operations.
We understand how important consistent reliability is for our customers, and we are treating this as our top priority. We will continue to provide timely updates as additional information becomes available from AWS.

Clients are reporting issues when trying to pull Socure reports.

Socure has acknowledged this problem with the following statement:
Impact: Service availability remains around 65%, with intermittent failures and increased latency across several components.
We continue to see service instability as the AWS outage persists. AWS has reported a global IAM service issue, which is currently preventing us from executing certain recovery and failover actions — including initiating a full disaster recovery (DR) transition.
The failures are not isolated to specific servers or paths, and we are observing unpredictable request behavior originating from AWS’s infrastructure. Our team remains actively engaged and is monitoring system performance closely while coordinating with AWS to restore full availability.

MeridianLink will provide updates when they're received from Socure directly.