3 ms·

I thought this was posted a few days ago, and by my reading it didn't seem like it was GCP's "fault" in that the issue was GCP failed to stop a bogus configurat

• barkbyte 2y ago
  Their comments I’ve seen are vague enough that we’re all trying to read between the lines and infer what they means. Your reading makes sense, and maybe that’s it, but the specifics are important and I’ve seen other plausible speculation too. They really need to be clear about what happened if they don’t want to take a giant reputational hit from this. Nobody ever got fired for choosing AWS.
  • morkalork 2y ago
    The part where it's described as a misconfiguration (on the client's part?) but the head of GCP is apologizing makes it sound kind of like one of those "If you owe the bank $100 that's your problem. If you owe the bank $100 million, that's the bank's problem" situations.