May 19, 22:10 UTC - Our automated monitoring detected API health check failures and paged our on-calls, who started investigating the issue. May 19, 22:11 UTC - Dashboard returning 503 errors. Users unable to log in. May 19, 22:19 UTC - Root cause identified: Google Cloud Platform has suspended Railway's production account. May 19, 22:22 UTC - P0 ticket filed with Google Cloud. Railway's GCP account manager engaged directly. May 19, 22:29 UTC - Incident declared. May 19, 22:29 UTC - GCP account access restored. All compute instances remained stopped and persistent disks inaccessible.
That's external dependency monitoring working exactly as it should. Most teams only monitor their own infrastructure. When a cloud provider, payment gateway, or third-party API fails — your own dashboards show green while users see failures.
The lesson isn't specific to GCP — it's that monitoring what you depend on but don't control is just as important as monitoring what you own.
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.
It sounds exactly like what I have experienced in terms of Google quality over the decades.
They said they are already using Gemini 3.5 Pro internally.
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.
its a nicely design hobby, that somebody could make a good product out of, by following the same abstractions
Google has an extremely poor reputation. Why are you thinking differently to that?
That said, did OCI, being an Oracle division, have a culture worth destroying? On the other hand, I could see TK importing that culture into Google...
If I think about it you might be right though some of this comes from Google's disdain for its customers be it hardware/software/cloud. So it is kinda inherited. One of the main reasons most good cloud consultants ask their clients to stay away from GCP is because of their depreciation policy. Plus stuff like this has been common in GCP.
So TK brought it to fix it instead of fixing it has brought the toxic OCI culture too which in the end brings them down even more.
opinion my own, yada yada yada.
As a former GCP consultant, I can share that these sort of shut downs aren't random and it's usually due to the customer not being compliant - that breaks cloud compliance requirements for the big clouds, so automated systems flag it. Eg. Someone serving CP on their CDN, for instance.
The Railway incident report also doesn't directly address this at all other than:
May 19, 22:22 UTC - P0 ticket filed with Google Cloud. Railway's GCP account manager engaged directly.
So, I would actually like to know more (What did the account manager say exactly?) before I just simply jump onto the Google hate train because it's cool to do so.I doubt we'll ever know, especially if it makes Google look negligent (ie. not reaching out to the customer first before restricting their production account)
Whatever the account manager said didn't inspire confidence that this wouldn't happen again.
Finally, we are in planning to remove Google Cloud services from our data plane’s hot path, and keeping them only for secondary/failover.
Or..they couldn't remain compliant with one of the strictest cloud vendors' policies.
> Or..they couldn't remain compliant with one of the strictest cloud vendors' policies.
Which is it? They can comply or they can’t? Both sides can’t be true at the same time.
Being open minded is good but don’t keep it so open your brain leaks out.
If this was the case it would obviously be horrific. I did check to see, and I noticed that Railway is not listed as an ESP who sent any reports to NCMEC / CyberTipline in 2025, which seems like the wrong number for a hosting provider. Maybe they just have absurdly good customers.
https://www.missingkids.org/content/dam/missingkids/pdfs/202...
Google “quality”? We’re talking about the same company that has killed off dozens of useful apps? The company that’s made 6 different chat apps? The one who will kill user accounts with no recourse or person to call?
GCP literally had to spend the last 5 years trying to convince enterprises everywhere that they were nothing like Google proper. I’m not sure the last time you left Silicon Valley, but Google’s name across the test of the US was synonymous with flaky commercial products that might not exist a year from now.
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. Don't expect Google quality from the name. It's just like those old brands which now have cheap licensed products like Nokia (An exaggeration I know but not far from truth).
Not only that they are known to shut off their services randomly giving you like 6 months to migrate. They have lots of engineers not doing anything, so they put them on migrating internal users off those services, most of their clients don't. There was a brilliant article on this by an ex-GCP employee that I can't find right now.
Avoid GCP like plague if you are serious about your business.
Edit: Gemini (unironically) found the article on this, a very good read: https://steve-yegge.medium.com/dear-google-cloud-your-deprec...