Service Health
Incident affecting Google Cloud Infrastructure Components
We are experiencing network latency in us-central1 and us-east1
Incident began at 2021-01-19 11:12 and ended at 2021-01-19 13:57 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 19 Jan 2021 | 13:57 PST | The issue with Google Cloud infrastructure components is believed to be currently affecting a very small number of projects 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. No further updates will be provided here. We thank you for your patience while we're working on resolving the issue. |
| 19 Jan 2021 | 13:40 PST | Description: We believe the issue with Google Cloud infrastructure components is partially resolved and risk of reoccurrence is low. The last event with this issue happened at 11:39 AM US/Pacific We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-01-19 15:00 US/Pacific with current details. Diagnosis: Cloud Networking traffic going through us-central1 and us-east1 shows increased latency. Workaround: None at this time. |
| 19 Jan 2021 | 13:25 PST | Description: Our engineering team has determined that further investigation is required to mitigate the issue. The issue remains intermittent. We will provide an update by Tuesday, 2021-01-19 14:00 US/Pacific with current details. Diagnosis: Cloud Networking traffic going through us-central1 and us-east1 shows increased latency. Workaround: None at this time. |
| 19 Jan 2021 | 12:06 PST | Description: We are experiencing an intermittent issue with Google Cloud infrastructure components, the issue manifests itself as periods of increased latency every 30 minutes, beginning at Tuesday, 2021-01-19 07:50:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2021-01-19 13:30 US/Pacific with current details. Diagnosis: Cloud Networking traffic going through us-central1 and us-east1 shows increased latency. Workaround: None at this time. |
- All times are US/Pacific