Earlier quoted context omitted.
There is always one bootlicker, fresh 1 day account no less.
Then let me be the not day-one account to say Railway is utterly bearing some responsibility here. "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. T…
Incident Report: May 19, 2026 – GCP Account Suspension
211–220 of 279 posts
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#212The interesting and yet-to-be-explained part is why google flagged the account? Put all the timestamps you want in the post mortem about what you observed, but you haven't addressed the root cause. The "this doesn't make sense" part of the story likely has a real explanation that nobody wants to reveal yet.
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#213Re: Incident Report: May 19, 2026 – GCP Account Suspension
#214Question: 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, Render, and even Heroku still are all better choices then working with Railway I think
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#215Re: Incident Report: May 19, 2026 – GCP Account Suspension
#216"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.
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#217Earlier quoted context omitted.
This feels like google applying the same anti-spam mindset everywhere: detect risk, ban first, ask questions later.
It's pretty stupid that big customers like Railway are not somehow protected from this.
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#218Earlier quoted context omitted.
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
#219"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.
Never could. Google might block your entire company because one of your workers did something nasty on their personal account, and their ban hammer is mighty and blocks all related accounts to the Nth degree
Re: Incident Report: May 19, 2026 – GCP Account Suspension
#220>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.