Birbla

Shouldn't Google need to give a public statement about Railway incident?

Shouldn't Google need to give a public statement about Railway incident?

176 pointsby srameshc106 comments

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • No warning, no email, nothing. Just you find out your business is down the same way your users do. Google needs to explain this.
    by SamiahAman
  • Google really should publish a flow diagram for how they decide to turn off someone's business.
    by nickdothutton
  • GCP is basically just a toy. If you're hosting something important there you should probably not do that. It works as a Plan B, but by no means should Google be your Plan A.

    I don't know what happened in this case, there's a chance it wasn't Google's fault but it doesn't matter, Google already lost all benefit of the doubt long ago.

    by zarzavat
  • Would you want your vendors publicly disclosing potentially private reasons for an outage?
    by ceejayoz
  • I really don't see how they can. The business and usage details of their clients are confidential. We have their word that ToS where violated, I don't really think they should say more. This needs to go to arbitration.
    by ZiiS
  • I think so. I'm a GCP user and I'm afraid of hosting workloads there now. I've heard too many nightmare stories, and I thought Google would be proper and thus not be infested with these kind of problems that cheaper providers are known for.

    Maybe AWS is the only player in town now? I don't know. Google doesn't instill confidence with these incidents, same with those cases of insurmountable bills caused by simple mistakes where there should be a way for smaller customers to cap usage.

    by r_lee
  • It's an especially awkward situation because Railway is a competitor of Google Cloud, with many third parties involved. So, I just think it will take them a little more time to figure out how to message things.

    To me, what it sounds like is that a Google Cloud system identified Railway as a misbehaving customer. Spam, hackers, that sort of thing. Often this happens for "platform as a service" companies, because Railway themselves probably do host some spammers and hackers, and they have their own systems for dealing with it.

    So, it's quite possible that according to the Google team, Railway violated the terms of something or other, and according to the Railway team, they did not, and now everyone has to argue about it.

    But who knows, this is just me guessing based on some experience running a PaaS that itself was running on top of AWS.

    by lacker
  • Related ongoing thread:

    Incident Report: May 19, 2026 – GCP Account Suspension - https://news.ycombinator.com/item?id=48204770 - May 2026 (144 comments)

    Previously:

    Incident Report: Railway Blocked by Google Cloud [resolved] - https://news.ycombinator.com/item?id=48201484 - May 2026 (344 comments)

    by dang

Explore Birbla archives