Google Cloud Status Dashboard
This page provides status information on the services that are part of Google Cloud Platform. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit cloud.google.com.
Google Cloud Networking Incident #21003
External HTTP(S) Load Balancers can't be created, updated, and deleted.
Incident began at 2021-02-24 08:32 and ended at 2021-02-24 09:19 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Feb 24, 2021 | 09:19 | The issue with External HTTP(S) Load Balancers regarding creation, updates and deletions, has been resolved for all affected users as of Wednesday, 2021-02-24 08:55 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|
The issue with External HTTP(S) Load Balancers regarding creation, updates and deletions, has been resolved for all affected users as of Wednesday, 2021-02-24 08:55 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|||
| Feb 24, 2021 | 09:03 | Description: We are experiencing an issue with External HTTP(S) Load Balancers beginning at Wednesday, 2021-02-24 07:54 US/Pacific. Existing configurations and Load Balancers are not affected. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. However current signs show improvements. We will provide more information by Wednesday, 2021-02-24 09:45 US/Pacific. Diagnosis: Any change applied to an External HTTP(S) Load Balancer gets stuck. Workaround: None at this time. |
|
Description: We are experiencing an issue with External HTTP(S) Load Balancers beginning at Wednesday, 2021-02-24 07:54 US/Pacific. Existing configurations and Load Balancers are not affected. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. However current signs show improvements. We will provide more information by Wednesday, 2021-02-24 09:45 US/Pacific. Diagnosis: Any change applied to an External HTTP(S) Load Balancer gets stuck. Workaround: None at this time. |
|||
| Feb 24, 2021 | 08:38 | Description: We are experiencing an issue with External HTTP(S) Load Balancers beginning at Wednesday, 2021-02-24 07:54 US/Pacific. Existing configurations and Load Balancers are not affected. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-02-24 09:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Any change applied to an External HTTP(S) Load Balancer gets stuck. Workaround: None at this time. |
|
Description: We are experiencing an issue with External HTTP(S) Load Balancers beginning at Wednesday, 2021-02-24 07:54 US/Pacific. Existing configurations and Load Balancers are not affected. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-02-24 09:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Any change applied to an External HTTP(S) Load Balancer gets stuck. Workaround: None at this time. |
|||
| Feb 24, 2021 | 08:32 | Description: We are experiencing an issue with External HTTP(S) Load Balancers beginning at Wednesday, 2021-02-24 07:54 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-02-24 09:15 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Any change applied to an External HTTP(S) Load Balancer gets stuck. Workaround: None at this time. |
|
Description: We are experiencing an issue with External HTTP(S) Load Balancers beginning at Wednesday, 2021-02-24 07:54 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-02-24 09:15 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Any change applied to an External HTTP(S) Load Balancer gets stuck. Workaround: None at this time. |
|||