GCP Google Cloud Platform Incidents
@gcp-incidents.bsky.social
Posts from Google Cloud Platform (#gcp) Incidents. This is not an official account from Google. Created by @januz.nl
For the full incident details, follow this link [5/5]
July 23, 2025 at 9:30 AM
For the full incident details, follow this link [5/5]
products included AlloyDB, Apigee, and others. [4/5]
July 23, 2025 at 9:30 AM
products included AlloyDB, Apigee, and others. [4/5]
Monitoring alerted engineers on 18 July 2025 at 14:06 UTC, identifying the issue by 14:39 UTC. Remediation involved moving traffic from the affected fabric, fully restoring services by 16:47 UTC. Google is enhancing safety controls and mechanisms to prevent future occurrences. Affected [3/5]
July 23, 2025 at 9:30 AM
Monitoring alerted engineers on 18 July 2025 at 14:06 UTC, identifying the issue by 14:39 UTC. Remediation involved moving traffic from the affected fabric, fully restoring services by 16:47 UTC. Google is enhancing safety controls and mechanisms to prevent future occurrences. Affected [3/5]
On 18 July 2025, from 14:50 UTC to 16:47 UTC, several Google Cloud Platform (GCP) and Google Workspace (GWS) products experienced elevated latencies and error rates in the us-east1 region. The root cause was a procedural error during hardware replacement, leading to a network partition. [2/5]
July 23, 2025 at 9:30 AM
On 18 July 2025, from 14:50 UTC to 16:47 UTC, several Google Cloud Platform (GCP) and Google Workspace (GWS) products experienced elevated latencies and error rates in the us-east1 region. The root cause was a procedural error during hardware replacement, leading to a network partition. [2/5]
For the full incident details, follow this link [5/5]
July 22, 2025 at 1:50 PM
For the full incident details, follow this link [5/5]
AlloyDB, Cloud Run, and Google Workspace applications. [4/5]
July 22, 2025 at 1:50 PM
AlloyDB, Cloud Run, and Google Workspace applications. [4/5]
procedural error during a hardware replacement, leading to network partitioning. Google technicians restored connectivity by 16:47 UTC. Plans for prevention include enhancing safety controls and implementing measures against control plane partitioning by Q4 2025. Affected products include [3/5]
July 22, 2025 at 1:50 PM
procedural error during a hardware replacement, leading to network partitioning. Google technicians restored connectivity by 16:47 UTC. Plans for prevention include enhancing safety controls and implementing measures against control plane partitioning by Q4 2025. Affected products include [3/5]
On 18 July 2025, from 14:50 to 16:47 UTC, several Google Cloud Platform (GCP) and Google Workspace (GWS) products experienced elevated latencies and error rates in the us-east1 region. GCP was impacted for 1 hour and 57 minutes, while GWS had a 50-minute impact. The incident was caused by a [2/5]
July 22, 2025 at 1:50 PM
On 18 July 2025, from 14:50 to 16:47 UTC, several Google Cloud Platform (GCP) and Google Workspace (GWS) products experienced elevated latencies and error rates in the us-east1 region. GCP was impacted for 1 hour and 57 minutes, while GWS had a 50-minute impact. The incident was caused by a [2/5]
For the full incident details, follow this link [5/5]
July 18, 2025 at 10:40 PM
For the full incident details, follow this link [5/5]
Cloud Support or Google Workspace Support. [4/5]
July 18, 2025 at 10:40 PM
Cloud Support or Google Workspace Support. [4/5]
redirecting traffic and restoring the hardware. Affected GCP products included AlloyDB for PostgreSQL, Apigee, Cloud Storage, and more. Workspace products impacted were Gmail, Google Meet, and Google Drive. A detailed incident report will follow. For additional support, please contact Google [3/5]
July 18, 2025 at 10:40 PM
redirecting traffic and restoring the hardware. Affected GCP products included AlloyDB for PostgreSQL, Apigee, Cloud Storage, and more. Workspace products impacted were Gmail, Google Meet, and Google Drive. A detailed incident report will follow. For additional support, please contact Google [3/5]
On July 18, 2025, from 15:10 UTC to 16:47 UTC, multiple GCP and GWS products in the us-east1 region experienced elevated latencies and error rates, lasting 1 hour and 37 minutes. The root cause was a procedural error during planned hardware maintenance in a data center. Mitigation involved [2/5]
July 18, 2025 at 10:40 PM
On July 18, 2025, from 15:10 UTC to 16:47 UTC, multiple GCP and GWS products in the us-east1 region experienced elevated latencies and error rates, lasting 1 hour and 37 minutes. The root cause was a procedural error during planned hardware maintenance in a data center. Mitigation involved [2/5]
For the full incident details, follow this link [4/4]
July 18, 2025 at 10:30 PM
For the full incident details, follow this link [4/4]
multiple services, lasting up to 1 hour and 37 minutes for GCP and 30 minutes for GWS. Affected products include AlloyDB for PostgreSQL, Apigee, Cloud Storage, Google Meet, and Gmail, among others. A detailed incident report will follow. For further assistance, contact Google Cloud Support. [3/4]
July 18, 2025 at 10:30 PM
multiple services, lasting up to 1 hour and 37 minutes for GCP and 30 minutes for GWS. Affected products include AlloyDB for PostgreSQL, Apigee, Cloud Storage, Google Meet, and Gmail, among others. A detailed incident report will follow. For further assistance, contact Google Cloud Support. [3/4]
We apologize for the inconvenience caused by the service disruption on July 18, 2025, from 15:10 to 16:47 UTC impacting GCP and GWS products in the us-east1 region. The incident stemmed from a procedural error during hardware maintenance, leading to elevated latencies and error rates across [2/4]
July 18, 2025 at 10:30 PM
We apologize for the inconvenience caused by the service disruption on July 18, 2025, from 15:10 to 16:47 UTC impacting GCP and GWS products in the us-east1 region. The incident stemmed from a procedural error during hardware maintenance, leading to elevated latencies and error rates across [2/4]
For the full incident details, follow this link [5/5]
July 18, 2025 at 10:10 PM
For the full incident details, follow this link [5/5]
please contact Google Cloud or Workspace Support. [4/5]
July 18, 2025 at 10:10 PM
please contact Google Cloud or Workspace Support. [4/5]
minutes, while GWS was affected for 30 minutes from 15:10 to 15:40 UTC. The affected products included AlloyDB for PostgreSQL, Apigee, Cloud Storage, Google Meet, Gmail, and others. Google is preparing a full incident report detailing the root cause and preventive measures. For assistance, [3/5]
July 18, 2025 at 10:10 PM
minutes, while GWS was affected for 30 minutes from 15:10 to 15:40 UTC. The affected products included AlloyDB for PostgreSQL, Apigee, Cloud Storage, Google Meet, Gmail, and others. Google is preparing a full incident report detailing the root cause and preventive measures. For assistance, [3/5]
Incident Report Summary:
An incident occurred on July 18, 2025, from 15:10 to 16:47 UTC, impacting GCP and GWS services in the us-east1 region due to a procedural error during planned hardware maintenance. GCP experienced elevated latencies and error rates lasting up to 1 hour and 37 [2/5]
An incident occurred on July 18, 2025, from 15:10 to 16:47 UTC, impacting GCP and GWS services in the us-east1 region due to a procedural error during planned hardware maintenance. GCP experienced elevated latencies and error rates lasting up to 1 hour and 37 [2/5]
July 18, 2025 at 10:10 PM
Incident Report Summary:
An incident occurred on July 18, 2025, from 15:10 to 16:47 UTC, impacting GCP and GWS services in the us-east1 region due to a procedural error during planned hardware maintenance. GCP experienced elevated latencies and error rates lasting up to 1 hour and 37 [2/5]
An incident occurred on July 18, 2025, from 15:10 to 16:47 UTC, impacting GCP and GWS services in the us-east1 region due to a procedural error during planned hardware maintenance. GCP experienced elevated latencies and error rates lasting up to 1 hour and 37 [2/5]
For the full incident details, follow this link [4/4]
July 18, 2025 at 6:10 PM
For the full incident details, follow this link [4/4]