A Note of Apology For Yesterday’s Outage

Here's a note we've just sent to all our customers:

We wanted to reach out and apologize for any issues caused by Ziggeo’s interrupted service yesterday -- and to let you know exactly what happened.   Here's the full story: On February 28th (yesterday), Ziggeo experienced an outage from 6pm - 9pm UTC. That meant videos using Ziggeo’s service could neither be recorded nor played during that time -- and data from dashboards couldn't be accessed. No data was lost, and our service fully recovered around 9pm. We use storage infrastructure from Amazon Web Services (AWS) called S3 that is supposed to be stable to four nines, meaning only 52 minutes per year of outage. But yesterday, AWS experienced a full and extended outage of S3 which in turn impaired a variety of dependent AWS services, including the AWS console and AWS Status Board itself, which made it particularly difficult to react to the outage. Other companies that were affected include Bitbucket, HipChat, Buffer, Business Insider, Chef, Citrix, Clarifai, Codecademy, Coursera, Docker, Elastic, Expedia, Flipboard, Giphy, GitHub, GitLab, Heroku, IFTTT, Imgur, Ionic, Kickstarter, Mailchimp, Medium, New Relic, PagerDuty, Quora, Slack, StatusPage, Travis CI, Trello, Twilio, Unbounce, The Verge, and many others. Zendesk, our customer support system, was also affected which made it impossible to receive tickets during that time. We have plans for mitigating against outages of entire AWS services and regions like this in the future. If you have any questions or concerns, please reach out to customer service at support@ziggeo.com Sincerely, Oliver and Susan Founders, Ziggeo