Is Google Cloud Identity and Access Management down?
Current Google Cloud Identity and Access Management status is UP

Summary: Multiple product outage in europe-west8-b
Description: We are experiencing an issue with Virtual Private Cloud (VPC) beginning on Wednesday, 2024-02-07 02:46 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2024-02-07 03:45 US/Pacific with current details.
Diagnosis: Most customers will find all VMs in europe-west8-b will be unreachable.
Workaround: None at this time.
Summary: Multiple product outage in europe-west8-b
Description: We are experiencing an issue with Persistent Disk, Google Cloud Networking, Service Directory, Traffic Director, Cloud Load Balancing, Google Cloud DNS, Cloud Memorystore, Cloud Dataflow, Cloud Build, Cloud SQL, Cloud Filestore beginning on Wednesday, 2024-02-07 02:46 US/Pacific.
Other products are likely impacted. Mitigation work is currently underway by our engineering team.. The mitigation is expected to complete by Wednesday, 2024-02-07 05:00 US/Pacific.
We will provide an update by Wednesday, 2024-02-07 05:00 US/Pacific with current details.
Diagnosis: Customers are unable to reach any of the impacted Google Cloud products in europe-west8-b.
Workaround: None at this time

Summary: Multiple product outage in europe-west8-b
Description: We are experiencing an issue with Google Kubernetes Engine, Cloud Key Management Service, Google BigQuery, Google Cloud Bigtable, Virtual Private Cloud (VPC), Google Cloud Deploy, Google Compute Engine, Persistent Disk, Google Cloud Networking, Service Directory, Traffic Director, Cloud Load Balancing, Google Cloud DNS, Cloud Memorystore, Cloud Dataflow, Cloud Build, Cloud SQL, Cloud Filestore, Identity and Access Management beginning on Wednesday, 2024-02-07 02:46 US/Pacific.
Other products are likely impacted. Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Wednesday, 2024-02-07 04:30 US/Pacific.
We will provide an update by Wednesday, 2024-02-07 04:30 US/Pacific with current details.
Diagnosis: Customers are unable to reach any of the impacted Google Cloud products in europe-west8-b.
Workaround: None at this time.
Summary: Multiple product outage in europe-west8-b
Description: We are experiencing an issue with Virtual Private Cloud (VPC) beginning on Wednesday, 2024-02-07 02:46 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2024-02-07 03:45 US/Pacific with current details.
Diagnosis: Most customers will find all VMs in europe-west8-b will be unreachable.
Workaround: None at this time.

Summary: Some Cloud Firestore customers experiencing permission denied errors when reading and writing to their database.
Description: Initial mitigation attempt did not resolve the issue and our engineering team has determined that further investigation is required to mitigate the issue.
We will provide an update by Wednesday, 2023-11-15 16:50 US/Pacific with current details.
Diagnosis: Customers may experience permission denied errors when using Firebase Rules to authenticate access to Cloud Firestore.
Workaround: None at this time.

Summary: Customers with Cloud products in asia-south2 or Cloud Interconnects in Delhi can face partial packet loss. 
Description: Our engineering team is continuing to work on mitigating  the issue by re-directing traffic away from the impacted network components. 
The packet loss is resolved at 09:41 US/Pacific for zone1 Interconnects or HA0 Interconnect attachments . 
We do not have an ETA for mitigation at this point. 
We will provide more information by Thursday, 2023-07-27 11:30 US/Pacific.
Diagnosis: Customers with Cloud products in asia-south2 or Cloud Interconnects in Delhi can experience partial packet loss. 
The current packet loss is limited to large MTU packets in zone2 Interconnects in [Delhi] (https://cloud.google.com/network-connectivity/docs/interconnect/concepts/choosing-colocation-facilities#locations-table) or HA1 Interconnect attachments in asia-south2.
Workaround: Affected customers should failover to zone1 Interconnects or HA0 Interconnect attachments.
Summary: Chronicle Security customers may experience data staleness or missed detections in US regions.
Description: Our engineering team is continuing mitigation efforts.
We do not have an ETA for mitigation at this point.
We will provide more information by Thursday, 2023-07-27 12:00 US/Pacific.
Diagnosis: All features in Chronicle are still working but the impacted users may get stale data while searching for UDM events, and they may experience missed threat detections for recently ingested telemetry.
All data ingested on or before 2023-07-25 08:30 US/Pacific has been processed successfully. There are gaps in UDM search for data ingested after that time. Recent telemetry for data ingested after this time may result in missed threat detections as well.
successfully. There are gaps in UDM search for data ingested after that time. Recent telemetry for data ingested after this time may result in missed threat detections as well.
Workaround: Customers can run raw log searches and should still be able to access results. Searches with raw log should be targeted to a log type or string/regex.
Customers can also leverage indexed UDM searches to surface up to date results. Indexed UDM searches must leverage one of the following UDM fields and one of the following UDM nouns. These searches must be an exact match on a field, which means they cannot include a REGEX expression or REF list. Basic Boolean logic that combines these UDM fields with other conditions should also surface fresh data (e.g. noun.field1 AND noun.field2)
Nouns:
Principal
Target
Field Names:
Hostname
Ip
Mac
Asset
File.md5
File.sha1
File.sha256
process.file.md5
process.file.sha1
process.file.sha256
process.parent_process.file.md5
process.parent_process.file.sha1
process.parent_process.file.sha256
Additionally the vast majority of single event rules are still being processed.
Summary: We are experiencing an issue with Cloud Filestore
Description: Mitigation work is currently underway by our engineering team.
We do not have an ETA for mitigation at this point.
We will provide more information by Friday, 2023-07-28 14:00 US/Pacific.
Diagnosis: Customers may be experiencing issues with instances access control changes not being applied.
Workaround: None at this time.

Summary: Serverless VPC Access users of VPC Service Controls are experiencing issues with creating and deleting service connectors.
Description: We are experiencing an issue with VPC Service Controls.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2023-07-26 16:15 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Affected customers will not be able to create or delete service connectors.
Workaround: Affected customers can use the workaround documented at https://cloud.google.com/vpc-service-controls/docs/supported-products#deployment_manager
Summary: Chronicle Security customers may experience data staleness or missed detections in US regions.
Description: Our engineering team is continuing to work on mitigating this issue.
We do not have an ETA for mitigation at this point.
We will provide more information by Wednesday, 2023-07-26 17:30 US/Pacific.
Diagnosis: All features in Chronicle are still working but the impacted users may get stale data while searching for UDM events, and they may experience missed threat detections for recently ingested telemetry.
All data ingested on or before 2023-07-25 08:30 US/Pacific has been processed successfully. There are gaps in UDM search for data ingested after that time. Recent telemetry for data ingested after this time may result in missed threat detections as well.
Workaround: Customers can still leverage indexed UDM searches to surface up to date results. Additionally the vast majority of single event rules are still being processed.
Summary: We are experiencing an issue with Cloud Filestore
Description: Mitigation work is currently underway by our engineering team.
We do not have an ETA for mitigation at this point.
We will provide more information by Friday, 2023-07-28 14:00 US/Pacific.
Diagnosis: Customers may be experiencing issues with instances access control changes not being applied.
Workaround: None at this time.