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)
this post was submitted on 15 Jun 2025
9 points (100.0% liked)
Cybersecurity
7584 readers
87 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub
Notable mention to !cybersecuritymemes@lemmy.world
founded 2 years ago
MODERATORS
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:
- A new feature added to Service Control on May 29, 2025, without adequate error handling.
- The policy change with blank fields was globally replicated and caused Service Control binaries to crash.