Customers in us-east-1 may experience elevated latency in the Visibility API
Nov 16, 09:19 UTCNov 16, 20:12 UTC
Duration
10h 53m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
21 incidents
Affected
us-east-1Amazon Web Services (AWS) - us-east-1
Final update
This incident has been resolved. Impact was primarily observed between 8:45 - 9:33 UTC.
Timeline
- Resolved · Nov 16, 20:12 UTC
This incident has been resolved. Impact was primarily observed between 8:45 - 9:33 UTC.
- Monitoring · Nov 16, 10:49 UTC
Visibility API latency has returned to pre-incident levels. We’re continuing to monitor.
- Investigating · Nov 16, 10:43 UTC
AWS has acknowledged an issue affecting some EC2 services in this region. We’ll provide more details as soon as they become available
- Investigating · Nov 16, 10:13 UTC
Customers may still experience delays in workflow updates being reflected in the Visibility API and increased latency when using the List and Count APIs. We are working with AWS to investigate the issue.
- Investigating · Nov 16, 09:19 UTC
Customers in us-east-1 may experience elevated latency in the Visibility API and delays in workflow updates being reflected in the API.
More from Temporal
Full historyElevated error rates on Temporal Cloud Ops APIlasted 0mStandalone activities actions correctionlasted 0mSome customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failureslasted 3h 44mIntermittent request failures for some namespaces in GCP us-east4lasted 45mElevated connection resets for some GCP namespaceslasted 0mNew namespace creation restricted across few GCP regions. Impacted regions are us-central1 and europe-west3lasted 33d 3h