Time: Aug. 8, 2016, 6:09 p.m.

Status: Resolved

Update: Zoey Engineers have restored connectivity to all affected sites. We are monitoring the environment closely to prevent any further interruptions.

Time: Aug. 8, 2016, 5 p.m.

Status: Identified

Update: Zoey Engineering has identified a problem with a physical compute node which has resulted in a partial outage. Currently a very small number of sites are unavailable. We are working to restore connectivity to these sites ASAP.

Time: July 25, 2016, 5:59 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 25, 2016, 5:05 a.m.

Status: Monitoring

Update: At this time we are continuing to monitor Stack 1 sites - all should be available. If you are still experiencing issues please open a ticket with support. We will post more information shortly.

Time: July 25, 2016, 3:15 a.m.

Status: Identified

Update: We are now in the final process of finishing to turn on the sites affected on Stack 1. If you are still experiencing issues please open a ticket with support. We will post more information shortly.

Time: July 25, 2016, 1:22 a.m.

Status: Identified

Update: We are continuing the process of restoring connectivity to the affected sites on Stack 1. We see sites coming back online now. We will post more information shortly.

Time: July 24, 2016, 11:32 p.m.

Status: Identified

Update: We are continuing the process of restoring connectivity to the affected sites on Stack1. We will post more information shortly.

Time: July 24, 2016, 10:38 p.m.

Status: Identified

Update: We have identified the issue affecting storage with Stack 1 and are currently resolving the issue. We have identified this outage affects <0.5% of customers. We will post more information shortly.

Time: July 24, 2016, 10:12 p.m.

Status: Investigating

Update: We are currently investigating some abnormal alerts with storage with regards to Stack 1. We will post more information shortly.

Time: July 5, 2016, 4 p.m.

Status: Resolved

Update: Node2 is now fully restored. Our Engineers are monitoring the servers to ensure connectivity is maintained. The root cause of this incident appears to be one of the three control (Node 1/2/3) clusters failed at around 8am ET on July 5, 2016 for, at this time, unknown reasons. Zoey has multiple computing clusters which we call "Stacks". Each Stack is controlled by three control nodes that provide critical functionality, such as network routing, to the underlying computing nodes in the cluster. While a single failure of a control cluster should not have caused downtime it appears to have been the case. Our Engineering team is currently in the process of rebuilding Stack 1 to conform to our newest architecture thereby resolving this type of problem in the future. Our expected rebuild of Stack 1 is by the end of August 2016 and should have no impact to our customers. We thank you for your patience during this incident and apologize for the frustration this caused.

Time: July 5, 2016, 3:11 p.m.

Status: Monitoring

Update: We continue to troubleshoot the stability of Node 2. No further updates at this time.

Time: July 5, 2016, 2:29 p.m.

Status: Monitoring

Update: We have identified the core routing issue for Node2 and are now resolving it. Thank you for your patience.

Time: July 5, 2016, 1:36 p.m.

Status: Resolved

Update: Our Engineers have been resolving the issues with Node2 and at this time appear to be partially resolved. We are continuing further monitoring to ensure stability of the impacted systems. We apologize for any problems this has caused.

Time: July 5, 2016, 12:15 p.m.

Status: Investigating

Update: We are receiving alerts of a down notification for one of the computing nodes in computing cluster 1. Service may be disrupted for some sites. We will be providing updates as more information becomes known.

Time: May 20, 2016, 8 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: May 20, 2016, 8 p.m.

Status: Investigating

Update: Our team has completed the restoration of all design center visual layouts. If you are experiencing any issues in what is being displayed please open a support ticket. The root cause was an incorrect matching of the revision number in the database to what was shown on the front end. Our fix has essentially restored this incorrect matching and your store should now display the correct content. Due to the nature of this incident, no data was ever at risk of being lost so long as it was properly published previously. We apologize for this inconvenience and if you have any further questions please create a support ticket.

Time: May 20, 2016, 7:17 p.m.

Status: Investigating

Update: Our team has begun rolling out the fix on a few stores and confirming it is working. Should tests prove to be successful we will roll out a patch to everyone. We will automatically determine whether or not your store needs to be corrected based on the internal tests the automated repairs are running.

Time: May 20, 2016, 6:34 p.m.

Status: Investigating

Update: Our team is finalizing the process of rolling out the fixes to stores. We expect for things to be restored shortly. If you are seeing incorrect information on your design center please open a ticket with support so that we may add your store to our global list to resolve.

Time: May 20, 2016, 4:55 p.m.

Status: Investigating

Update: Our team has identified all stores with this issue and will now begin rolling a fix to each one of them. Further updates will be available once we start this process.

Time: May 20, 2016, 2:50 p.m.

Status: Investigating

Update: Our team is continuing to work on a fix for the affected customers. At this time we believe less than 2% of customers are affected. If you are seeing incorrect information on your design center please open a ticket with support so that we may add your store to our global list to resolve.

Time: May 20, 2016, 1:25 p.m.

Status: Investigating

Update: Our team has identified the root cause of the issue and is working on a resolution. Further updates will be provided as they become available.

Time: May 20, 2016, 12:36 p.m.

Status: Investigating

Update: Our team continues to investigate this issue. No further updates are available at this time.

Time: May 20, 2016, 11:55 a.m.

Status: Investigating

Update: We are currently investigating an issue where some stores are displaying older versions of their design. This is impacting an extremely small subset of users but our team is investigating thoroughly. More updates will be provided as soon as we have additional information.