Kore.ai incident
Temporary Service Disruption Linked to AWS Outage
Kore.ai experienced a major incident on October 20, 2025 affecting AWS ec2-us-east-1 and AWS ec2-ap-northeast-1 and 1 more component, lasting 3h 43m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 09:41 AM UTC
Hello Everyone, We are aware of the ongoing outage currently reported by AWS. Our internal teams are actively validating systems to assess any potential impact related to this AWS outage. We are closely monitoring the situation and will provide timely updates on this page as new information becomes available. For more details on the AWS outage, please refer to the official AWS Status Page: https://health.aws.amazon.com/health/status
- monitoring Oct 20, 2025, 10:11 AM UTC
We have received the following update from AWS: “We continue to observe recovery across most of the affected AWS services. Global services and features that rely on the US-EAST-1 region have also recovered. We are continuing to work toward full resolution and will share further updates as more information becomes available.” Our teams will continue to monitor the situation closely and provide additional updates as necessary.
- monitoring Oct 20, 2025, 11:37 AM UTC
The AWS team is actively working toward full recovery from EC2 launch errors, which may appear as “Insufficient Capacity” errors. In addition, they are continuing efforts to mitigate increased polling delays affecting AWS Lambda, particularly for Lambda Event Source Mappings with SQS.
- monitoring Oct 20, 2025, 01:05 PM UTC
AWS is reporting significant progress in resolving the issue that was preventing the launch of new EC2 instances in the US-EAST-1 Region. New instances can now be launched successfully in a number of Availability Zones, and they are actively working to restore the remaining ones. Additionally, the backlog of events for EventBridge and CloudTrail has been cleared, and new events are being delivered normally. We will provide further updates when we receive new information from AWS.
- monitoring Oct 20, 2025, 01:24 PM UTC
Update - We have not observed any disruptions to our runtime services and our internal monitoring and alerting is also not showing any issues. With this, we are closing this incident. We will continue to monitor the AWS health and status page (https://health.aws.amazon.com/health/status) and will report if we see anything is impacting our services.
- resolved Oct 20, 2025, 01:24 PM UTC
This incident has been resolved.