3 ms·
There are a couple of lessons to be learned from this: * Make sure to have a plan B for all service providers that you use for critical services. * Make sure
by ahje 8y ago
There are a couple of lessons to be learned from this:
* Make sure to have a plan B for all service providers that you use for critical services.
* Make sure you have a secondary copy of critical data, and that you store it responsibly in case a provider does something.
That still doesn't excuse not informing the account holder, but given the short time that has passed, it is possible that task has ended up in someone's backlog.
- tgsovlerkhgsel 8y agoIf it ended up in someone's backlog, then MailChimp still screwed up because the "suspend account" button should automatically send a notification (even if it only said that more information will follow). I'd also add one item to your list: Proper monitoring (which is extremely difficult and time-consuming to set up). A plan B is useful if you know that you need to enact it. Here, the third party provider had silently caused an outage, possibly because they consider shadow bans more effective without considering that the same thing that makes them effective makes them extremely damaging when they're handed out incorrectly.
- ahje 8y agoGood point! Monitoring is also one of those critical things one should always have.