Is Cloud Logging down?
Current Cloud Logging status is UP

Summary: Apigee API Platform - Service Issues
Description: Starting Wednesday, 2024-05-08 16:41 US/Pacific, customers making use of caching policies in their API proxies are experiencing issues with Apigee API Platform services.
The mitigation roll out is progressing region by region, and the roll out will continue till all regions have received the update. We expect this to be completed within the next 8 hours. We do not have an ETA for completion of mitigation at this time.
We will provide an update by Thursday, 2024-05-09 08:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Impacted customers may experience latency in the completion of their API calls.
Workaround: There is no workaround at this time.

Summary: Apigee API Platform - Service Issues
Description: Starting Wednesday, 2024-05-08 16:41 US/Pacific, customers making use of caching policies in their API proxies are experiencing issues with Apigee API Platform services.
The mitigation roll out is progressing region by region, and the roll out will continue till all regions have received the update. We expect this to be completed within the next 8 hours. We do not have an ETA for completion of mitigation at this time.
We will provide an update by Thursday, 2024-05-09 08:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Impacted customers may experience latency in the completion of their API calls.
Workaround: There is no workaround at this time.

Summary: Multiple services impacted in australia-southeast1.
Description: We are experiencing an issue with Persistent Disk, Google Cloud Dataflow, Google Cloud Pub/Sub, Google BigQuery, Google Compute Engine, Cloud Filestore, Virtual Private Cloud (VPC), Cloud logging, Cloud SQL, Cloud Bigtable, Apigee beginning at Wednesday, 2024-05-08 18:45 US/Pacific.
Mitigation strategy has been identified. The services are now recovering.
We will provide an update by Wednesday, 2024-05-08 23:00 US/Pacific with current details.
Diagnosis: Multiple GCP services are experiencing issues in australia-southeast1 region.
**Persistent Disk:** While most devices have restored their functionality, some users might encounter slow or unavailable devices.
**Google Cloud Dataflow:** Users experienced issues for streaming jobs with Watermark increasing. The issue with Google Cloud Dataflow is mitigated at 2024-05-08 19:47:27 PDT.
**Google Cloud Pub/Sub:** The PubSub impact is mitigated.
**Google BigQuery:** The impacted users experienced failures with the bigquery jobs in the australia-southeast1 Region. The issue with Google Bigquery has been resolved for all the affected users as of Wednesday, 2024-05-08 21:13 US/Pacific.
**Google Compute Engine:** VM’s went into repair for around 45 minutes and have started recovering.
**Cloud Filestore:** The Filestore is partially recovered. However, a small subset of users would not able to access the NFS filestore in the australia-southeast1-a zone.
**Virtual Private Cloud (VPC):** The impacted users may face delays while creating new VMs and packet loss / unreachability for existing VMs.
**Cloud SQL:** A subset of the Cloud SQL users are experiencing errors when accessing their Cloud SQL database instances in the australia-southeast1-a zone.
**Cloud logging:** All requests are failing at the send request step. The issue with Cloud logging has been resolved for all the affected users as of Wednesday, 2024-05-08 21:16:07 US/Pacific.
**Cloud Bigtable:** Cloud Bigtable experienced a high error rate for 25 minutes in australia-southeast1-a due to a power event. The issue with Cloud Bigtable has been resolved for all the affected users as of Wednesday, 2024-05-08 20:08:30 US/Pacific.
**Apigee:** There was a minor outage due to the GKE error which caused all of the nodes to restart. The GKE cluster is currently undergoing repair. This resulted in a 30 minute outage for the customer. The issue with Apigee has been resolved for all the affected users as of Wednesday 2024-05-08 20:34:47 US/Pacific.
Workaround: None at this time.
Summary: Apigee API Platform - Service Issues
Description: Starting Wednesday, 2024-05-08 16:41 US/Pacific, customers making use of caching policies in their API proxies are experiencing issues with Apigee API Platform services.
The mitigation roll out is in progress, we do not have an ETA for completion of mitigation at this time.
We will provide an update by Wednesday, 2024-05-08 23:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Impacted customers may experience latency in the completion of their API calls.
Workaround: There is no workaround at this time.

Summary: Multiple services impacted in australia-southeast1.
Description: We are experiencing an issue with Persistent Disk, Google Cloud Dataflow, Google Cloud Pub/Sub, Google BigQuery, Google Compute Engine, Cloud Filestore, Virtual Private Cloud (VPC), Cloud logging, Cloud SQL, Cloud Bigtable, Apigee beginning at Wednesday, 2024-05-08 18:45 US/Pacific.
Mitigation strategy has been identified. The services are now recovering.
We will provide an update by Wednesday, 2024-05-08 23:00 US/Pacific with current details.
Diagnosis: Multiple GCP services are experiencing issues in australia-southeast1 region.
**Persistent Disk:** While most devices have restored their functionality, some users might encounter slow or unavailable devices.
**Google Cloud Dataflow:** Users experienced issues for streaming jobs with Watermark increasing. The issue with Google Cloud Dataflow is mitigated at 2024-05-08 19:47:27 PDT.
**Google Cloud Pub/Sub:** The PubSub impact is mitigated.
**Google BigQuery:** The impacted users experienced failures with the bigquery jobs in the australia-southeast1 Region. The issue with Google Bigquery has been resolved for all the affected users as of Wednesday, 2024-05-08 21:13 US/Pacific.
**Google Compute Engine:** VM’s went into repair for around 45 minutes and have started recovering.
**Cloud Filestore:** The Filestore is partially recovered. However, a small subset of users would not able to access the NFS filestore in the australia-southeast1-a zone.
**Virtual Private Cloud (VPC):** The impacted users may face delays while creating new VMs and packet loss / unreachability for existing VMs.
**Cloud SQL:** A subset of the Cloud SQL users are experiencing errors when accessing their Cloud SQL database instances in the australia-southeast1-a zone.
**Cloud logging:** All requests are failing at the send request step. The issue with Cloud logging has been resolved for all the affected users as of Wednesday, 2024-05-08 21:16:07 US/Pacific.
**Cloud Bigtable:** Cloud Bigtable experienced a high error rate for 25 minutes in australia-southeast1-a due to a power event. The issue with Cloud Bigtable has been resolved for all the affected users as of Wednesday, 2024-05-08 20:08:30 US/Pacific.
**Apigee:** There was a minor outage due to the GKE error which caused all of the nodes to restart. The GKE cluster is currently undergoing repair. This resulted in a 30 minute outage for the customer. The issue with Apigee has been resolved for all the affected users as of Wednesday 2024-05-08 20:34:47 US/Pacific.
Workaround: None at this time.
Summary: Apigee API Platform - Service Issues
Description: Starting Wednesday, 2024-05-08 16:41 US/Pacific, customers making use of caching policies in their API proxies are experiencing issues with Apigee API Platform services.
The mitigation roll out is in progress, we do not have an ETA for completion of mitigation at this time.
We will provide an update by Wednesday, 2024-05-08 23:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Impacted customers may experience latency in the completion of their API calls.
Workaround: There is no workaround 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.