Service Health
Incident affecting Google Compute Engine
Network disruption in us-central1-c
Incident began at 2016-05-20 13:08 and ended at 2016-05-20 16:55 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 20 May 2016 | 17:01 PDT | The issue with networking in us-central1-a should have been resolved for all affected instances as of 16:55 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
| 20 May 2016 | 16:08 PDT | The issue with networking in us-central1-c should have been resolved for the majority of affected instances and we expect a full resolution in the near future. Customers still experiencing networking issues in us-central1-c can perform a Stop/Start cycle on their instances to regain connectivity. We will provide another status update by 17:00 US/Pacific with current details. |
| 20 May 2016 | 15:21 PDT | We are still investigating the issue with networking in us-central1-c. Current data indicates that between approximately 0.5% of instances in the zone are affected by this issue. We will provide another status update by 16:00 US/Pacific with current details. |
| 20 May 2016 | 14:45 PDT | We are experiencing an issue with networking in us-central1-c beginning at Friday, 2016-05-20 13:08. Some instances will be inaccessible by internal and external IP addresses. No other zones are affected by this incident. We will provide more information by 15:30 US/Pacific. |
| 20 May 2016 | 14:04 PDT | We are investigating an issue with networking in us-central1-c. We will provide more information by 14:30 US/Pacific. |
- All times are US/Pacific