Don&#x27;t presume to give them so much benefit of the doubt. Apparently Stripe are kind of jokers.<p>This incident report reminded me of the &#x27;Game Day Exercise&#x27; post from 2014:<p><a href="https:&#x2F;&#x2F;stripe.com&#x2F;blog&#x2F;game-day-exercises-at-stripe" rel="nofollow">https:&#x2F;&#x2F;stripe.com&#x2F;blog&#x2F;game-day-exercises-at-stripe</a><p>in which one robustness check that should be a continuous-integration kind of test, or at <i>least</i> a daily test of a normally working system, is such a big deal to them that they make a big &#x27;Game Day&#x27; about it, and serious problems result from this one simple test.<p><i>After</i> they have lots of paying customers, of course.<p>I know we are supposed to be positive and supportive on HN but this was a red flag that the entire department has no idea what an actual robust system looks like and were so far away from that, after having built a substantial amount of software, that expecting them to ever get there may be wishful thinking.<p>So I am completely unsurprised that they are having this kind of problem. The post-mortem reveals problems that could only occur in systems designed by people who do not think carefully about robustness ... which is consistent with the 2014 post. It kind of shocks me that anyone lets Stripe have anything to do with money.