Service Health
-
-
-
-
Incident affecting Operations
The issue with Google Stackdriver Logging has been resolved for all affected projects as of 20:02 US/Pacific.
Incident began at 2018-01-31 18:20 and ended at 2018-01-31 19:50 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| | 7 Feb 2018 | 10:06 PST | On Wednesday 31 January 2017, some Google Cloud services experienced elevated errors and latency on operations that required inter-data center network traffic for a duration of 72 minutes. The impact was visible during three windows: between 18:20 and 19:08 PST, between 19:10 and 19:29, and again between 19:45 and 19:50. Network traffic between the public internet and Google's data centers was not affected by this incident. The root cause of this incident was an error in a configuration update to the system that allocates network capacity for traffic between Google data centers. To prevent a recurrence, we will improve the automated checks that we run on configuration changes to detect problems before release. We will be improving the monitoring of the canary to detect problems before global rollout of changes to the configuration. |
| | 31 Jan 2018 | 20:49 PST | The issue with Google Stackdriver Logging has been resolved for all affected projects as of 20:02 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. For everyone who is affected, we apologize for the disruption. |
| | 31 Jan 2018 | 20:23 PST | The issue with Google Stackdriver Logging should be resolved for the majority of projects and we expect a full resolution in the near future. We will provide another status update by 20:45 US/Pacific with current details. |
| | 31 Jan 2018 | 19:28 PST | We are investigating an issue with Google Stackdriver Logging. We will provide more information by 20:00 US/Pacific. |
- All times are US/Pacific