Resolved after 6 hours 5 minutes, on July 19, 2016.
We have concluded that this morning's brief outage was caused by degraded performance of Amazon's Elastic Block Storage service. Amazon did not update their status page (http://status.aws.amazon.com/) to indicate that degraded performance occurred, but our logs indicate it was caused by Elastic Block Storage. We'll continue to monitor the situation.
Update timeline
- monitoring Jul 19, 2016, 10:31 AM UTC
At 5:36AM Eastern our primary load balancer failed to respond to network input/output. This prevented any traffic coming into ProcedureFlow. The problem automatically corrected itself within 2 minutes and ProcedureFlow was available again. We're investigating the root cause.
- resolved Jul 19, 2016, 04:37 PM UTC
We have concluded that this morning's brief outage was caused by degraded performance of Amazon's Elastic Block Storage service. Amazon did not update their status page (http://status.aws.amazon.com/) to indicate that degraded performance occurred, but our logs indicate it was caused by Elastic Block Storage. We'll continue to monitor the situation.
Your product runs on more than ProcedureFlow
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services