Resolved
We have not detected any new impact in the last 30 minutes. It appears that the underlying AWS issue has been resolved; however, we are continuing to monitor the situation closely to ensure stability across all affected regions.
Investigating
We are now detecting errors in the Ohio (us-east-2) and N. California (us-west-1) AWS regions, in addition to the ongoing issues in the N. Virginia (us-east-1) region. We are actively investigating this expanded scope.
Investigating
Despite earlier signs of recovery the issue has resurfaced. We are detecting new impact and have resumed active investigation. We remain in contact with AWS to resolve this recurrence.
Resolved
AWS has marked the DynamoDB issue as resolved. It has now been more than 1 hour without any new impact on our end.
Monitoring
We are beginning to observe signs of recovery, with no new impact identified over the past 30 minutes. We remain in contact with AWS and are continuing to monitor the situation closely.
We will provide further updates as necessary.
Monitoring
Some functionalities affected so far:
Resuming async Decisions
Managing Connections
DB Connector Node
Jobs
Identified
Since ~18:00 UTC we have been tracking intermittent 5xx API responses in the N.Virginia (us-east-1) AWS region. The root cause is an ongoing AWS DynamoDB service incident.