Google Cloud MINOR
Cloud Translation experienced elevated latency and error rates
January 28, 2025 · 12:50 PM UTC – 10:16 PM UTC · Duration: 9h 26min
Affected Services
Cloud Machine LearningCloud Translation
Timeline
10:16 PM
The issue with Cloud Translation has been resolved for all affected users as of Tuesday, 2025-01-28 14:00 US/Pacific.
We thank you for your patience while we worked on resolving the issue.
09:36 PM
Summary: Cloud Translation experiencing elevated latency and error rates
Description: Our engineering team has mitigated the issue and are showing signs of
recovery. We will continue to monitor the service for stability.
We will provide more information by Tuesday, 2025-01-28 15:00 US/Pacific.
Diagnosis: Customers may experience elevated latency, error rates including 'resource exhausted' or service unavailable.
Workaround: None at this time.
08:03 PM
Summary: Cloud Translation experiencing elevated latency and error rates
Description: Mitigation work is currently underway by our engineering team. We are seeing signs of recovery and continue to monitor for further impact.
We do not have an ETA for mitigation at this point.
We will provide more information by Tuesday, 2025-01-28 13:00 US/Pacific.
Diagnosis: Customers may experience elevated latency, error rates including 'resource exhausted' or service unavailable.
Workaround: None at this time.
06:44 PM
Summary: Cloud Translation experiencing elevated latency and error rates
Description: Mitigation work is currently underway by our engineering team. We are seeing signs of recovery and continue to monitor for further impact.
We do not have an ETA for mitigation at this point.
We will provide more information by Tuesday, 2025-01-28 12:00 US/Pacific.
Diagnosis: Customers may experience elevated latency, error rates including 'resource exhausted' or service unavailable.
Workaround: None at this time.
06:33 PM
Summary: We are experiencing an issue with Cloud Translation
Description: We are experiencing an issue with Cloud Translation beginning at Tuesday, 2025-01-28 04:50 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2025-01-28 11:08 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: None at this time.
Workaround: None at this time.