Is Cloud Logging down?
Current Cloud Logging status is UP

Summary: Multiple Google Cloud Products are experiencing issues in us-west1
Description: We are experiencing an issue with multiple Google Cloud Products beginning on Wednesday, 2024-02-14 9:40 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2024-02-14 12:30 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Existing customer load balancers will continue to function. New load balancers or changes to existing load balancers will not propagate configs and changes to the configurations of load balancers may result in an error.
Configuration changes can not be made to the Regional Internal, Regional External, and Global External Application Load Balancers in the affected region.
Customers may see errors when making configuration changes.
Workaround: None at this time.

Summary: Multiple Google Cloud Products are experiencing issues in us-west1
Description: We are experiencing an issue with multiple Google Cloud Products beginning on Wednesday, 2024-02-14 9:40 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2024-02-14 12:30 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Existing customer load balancers will continue to function. New load balancers or changes to existing load balancers will not propagate configs and changes to the configurations of load balancers may result in an error.
Configuration changes can not be made to the Regional Internal, Regional External, and Global External Application Load Balancers in the affected region.
Customers may see errors when making configuration changes.
Workaround: None at this time.

Summary: Global: Cloud Logging Data is experiencing issues with displaying log data in Google Cloud Console
Description: We are experiencing an issue with Cloud Logging, Cloud Dataflow, and Personalized Service Health (PSH).
After further investigation, the impact is narrowed down to Cloud Logging customers using buckets configured in us-central1, us-east1, europe-west1, and Global rather than all the regions as previously mentioned. We apologize for any confusion this may have caused.
Our engineering team has narrowed down the root cause to a feature rollout that started at 09:30 US/Pacific. The new feature usage caused contention in the backend database.
Our engineers have completed the roll back of the new feature and are currently working on processing the logs in the pending queue in us-central1, europe-west1,Global buckets. us-east1 recovered as of 10:20 US/Pacific. Currently, the ETA for the full mitigation is 1 hour.
We will provide more information by Tuesday, 2024-01-23 14:00 US/Pacific.
Diagnosis:
* Customers are unable to receive logs at this time in the Google Cloud Console.
* Cloud Dataflow is impacted and we are working to identify other downstream impacts.
* GCP products and services using Cloud Logging are potentially impacted.
* Customers using PSH notifications are also impacted. While the PSH dashboard is available and outage communications are displayed on it, customers will not get notifications on the outages until issue resolution. Additionally, log messages written by PSH are also impacted. Integrations to the PSH API are not impacted.
Workaround: None at this time.

Summary: Global: Cloud Logging Data is experiencing issues with displaying log data in Google Cloud Console
Description: We are experiencing an issue with Cloud Logging, Cloud Dataflow, and Personalized Service Health (PSH).
After further investigation, the impact is narrowed down to Cloud Logging customers using buckets configured in us-central1, us-east1, europe-west1, and Global rather than all the regions as previously mentioned. We apologize for any confusion this may have caused.
Our engineering team has narrowed down the root cause to a feature rollout that started at 09:30 US/Pacific. The new feature usage caused contention in the backend database.
Our engineers have completed the roll back of the new feature and are currently working on processing the logs in the pending queue in us-central1, europe-west1,Global buckets. us-east1 recovered as of 10:20 US/Pacific. Currently, the ETA for the full mitigation is 1 hour.
We will provide more information by Tuesday, 2024-01-23 14:00 US/Pacific.
Diagnosis:
* Customers are unable to receive logs at this time in the Google Cloud Console.
* Cloud Dataflow is impacted and we are working to identify other downstream impacts.
* GCP products and services using Cloud Logging are potentially impacted.
* Customers using PSH notifications are also impacted. While the PSH dashboard is available and outage communications are displayed on it, customers will not get notifications on the outages until issue resolution. Additionally, log messages written by PSH are also impacted. Integrations to the PSH API are not impacted.
Workaround: None at this time.

Summary: Global: Cloud Logging Data is experiencing issues with displaying log data in Google Cloud Console
Description: We are experiencing an issue with Cloud Logging, Cloud Dataflow, and Personalized Service Health (PSH).
Our engineering team has narrowed down the root cause to a feature rollout that started at 09:30 US/Pacific. The new feature usage caused contention in the backend database.
Our engineers have completed the roll back of the new feature and are currently working on processing the logs in the pending queue. Currently, the ETA for the full mitigation is 3 hours.
We will provide more information by Tuesday, 2024-01-23 13:00 US/Pacific.
Diagnosis:
* Customers are unable to receive logs at this time in the Google Cloud Console.
* Cloud Dataflow is impacted and we are working to identify other downstream impacts.
* GCP products and services using Cloud Logging are potentially impacted.
* Customers using PSH notifications are also impacted. While the PSH dashboard is available and outage communications are displayed on it, customers will not get notifications on the outages until issue resolution. Additionally, log messages written by PSH are also impacted. Integrations to the PSH API are not impacted.
Workaround: None at this time.