Anyone know how a service that requires an account and API keys can suffer from a DDoS attack impacting their API?
Does that mean their API servicing infrastructure is the same as their public front end? Or that they're just unwilling to stop new account sign ups at the expense of existing users?
This whole thing is crazy. I get it that it isn't their fault that they are being attacked... what they can control is their communications with their customers and be transparent with their issues and fixes. They're being vague, and that's the reason I just configured a competitor's SMTP relay account. I can forgive the outage, I can't forgive the poor communications... that's a choice.
2 comments
[ 1.3 ms ] story [ 16.7 ms ] threadDoes that mean their API servicing infrastructure is the same as their public front end? Or that they're just unwilling to stop new account sign ups at the expense of existing users?