Comment by r721
17 hours ago
>We have resolved this incident and a post mortem is available here.
>https://blog.railway.com/p/incident-report-may-19-2026-gcp-a...
>May 20, 07:57 UTC
17 hours ago
>We have resolved this incident and a post mortem is available here.
>https://blog.railway.com/p/incident-report-may-19-2026-gcp-a...
>May 20, 07:57 UTC
Thanks! The post-mortem is currently on the frontpage here:
Incident Report: May 19, 2026 – GCP Account Suspension - https://news.ycombinator.com/item?id=48204770
> Railway owns our vendor choices, and we ultimately own this one. Your customers don't care whether the failure was Google or Railway; they see your product. Your uptime is our responsibility, and we'll keep delivering on it.
This is an excellent closing statement.
It should be possible to sue Google for damages in such cases. This isnt a network outage or service failure which I would consider part of ToS.
What if the reason for their stuff being shut down was a payment issue like an expired credit card or maxed credit account? Unless I missed it skim reading their post I don’t see any information anywhere about their communications with Google.
If you have an account manager and a contract, there's zero excuse for automated suspension. That's literally the whole point of having a dedicated person. From the report:
> May 19, 22:22 UTC - P0 ticket filed with Google Cloud. Railway's GCP account manager engaged directly.
It's always possible to sue, but Google has good terms of service and lawyers - I'm 99% confident that a lawsuit would end up nowhere.
They have every right to sue, and if they did sue they almost certainly would win. This is clear breach of contract. The only argument Google could make is "they did something to violate our agreement" but they'd have to prove that, and then have a damn good explanation for why they were in the right to suspend the account without any outreach. Unless Railway did something egregious, Google clearly made an error.
But that's not what will happen. Google will offer an apology (perhaps even a public one), a giant pile of account credit, and a pinky promise not to do it again. Railway will accept it and hmmm and haw internally about whether to decrease their reliance on GCP, and then when they calculate the cost of going in on other clouds more heavily (or their own metal), they'll just think harder about weird failure modes.
4 replies →
I can assure you that Google will be giving them significant commercial incentives as an apology for this behind the scene
Railway say the incident is resolved but many are still down (returning 502): on our side, we had to manually trigger a redeploy to fix it but I believe it should have been triggered automatically by Railway and I can't understand how they can mark this as resolved while many are still down.
In total, down for >11 hours on our side.