Live data from Hacker News

Incident Report: May 19, 2026 – GCP Account Suspension

blog.railway.com

141–150 of 279 posts

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#141
post #29

Earlier quoted context omitted.

> These cloud providers need to step back and observe how terrible they've made these products. They don't, because the allure of effortless scaling is hard to resist: everyone thinks of themselves as the next tech unicorn. And if you actually become an unicorn, you're already too dependent on AWS / Azure / GCP to easily move somewhere else. At best, your strategy is to become "multi-cloud".

That effortlessness is a fantasy. That's illustrated right here in this write-up by how complicated their system is. >Railway’s network is a mesh ring, built up of high availability fiber interconnects between Metal GCP AWS. However, in this ring, there was still a hard dependency on workload discoverability being tied to the network control plane API that was hosted on the machines running in Google Cloud What the h…

"We had all of our workers set up in an open office layout to to make sure everyone could talk to each other without a single point of failure. But last night the boss got too drunk and didn't come in, so everyone spent the day scrolling tiktok."

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#143
post #70
post #60

Earlier quoted context omitted.

Meta is no different. I know a company that had their OAuth app on Meta rendered completely unusable just because one of their employees (a dev) had their personal Facebook account banned by Meta for no reason. They tried to escalate it multiple times but got nowhere, lol. Meta is even worse because accounts need to be 'personal'; if you have a Business Manager, the users added to it are all tied to their personal Me…

[flagged]

[deleted]

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#144

This should be a warning to anyone running GCP. They suspend accounts left right and centre without even thinking about what they're doing. It seems like they use Gemini 3.1 Pro to run their production decisions. TK has a history of absolutely destroying the culture of the place like in OCI and has done something similar in GCP from what I've heard. GCP and Google are completely different entities with how they work.…

Hasn't theGoog acted this way of quick to suspend accounts well before Gemini? I like to bash on LLMs as much as the next guy, but this seems very much like the memory of a gold fish. Or, you are just too young to remember pre-LLMs???

Haha, no. I know Google bans anyone randomly with usually no recourse in sight. I just wanted to take a dig at how bad their LLM is too while we were at it and thinks like Google themselves which is not surprising.

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#145

This should be a warning to anyone running GCP. They suspend accounts left right and centre without even thinking about what they're doing. It seems like they use Gemini 3.1 Pro to run their production decisions. TK has a history of absolutely destroying the culture of the place like in OCI and has done something similar in GCP from what I've heard. GCP and Google are completely different entities with how they work.…

> It seems like they use Gemini 3.1 Pro to run their production decisions. They said they are already using Gemini 3.5 Pro internally.

Then it's a bad endorsement for Gemini 3.5 pro too. But jokes aside, I think they need a customer centric thinking instead of a self-centred one they seem to harbour even before TK joined (not everything can be blamed on him although it should be his responsibility now).

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#146

What drives Google to apply these actions so completely and immediately, versus a more deliberate approach, with notification and delay before action, manual review for paying customers, or a warning to resolve within X hours/days? Once or twice could be errors or bad implementation, but these can't explain away the pattern. It would seem that Google's counsel has deemed that whenever _____ is detected, the company m…

It could be automated action based on abuse reports. TONS of spam comes from Railway associated networks.

I work in a security adjacent role and I know we have had a few incidents that involved Railway networks lately. Could be something to that, I don't know

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#147

This should be a warning to anyone running GCP. They suspend accounts left right and centre without even thinking about what they're doing. It seems like they use Gemini 3.1 Pro to run their production decisions. TK has a history of absolutely destroying the culture of the place like in OCI and has done something similar in GCP from what I've heard. GCP and Google are completely different entities with how they work.…

This feels like google applying the same anti-spam mindset everywhere: detect risk, ban first, ask questions later.

That seems to be the case. But as we see it backfires. Railway is very public, but we know at hacker news google has been doing this kind of thing for quite some time now.

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#148
post #93

This should be a warning to anyone running GCP. They suspend accounts left right and centre without even thinking about what they're doing. It seems like they use Gemini 3.1 Pro to run their production decisions. TK has a history of absolutely destroying the culture of the place like in OCI and has done something similar in GCP from what I've heard. GCP and Google are completely different entities with how they work.…

And this is Railway, a big enough name to top the HN main page and presumably find someone from Google to intervene at some point. I would have zero recourse if it was some little product that I built.

100% agree, I've seen on Twitter and HN small players facing similar issues with no recourse and response from Google. I don't know what kind of place they are trying to build there.

They got TK to woo the enterprise customers who were forced to be hostage to OCI. But it seems they are still doing opposite of hostage here.

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#149

This should be a warning to anyone running GCP. They suspend accounts left right and centre without even thinking about what they're doing. It seems like they use Gemini 3.1 Pro to run their production decisions. TK has a history of absolutely destroying the culture of the place like in OCI and has done something similar in GCP from what I've heard. GCP and Google are completely different entities with how they work.…

Hasn't theGoog acted this way of quick to suspend accounts well before Gemini? I like to bash on LLMs as much as the next guy, but this seems very much like the memory of a gold fish. Or, you are just too young to remember pre-LLMs???

They probably do use similar tech to make some of these decisions, though. And they always have done that as well.

Re: Incident Report: May 19, 2026 – GCP Account Suspension

#150

Earlier quoted context omitted.

> It seems like they use Gemini 3.1 Pro to run their production decisions. They said they are already using Gemini 3.5 Pro internally.

Then it's a bad endorsement for Gemini 3.5 pro too. But jokes aside, I think they need a customer centric thinking instead of a self-centred one they seem to harbour even before TK joined (not everything can be blamed on him although it should be his responsibility now).

Google? Customer-centric? The closest thing to that is their cloud division buttering up some big name clients.

Other than that, Google prefers to act like "customers" are some kind of unfortunate rash they can't quite seem to get rid of, but would love to do so.

Post reply on HN