4 ms·

The two Google Cloud networking incidents are: Incident #19008 began at 2019-06-02 12:48. https://status.cloud.google.com/incident/cloud-networking/19008 https

The two Google Cloud networking incidents are: Incident #19008 began at 2019-06-02 12:48. https://status.cloud.google.com/incident/cloud-networking/19008 https://status.cloud.google.com/incident/cloud-networking/19... Incident #19009 began at 2019-06-02 12:53. https://status.cloud.google.com/incident/cloud-networking/19009 https://status.cloud.google.com/incident/cloud-networking/19... Times are US/Pacific

pm90 7y ago
They both seem to say the same thing....
boulos 7y ago
dang et al.: I’d make 19009 the URL for this (GCE Just reported first, but this is an outage / networking issue in the Eastern US).
- AnssiH 7y ago
  #19008 mentioned by parent is not the GCE one, there are two networking ones: #19008 and #19009. The #19008 (networking) says there will be an update by "13:30 US/Pacific", but as of 17:05 there is no update. Similarly, #19003 (GCE) says there will be an update by "16:00 US/Pacific", but no update as of 17:05. All the latest updates seem to only be in the third incident #19009 (networking).
cheeze 7y ago
Looks like they are having trouble updating their statuses. 19008 was supposed to be updated over an hour ago. Meanwhile, 19009 has the same comment posted three times. I'm guessing internal tools are barely working at best.
- londons_explore 7y ago
  That is normal for Google status pages. They don't want to admit fault or place blame because there can be legal and commercial ramifications, so they can only say canned responses.
  - cheeze 7y ago
    Updating a status page, sure. They aren't going to say "JamesBondService is having issues because a bug was deployed", but they usually don't repeat the same message 3 times in the same minute and they are usually pretty good about sticking to an update "within SLA"