This could’ve happened anywhere, indeed.
We don’t yet do post-mortems. We’re too small and don’t have enough time on our hands. Not to diminish the impact of this issue, but it only affected a single region and some IP ranges. We do want to do post-mortem analysis at some point, we’re hiring a lot more infrastructure and operations people to help us get there. We’re happy to do give you more details on a case-by-case basis though!
I’ve already logged a ticket (with a potential solution) to work on a way to detect this issue the next time it happens do we can deal with it automatically / swiftly.