Incidentsby GlyphSome customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures
Nov 6, 13:40 UTCNov 6, 17:25 UTC
Duration
3h 44m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
22 incidents
Affected
us-west-2Amazon Web Services (AWS) - us-west-2
Final update
We have observed no more failures since the fix and are fully recovered. This incident is now resolved.
Timeline
- Resolved · Nov 6, 17:25 UTC
We have observed no more failures since the fix and are fully recovered. This incident is now resolved.
- Monitoring · Nov 6, 14:27 UTC
We applied a mitigation and are monitoring the results.
- Identified · Nov 6, 14:21 UTC
We've identified the issue, and mitigation is in progress.
- Investigating · Nov 6, 13:40 UTC
Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures We are investigating
More from Temporal
Full historyIntermittent 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, us-east4 and europe-west3still openElevated latency and errors in GCP us-west1lasted 17mElevated latency and errors in AWS us-east-1lasted 2h 17mElevated error rates for cross-region traffic between US AWS regionslasted 0m