Is Google Cloud Personalized Service Health down?
Current Google Cloud Personalized Service Health status is UP

Summary: Multiple regions: Cloud Logging is experiencing issues with displaying log data in Google Cloud Console
Description: 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.
After further investigation, the impact is narrowed down to logs from GCP products or services in us-central1, us-east1, and europe-west1 destined to any Cloud Logging buckets. We apologize for any confusion by the previous communications.
us-east1 recovered as of 10:20 US/Pacific and us-central1 recovered as of 13:42 US/Pacific.
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. The rollout to clear the logs backlog has completed to all the affected regions. The logs backlog for us-east1 completed as of 10:20 US/Pacific, for us-central1 completed as of 13:42 US/Pacific and for europe-west1 completed as of 14:15 US/Pacific
**Remaining Impact:** Customers using [log based metrics](https://cloud.google.com/logging/docs/logs-based-metrics) may observe metrics with no backing logs. Our engineering teams are working on mitigating the metrics backfill. We do not have an ETA for mitigation of log based metrics issue at this point.
The notification error rate for PSH has reduced significantly and we believe that the majority of the backed up notifications are delivered. As we gradually process the remaining logs in the pending queue, customers may see an increase of historical outage notifications from PSH for the affected time period. We apologize for the inconvenience.
We will provide more information by Tuesday, 2024-01-23 15:30 US/Pacific.
Diagnosis: - Customers using [log based metrics](https://cloud.google.com/logging/docs/logs-based-metrics) may observe metrics with no backing logs.
- Other impacts that were previously reported for Cloud Logging and PSH notifications should now be resolved.
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.

Summary: Global: Cloud Logging Data Unavailable in Google Cloud Console
Description: We are experiencing an issue with Cloud Logging.
Our engineering team continues to investigate the issue.
We identified the potential root cause and working on a mitigation strategy.
We will provide more information by Tuesday, 2024-01-23 12:00 US/Pacific.
Diagnosis: Customers are unable to receive fresh logs at this time in the Google Cloud Console.
Workaround: None at this time.