The issue is now resolved. We have identified the problem as a bad server in one of our blade Array. This server is now disabled and will be replaced later tonight. No downtime is required. Please accept our apologies for this inconvenience.
Posted Aug 30, 2016 - 09:50 PDT
We have identified the problem and applied a fix. we are monitoring the situation.
Posted Aug 30, 2016 - 09:40 PDT
We are looking into this, more updates will be posted soon