close
close

Google Cloud Service Health Status

Google Cloud Service Health Status

Google Cloud Service Health Status

This page provides information about the status of the services that are part of Google Cloud. Check back here to see the current status of the services listed below. If you encounter an issue that is not listed here, please contact support. To learn more about what is published on the dashboard, see this FAQ. For more information about these services, visit https://cloud.google.com/.

  • Available
  • Service information
  • Service interruption
  • Service failure

Customers using AutoML translations may experience high latency and failures due to “resource exhaustion”.

The incident began at 02/08/2024 09:30 and ended at 02/08/2024 17:36 (all times are United States/Pacific).

Previously affected locations

Netherlands (europe-west4)Iowa (us-central1)

Date Time Description
August 2, 2024 5:36pm PDT

Our engineering team has successfully completed validations and confirmed that the issue has been mitigated.

If you have any questions or need further assistance, please open a case with the Support Team and we will work with you to ensure your concerns are addressed.

We appreciate your patience as we work to resolve the issue.

August 2, 2024 2:58 PM PDT

Summary: Clients using AutoML translations may experience high latency and failures due to resource exhaustion.

Description: We believe the issue with AutoML Translation is mitigated based on our monitoring.

Our engineering team is further validating the mitigation, to ensure the issue is fully resolved for all of our customers.

We will provide an update by Friday 2024-08-02 7:00 PM US/Pacific with current details.

Diagnosis: When users use translation with custom models, most requests fail either due to timeout/resource exhaustion or with latency up to 2 minutes.

Workaround: None at this time.

August 2, 2024 11:53 PDT

Summary: Clients using AutoML translations may experience high latency and failures due to resource exhaustion.

Description: We believe the issue with AutoML Translation is mitigated based on our monitoring.

Our engineering team continues to validate to ensure the issue is fully resolved for all of our customers.

We will provide an update by Friday 2024-08-02 3:00 PM US/Pacific with current details.

Diagnosis: When users use translation with custom models, most requests fail either due to timeout/resource exhaustion or with latency up to 2 minutes.

Workaround: None at this time.

August 2, 2024 10:18 PDT

Summary: Clients using AutoML translations may experience high latency and failures due to resource exhaustion.

Description: We believe the issue with AutoML Translation is mitigated based on our monitoring.

Our engineering team is currently conducting further validation to ensure the issue is fully resolved for all of our customers.

We will provide an update by Friday 2024-08-02 12:00 PM US/Pacific with current details.

Diagnosis: When users use translation with custom models, most requests fail either due to timeout/resource exhaustion or with latency up to 2 minutes.

Workaround: None at this time.

August 2, 2024 09:56 PDT

Summary: Clients using AutoML translations may experience high latency and failures due to resource exhaustion.

Description: We are experiencing an issue with AutoML translations

Our engineering team continues to investigate the issue.

We will provide an update by Friday, August 2, 2024 at 11:08 a.m. (US/Pacific Time) with current details.

We apologize to anyone affected by the disruption.

Diagnosis: AutoML translations may experience high latency and failures due to resource exhaustion.

Workaround: None at this time.

August 2, 2024 09:49 PDT

Summary: Clients using AutoML translations may experience high latency and failures due to resource exhaustion.

Description: We are experiencing an issue with Cloud Translation.

Our engineering team continues to investigate the issue.

We will provide an update by Friday, August 2, 2024 at 11:08 a.m. (US/Pacific Time) with current details.

We apologize to anyone affected by the disruption.

Diagnosis: None at this time.

Workaround: None at this time.