Google Cloud incident report (status.cloud.google.com)
from kid@sh.itjust.works to cybersecurity@sh.itjust.works on 15 Jun 23:58
https://sh.itjust.works/post/40242383

#cybersecurity

threaded - newest

kid@sh.itjust.works on 16 Jun 00:02 next collapse

The incident occurred on June 12, 2025, due to a policy change that contained blank fields, causing 503 errors in Google Cloud and Google Workspace APIs. The root cause was:

  1. A new feature added to Service Control on May 29, 2025, without adequate error handling.
  2. The policy change with blank fields was globally replicated and caused Service Control binaries to crash.
IllNess@infosec.pub on 16 Jun 02:50 collapse

I know what the problem is.

February’s Google job cuts now layer on HR and Cloud divisions, with Cloud layoffs echoing last year’s 10% workforce reduction.

The HR Digest: Google cloud layoffs and HR cuts, what’s the 2025 memo hiding?, Feb 28, 2025)