Service Outage Apology

We want to apologize to all our customers affected by a recent AWS problem that led to our services being offline for 43 hours (January 4th – 6th). We want to assure our customers that this was not a hack or breach. The issue stemmed from an AWS algorithm firing a false positive on our account, resulting in a temporary suspension pending further investigation by the AWS team.

Even though we’ve worked collectively to address the problem, we understand that this outage has caused some inconvenience for our customers. For this reason, we send our sincerest regards and are deeply sorry. We understand the importance of uptime and the availability of our services. So, we’ve also double-downed on different approaches to ensure this does not happen again as we work closely with AWS Team.

To minimize the impact of such incidents in the future, we are actively working on diversifying our infrastructure and reducing our dependence on a single cloud provider. We will also be implementing further contingencies and failover measures to minimize the impact of such incidents on our customers.

We take full responsibility for this problem and would like you to know that your trust is important to us, and we take significant measures to ensure that your experience with us remains secure, seamless, and stress-free at all times. From implementing secure data storage protocols, installing state-of-the-art firewalls, deploying anti-malware solutions, and performing regular upgrades/ maintenance checks – your safety remains our topmost priority.

Once again, please accept our sincere apologies for any inconvenience caused due to this incident. If there’s anything else we can do for you to make up for it, feel free to get in touch with us directly. Thank you for understanding!

Thanks,
The Todo Cloud Team

Share This Post

Share on twitter
Share on linkedin
Share on facebook
Share on email

Subscribe To Our Newsletter

Get updates and learn from the best

More To Explore

Leave a Reply

Your email address will not be published. Required fields are marked *