AWS Global Outage

Hi Team,

We’d like to inform you that the AWS network connectivity issues in the US-EAST-1 Region have now been resolved.

Between 11:49 PM PDT on October 19 (Oct 20, 12:19 PM IST) and 2:24 AM PDT on October 20 (Oct 20, 2:54 PM IST), AWS experienced increased error rates and latencies across multiple services due to DNS resolution issues affecting regional DynamoDB endpoints, which subsequently impacted EC2, Lambda, and other dependent services.

All affected AWS services have now returned to normal operations as of 3:01 PM PDT (Oct 21, 3:31 AM IST), and connectivity has been fully restored. Some services may continue processing residual backlogs, which AWS expects to clear shortly.

However rest assured We will continue to monitor for continued stability.

Please feel free to reach out to Sprinklr Support if you have any questions or need further assistance

Hi Team,

We’d like to inform you that AWS has reported ongoing recovery across multiple Availability Zones (AZs) in the US-EAST-1 Region. EC2 instance launches are now succeeding in most zones, and network connectivity issues affecting DynamoDB, SQS, and Amazon Connect are gradually subsiding.

For Lambda, intermittent function errors may still occur when making network requests, but queued events are being processed and full recovery is expected within the next two hours. Services dependent on EC2, such as ECS and Glue, will recover as instance launch rates improve.

We are closely monitoring the situation and will share further updates as more information becomes available.

Thank you for your patience and understanding.

Hi Team,

AWS has reported ongoing recovery across multiple Availability Zones in the US-EAST-1 Region. EC2 instance launches are now succeeding in most zones, and network connectivity issues affecting services such as DynamoDB, SQS, and Amazon Connect are gradually subsiding.

For Lambda, customers may still experience intermittent function errors when functions make network requests to other services, as AWS continues to address residual connectivity issues. Steps such as adjusting SQS polling rates via Lambda Event Source Mappings are helping improve invocation success.

We will continue to closely monitor the situation and share further updates as more information becomes available.

Thank you for your patience and understanding.

Hi team,

We’d like to inform you that AWS has reported that their mitigations to resolve launch failures for new EC2 instances are progressing, with internal EC2 subsystems showing early signs of recovery in several Availability Zones (AZs) within the US-EAST-1 Region.

Mitigations are now being applied to the remaining AZs, and AWS expects launch errors and network connectivity issues affecting services such as DynamoDB, SQS, and Amazon Connect to gradually subside as recovery continues.

We will continue to monitor AWS’s progress and provide further updates as more information becomes available.

Thank you for your patience and understanding.

Hi Team,

We’d like to inform you that AWS is continuing to investigate the root cause of the ongoing network connectivity issues impacting services such as DynamoDB, SQS, and Amazon Connect in the US-EAST-1 Region.

According to AWS, the issue originated within the EC2 internal network, and their engineering teams are actively working on identifying mitigations and restoring full service functionality.

We are closely monitoring the situation and will share further updates as more information becomes available.

Thank you for your patience and understanding.

We are currently observing significant API errors and connectivity issues impacting multiple services. These issues are related to AWS operations in the US-EAST-1 Region. Our engineering teams are actively monitoring the situation and coordinating with AWS to restore full functionality.

We will keep you informed as soon as further updates are available.

Thank you for your patience and understanding.

Hi Team,

We are monitoring the ongoing AWS US-EAST-1 incident, which is affecting multiple services. AWS has started recovery, and operations are gradually stabilizing. Some delays may still occur as they work through the backlog and restore full functionality.

Our teams are actively tracking the situation and coordinating closely with AWS. We will provide another update as soon as more information is available.

Hi Team,

AWS has applied initial mitigations to the ongoing issue in their us1 Region, and we are now observing significant signs of recovery across our affected services. Most requests are currently succeeding, and performance is steadily improving.
Our incident response team continues to monitor the situation closely in collaboration with AWS. We will maintain heightened oversight until full resolution is confirmed.

Thank you for your continued patience. We will share additional updates as new information becomes available.

Hi Team,
AWS has applied initial mitigations to the ongoing issue in their us1 Region, and we are now observing significant signs of recovery across our affected services. Most requests are currently succeeding, and performance is steadily improving.
Our incident response team continues to monitor the situation closely in collaboration with AWS. We will maintain heightened oversight until full resolution is confirmed.
Thank you for your continued patience. We will share additional updates as new information becomes available.

We are currently experiencing service disruptions across multiple product lines due to an ongoing incident with AWS in their us1 Region.
Our incident response team has been activated and is actively working on mitigation while coordinating closely with AWS. The issue has been escalated to AWS leadership for expedited resolution.

At this stage, no failover actions to alternative regions are recommended. Should this guidance change, we will immediately communicate the updated instructions.

We appreciate your patience and understanding. Further updates will be shared as soon as additional information becomes available.