What is a JSON feed? Learn more

JSON Feed Viewer

Browse through the showcased feeds, or enter a feed URL below.

Now supporting RSS and Atom feeds thanks to Andrew Chilton's feed2json.org service

CURRENT FEED

Google Cloud Status Dashboard Updates

A feed by Google Cloud Platform

XML


RESOLVED: Incident 20006 - We are experiencing issues with creation of new Google Cloud Load Balancers and updates to existing ones.

Permalink - Posted on 2020-07-02 16:36

The issue with Google Cloud Load Balancer has been resolved for all affected users as of Thursday, 2020-07-02 09:36 US/Pacific. We thank you for your patience while we're working on resolving the issue.


UPDATE: Incident 20006 - We are experiencing issues with creation of new Google Cloud Load Balancers and updates to existing ones.

Permalink - Posted on 2020-07-02 15:57

Description: We are experiencing an issue with Cloud Cloud Load Balancer as of Thursday, 2020-07-02 08:39 US/Pacific. Customers will not be able to create new HTTP services or update certain aspects of existing services (timeouts, health checks, backend port). They will still be able to drain, add groups, and add/remove VMs. We will provide more information by Thursday, 2020-07-02 10:15 US/Pacific. Diagnosis: Customers will not be able to create new HTTP services or update certain aspects of existing services (timeouts, health checks, backend port). Workaround: None at this time.


RESOLVED: Incident 20003 - GKE Clusters in us-east1c may be unavailable

Permalink - Posted on 2020-06-29 20:15

The issue with Google Kubernetes Engine has been resolved for the majority of affected projects as of Monday, 2020-06-29 11:15 US/Pacific. If you have questions or feel that you may be impacted, please open a case with the Support Team and we will work with you until the issue is resolved. We will publish analysis of this incident once we have completed our internal investigation. We thank you for your patience while we're working on resolving the issue.


RESOLVED: Incident 20005 - We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 20:06

The issue with Cloud Networking and Persistent Disk has been resolved for the majority of affected projects as of Monday, 2020-06-29 10:20 US/Pacific, and we expect full mitigation to occur for remaining projects within the hour. If you have questions or feel that you may be impacted, please open a case with the Support Team and we will work with you until the issue is resolved. We will publish analysis of this incident once we have completed our internal investigation. We thank you for your patience while we're working on resolving the issue.


UPDATE: Incident 20005 - We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 19:17

Description: We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services. Services in us-east1-d have been fully restored. Services in us-east1-c are fully restored except for Persistent Disk which is partially restored. No ETA for full recovery of Persistent Disk yet. Impact is due to power failure. A more detailed analysis will be available at a later time. Our engineering team is working on recovery of impacted services. We will provide an update by Monday, 2020-06-29 13:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones. Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.


UPDATE: Incident 20005 - We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 18:45

Description: We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services. Services in us-east1-d have been fully restored. Services in us-east1-c are fully restored except for Persistent Disk which is partially restored. No ETA for full recovery of Persistent Disk yet. Impact is due to power failure. A more detailed analysis will be available at a later time. Our engineering team is working on recovery of impacted services. We will provide an update by Monday, 2020-06-29 12:20 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones. Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.


UPDATE: Incident 20003 - GKE Clusters in us-east1c may be unavailable

Permalink - Posted on 2020-06-29 18:41

Description: We are experiencing an issue with Google Kubernetes Engine in us-east1-c where clusters may be unavailable or unreachable beginning at Monday, 2020-06-29 07:15 US/Pacific US/Pacific. Mitigation work is currently underway by our engineering team. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005


RESOLVED: Incident 20005 - We are experiencing issues with Google Compute Engine Autoscaling in us-east1-c

Permalink - Posted on 2020-06-29 18:40

The issue with Google Compute Engine has been resolved for all affected users as of Monday, 2020-06-29 11:39 US/Pacific. For current information on the broader incident, and for any public incident reports that may follow, please see https://status.cloud.google.com/incident/cloud-networking/20005. We thank you for your patience while we're working on resolving the issue.


RESOLVED: Incident 20002 - We are experiencing an issue with Cloud Memorystore in us-east1-c and us-east1-d.

Permalink - Posted on 2020-06-29 18:29

The issue with Cloud Memorystore has been resolved for all affected users as of Monday, 2020-06-29 11:27 US/Pacific. For current information on the broader incident, and for any public incident reports that may follow, please see https://status.cloud.google.com/incident/cloud-networking/20005 We thank you for your patience while we're working on resolving the issue.


UPDATE: Incident 20003 - GKE Clusters in us-east1c may be unavailable

Permalink - Posted on 2020-06-29 18:13

Description: We are experiencing an issue with Google Kubernetes Engine in us-east1-c where clusters may be unavailable or unreachable beginning at Monday, 2020-06-29 07:15 US/Pacific US/Pacific. Mitigation work is currently underway by our engineering team. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 11:45 US/Pacific.


UPDATE: Incident 20005 - We are experiencing issues with Google Compute Engine Autoscaling in us-east1-c

Permalink - Posted on 2020-06-29 18:12

Description: We are experiencing an intermittent issue with Google Compute Engine Managed Instance Group's Autoscaler beginning on Monday, 2020-06-29 08:15 US/Pacific. Mitigation work is underway. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 11:45 US/Pacific . Diagnosis: Autoscaling of instances in Managed Instance Groups may not occur due to instances being unreachable. Workaround: None at this time.


UPDATE: Incident 20005 - We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 18:00

Description: We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services. Services in us-east1-d have been restored. Most services in us-east1-c are restored except for Persistent Disk. No ETA for Persistent disk recovery as of now. Impact is due to power failure. A more detailed analysis will be available at a later time. Our engineering team is working on recovery of impacted services. We will provide an update by Monday, 2020-06-29 11:45 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones. Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.


UPDATE: Incident 20005 - We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 17:31

Description: We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services. Services in us-east1-d have been restored. Most services in us-east1-c are restored except for Persistent Disk. No ETA for Persistent disk recovery as of now. Impact is due to power failure. A more detailed analysis will be available at a later time. Our engineering team is working on recovery of impacted services. We will provide an update by Monday, 2020-06-29 11:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones. Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.


UPDATE: Incident 20003 - GKE Clusters in us-east1c may be unavailable

Permalink - Posted on 2020-06-29 17:29

Description: We are experiencing an issue with Google Kubernetes Engine in us-east1-c where clusters may be unavailable or unreachable beginning at Monday, 2020-06-29 07:15 US/Pacific US/Pacific. Mitigation work is currently underway by our engineering team. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 11:00 US/Pacific.


UPDATE: Incident 20005 - We are experiencing issues with Google Compute Engine Autoscaling in us-east1-c

Permalink - Posted on 2020-06-29 17:28

Description: We are experiencing an intermittent issue with Google Compute Engine Managed Instance Group's Autoscaler beginning on Monday, 2020-06-29 08:15 US/Pacific. Mitigation work is underway. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 11:00 US/Pacific . Diagnosis: Autoscaling of instances in Managed Instance Groups may not occur due to instances being unreachable. Workaround: None at this time.


UPDATE: Incident 20005 - We are experiencing issues with Google Compute Engine Autoscaling in us-east1-c

Permalink - Posted on 2020-06-29 17:20

Description: We are experiencing an intermittent issue with Google Compute Engine Managed Instance Group's Autoscaler beginning on Monday, 2020-06-29 08:15 US/Pacific. Our engineering team continues to investigate the issue. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 10:30 US/Pacific . Diagnosis: Autoscaling of instances in Managed Instance Groups may not occur due to instances being unreachable. Workaround: None at this time.


UPDATE: Incident 20003 - GKE Clusters in us-east1c may be unavailable

Permalink - Posted on 2020-06-29 17:07

Description: We are experiencing an issue with Google Kubernetes Engine in us-east1-c where clusters may be unavailable or unreachable beginning at Monday, 2020-06-29 07:15 US/Pacific US/Pacific. Mitigation work is currently underway by our engineering team. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 10:30 US/Pacific.


UPDATE: Incident 20005 - We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 17:00

Description: We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services. Services in us-east1-d have been restored. Services in us-east1-c are still being restored. No ETA as of now. Impact is due to power failure. A more detailed analysis will be available at a later time. Our engineering team is working on recovery of impacted services. We will provide an update by Monday, 2020-06-29 10:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones. Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.


RESOLVED: Incident 20004 - We are experiencing an issue with Google Compute Engine in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 17:00

The issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific has been resolved for all affected users as of Monday, 2020-06-29 09:45 US/Pacific. The impact to us-east1-d has been mitigated by Monday, 2020-06-29 08:45 US/Pacific. The impact to us-east1-c has been mitigated by Monday, 2020-06-29 09:45 US/Pacific. For additional information on the broader outage and any follow up reports, please see https://status.cloud.google.com/incident/cloud-networking/20005 We thank you for your patience while we're working on resolving the issue.


UPDATE: Incident 20004 - We are experiencing an issue with Google Compute Engine in us-east1-c and us-east1-d

Permalink - Posted on 2020-06-29 16:56

The issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific has been resolved for all affected users as of Monday, 2020-06-29 09:45 US/Pacific. We are experiencing an issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific. The impact to us-east1-d has been mitigated by Monday, 2020-06-29 08:45 US/Pacific. The impact to us-east1-c has been mitigated by Monday, 2020-06-29 09:45 US/Pacific. We thank you for your patience while we're working on resolving the issue.