Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors
May 28, 20:22 UTCMay 29, 22:14 UTC
Duration
25h 51m
Impact
Informational
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-east-1Amazon Web Services (AWS) - us-east-1
Final update
The service has remained stable since the initial behavior was observed 5/28 19:40 to 20:05 UTC. A permanent fix for the region is now in-progress.
Timeline
- Resolved · May 29, 22:14 UTC
The service has remained stable since the initial behavior was observed 5/28 19:40 to 20:05 UTC. A permanent fix for the region is now in-progress.
- Monitoring · May 29, 10:48 UTC
The service continues to operate normally. We will provide additional updates as they become available.
- Monitoring · May 29, 02:11 UTC
The service remains stable. We are continuing to monitor closely while work progresses on a permanent fix to prevent recurrence.
- Monitoring · May 28, 23:17 UTC
We have confirmed the service is now stable and are now working to ensure a permanent fix is in place to prevent any recurrence. We will continue to monitor for errors until the fix is deployed.
- Monitoring · May 28, 22:14 UTC
Service has remained stable and we are continuing to monitor the situation. We will continue to provide updates as they become available.
- Monitoring · May 28, 21:00 UTC
The gRPC UNIMPLEMENTED errors previously observed have been mitigated. We are continuing to monitor the situation and are working towards a permanent fix at this time.
- Identified · May 28, 20:22 UTC
Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors today from 19:40 to 20:05 UTC. We have identified a root cause and are currently working towards a permanent fix.
More from Temporal
Full historyNew namespace creation restricted across all GCP regionsstill 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 0mElevated GCP storage latency in us-central1 – precautionary namespace failoverlasted 4h 25mIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIlasted 29m