As the sysops manager and ultimately the person at Unbounce responsible for our service uptime, I'd like to start off by apologizing for any problems this outage caused. Our whole team is working hard to try and prevent this from happening again in the future.
Between 12:08 AM and 3:40 AM PDT, Monday August 10th, and again between 12:03 PM and 12:19 PM PDT the same day, Amazon AWS (our hosting provider) experienced serious service interruptions in their Simple Storage Service (S3), which Unbounce uses for storage for many of our services (both internal and external).
Although no services completely went offline, publishing pages was severely impacted, often delayed for quite some time, or failing to publish at all.
In a small percentage of cases (about 0.05%) published pages on unbouncepages.com as well as custom domains were serving "404 - Not Found" errors.
All other backend services were functioning normally. The page builder itself was up during the outage (with exception of page publishing). Visitor stats, form submissions, and click conversions were also unaffected.
The problem was due to a service outside of our direct control. We were only able to monitor the situation and update our status page during the outage.
We don't have any immediate changes planned. We still believe the choices we've made and systems we have in place are quite stable and reliable. Making reactive changes to an outage like this may cause more harm than good.
From a long-term perspective, we are always looking at ways to improve the reliability and uptime for all our systems. We are currently investigating the possibility of having redundant storage locations for published pages, giving us the ability to turn off one location if it is behaving badly.
If you have questions or concerns, feel free to reach out. My email is mthorpe@unbounce.com; however, I'd ask that you email support@unbounce.com and address it to me so that the rest of the team can stay in the loop.
Sincerely, Mike Thorpe Technical Operations Manager