Service Health
Incident affecting Google Cloud Networking
Google AppEngine customers may experience connectivity issues to endpoints on Azure
Incident began at 2023-06-15 18:08 and ended at 2023-06-16 05:47 (all times are US/Pacific).
Previously affected location(s)
Iowa (us-central1)South Carolina (us-east1)
Date | Time | Description | |
---|---|---|---|
| 16 Jun 2023 | 05:47 PDT | The issue with Google Cloud Networking is believed to be affecting a very small number of customers and our Engineering Team is working on it. If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved. We thank you for your patience while we're working on resolving the issue. |
| 16 Jun 2023 | 00:49 PDT | Summary: Google AppEngine customers may experience connectivity issues to endpoints on Azure Description: We are experiencing an issue with Google Cloud Networking. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2023-06-16 08:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Azure Cloud Endpoint calls are timing out for user in us-east1 and us-central1 while using Google Cloud Network. Some operations may fail with 'https 500 error' due to latency. Workaround: Affected users may use a VPC Connector and configure Cloud NAT with dynamic port ranges. |
| 15 Jun 2023 | 22:47 PDT | Summary: Google AppEngine customers may experience connectivity issues to endpoints on Azure. Description: We are experiencing an issue with Google Cloud Networking. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2023-06-16 01:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Azure Cloud Endpoint calls are timing out for user in us-east1 and us-central1 while using Google Cloud Network. Some operations may fail with 'https 500 error' due to latency. Workaround: Affected users may use a VPC Connector and configure Cloud NAT with dynamic port ranges. |
| 15 Jun 2023 | 20:32 PDT | Summary: Google AppEngine customers may experience connectivity issues to endpoints on Azure. Description: We are experiencing an issue with Google Cloud Networking. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-06-15 23:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Azure Cloud Endpoint calls are timing out for user in us-east1 and us-central1 while using Google Cloud Network. Some operations may fail with 'https 500 error' due to latency. Workaround: Affected users may use a VPC Connector and configure Cloud NAT with dynamic port ranges. |
| 15 Jun 2023 | 19:08 PDT | Summary: Google AppEngine customers may experience connectivity issues to endpoints on Azure. Description: We are experiencing an issue with Google Cloud Networking. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-06-15 22:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: None at this time. Workaround: None at this time. |
| 15 Jun 2023 | 18:36 PDT | Summary: Google AppEngine customers may experience connectivity issues to endpoints on Azure. Description: We are experiencing an issue with Google Cloud Networking. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-06-15 19:40 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: None at this time. Workaround: None at this time. |
| 15 Jun 2023 | 18:08 PDT | Summary: Google AppEngine customers may experience connectivity issues to endpoints on Azure. Description: We are experiencing an issue with Google Cloud Networking. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-06-15 18:40 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: None at this time. Workaround: None at this time. |
- All times are US/Pacific