Live data from Hacker News

Incident Report: May 19, 2026 – GCP Account Suspension

blog.railway.com

161–170 of 279 posts

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

#161

Question: for a smaller SaaS tool, or even internal product. If a team doesn't want to manage AWS or another IaaS provider, what are the best alternatives for the following 1.) Vercel - having a bad month 2.) Supabase - having a bad month 3.) Railway - now having a bad month

Fly.io (AFAIK) still has a relatively good track record?

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

#162

Earlier quoted context omitted.

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.

Yup, updated with the article I mentioned by Steve Yegge. Still holds true today.

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

#163
post #15

"Finally, we are in planning to remove Google Cloud services from our data plane’s hot path, and keeping them only for secondary/failover." That's pretty clear. Google can no longer be trusted as a B2B service provider.

They have not explained WHY their account was suspended. That's the most important part, imo. Cloud Providers don't suspend entire accounts for no reason.

> "Cloud Providers don't suspend entire accounts for no reason."

Maybe I'm getting old but here[1] is a HN comment from 17 years ago complaining about Google banning accounts "by mistake" and having no recourse but to post on HN and hope Matt Cutts sees it and helps, and saying "there are literally 1000s of such stories for many years all over the blogoshphere and forums" which is something I remember from HN of years ago.

[1] https://news.ycombinator.com/item?id=791004

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

#164

Earlier quoted context omitted.

I don't think you're typically told why for these things, and it's mostly automated from what I can tell. The automated systems make mistakes but more importantly they're completely opaque. Nobody, not even Google, knows how they work exactly.

For big accounts, like railway, zero chance this was a handsoff fully automated ban

That assumes a competent org. If this were aws, I fully believe that. At gcp it's entirely plausible.

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

#166
post #15

"Finally, we are in planning to remove Google Cloud services from our data plane’s hot path, and keeping them only for secondary/failover." That's pretty clear. Google can no longer be trusted as a B2B service provider.

I'm not sure that's the lesson to learn from this outage. Hell Google resolved the problem in 7 minutes which is as good as you could hope for.

The resulting action should be you have proper disaster recovery, failover, etc.

Not sure I would trust these folks if this is the conclusion they are coming to from this experience. Any cloud provider can/will do this to you.

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

#167
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.

This is the bigger point of all of this. Scary.

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

#168

Earlier quoted context omitted.

> google knows it's the same household as the parent, Nearly all these linkages are due to people sharing recovery email addresses and phone numbers. Don't do that.

Are you honestly saying that a kid should not use their parent's email address as a recovery option? Seems like that would be the natural way to do it.

I don’t know about you, but I have a family account that we use as an email recovery for kids.

Adults have multiple emails so they won’t have to share it.

If something takes out the family email account, that’s fine. The only thing going there regularly are school notices, contractor receipts and recovery emails.

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

#169
post #15

"Finally, we are in planning to remove Google Cloud services from our data plane’s hot path, and keeping them only for secondary/failover." That's pretty clear. Google can no longer be trusted as a B2B service provider.

Railway don't have a great reputation for building scalable systems (effects of vibe coding?). It's worth waiting for Google's response before jumping to conclusions. They can move to Azure/AWS/own datacenter, but there's a good chance this will repeat in a few months.

There is always one bootlicker, fresh 1 day account no less.

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

#170

Unfortunately we had to make emergency migration off to Azure yesterday due to this. Thankfully our DB was not hosted on Railway and we were back up in a couple hours. As much as we loved the simplicity they provided us, there's just been too many mishaps and shortcomings for us to continue running a B2B enterprise app on their infrastructure. Sad day :(

What were your reasons for going with railway in the first place? I'm not super familiar with them, but did you choose them for unique offerings, or essentially just VMs? If unique offerings, how rough was the migration out?
Post reply on HN