>Google Cloud placed Railway’s production account into a suspended status incorrectly, as part of an automated action. There is no justification given on why this action was incorrect. It's possible they actually did something wrong.
Incident Report: May 19, 2026 – GCP Account Suspension
191–200 of 279 posts
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#192"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
#193Why would you use an infrastructure provider on top of another infrastructure provider? It adds cost and risk, it's always going to be a leaky abstraction, and it's not hard to learn how to use GCP or AWS correctly - especially with agents.
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#194Re: Incident Report: May 19, 2026 – GCP Account Suspension
#195This 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.…
What/who is TK? What is OCI?
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#196Re: Incident Report: May 19, 2026 – GCP Account Suspension
#197Re: Incident Report: May 19, 2026 – GCP Account Suspension
#198Earlier quoted context omitted.
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.
"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."
They've gotta be joking me that they deliberately left something so critical under the control of any other entity than themselves. That demonstrates a lack of critical planning and a lack looking at their configuration from a first-principles approach.
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#199Earlier 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.
Google should know why a human accepted the automated suggestion, or if and why there wasn't any human oversight in the first place.
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#200Question: 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
Azure!
It’s the enterprise cloud with enterprise support. They won’t randomly pull the plug on your account, unlike companies that have a wildly different cultural background:
Google - ad tech (you’re the product)
Amazon - shop front (you’re a comptetitor)
Oracle - lawyers (you’re a future lawsuit for license extortion)
Etc…