On Sunday morning, Stackable will be performing maintenance in its data center which will affect 13 customers. If you are one of the customers expected to be affected, you have already been notified by email.
We plan to begin this work at Sunday, Jul 3, 9:00 AM MST and expect that all work will be concluded by 9:30 AM (30 minutes).
Stackable does offer high-availability options to ensure that even scheduled downtimes like these won’t affect your site. Contact us by emailing sales@stackable.com or calling (877) 977-2253 to learn more.
If you have any questions at all, please don’t hesitate to let us know. We’re available during regular business hours (9 AM - 5 PM MST, Monday - Friday) via the Live Chat link on our website http://www.stackable.com or by emailing help@stackable.com.
As of 9:00 AM MST, we are unable to take support requests via phone or live chat. We are working to correct the issue.
In the interim, please direct all support requests to help@stackable.com and they will be handled promptly.
UPDATE: This issue was resolved at 9:41 AM MST.
Between 6:15 AM and 1:30 PM MST our back end storage file system experienced an usually high amount of lag causing some customers to experience slow page load times. Our systems administrators quickly identified the problem and worked as quickly as possible to resolve the issue. We are currently evaluating a variety of options to prevent this issue for occurring in the future.
We are deeply sorry for any inconvenience this may have caused and thank you for your patience.
Today between 1:35 PM and 1:45 PM MST, the core routers which handle all XMission and Stackable traffic to and from the Internet experienced an overload which caused sporadic traffic outages during this time period.
XMission has redundant routers with connectivity to several Internet backbone providers. Currently only one of these is IPv6 capable. During an attempt to bring the second router online with IPv6, it caused high CPU use and overload which caused processing all traffic to slow. As soon as the overload was noticed, the changes were undone.
This was a minor network change that was not expected to cause any problems. XMission will hold off conversion of this second router until they find a resolution as to why the routers overloaded. This change will be executed during off hours just to be certain. Both XMission and Stackable apologize for any inconvenience caused due to this outage.
A small number of VPS containers in our SLC1 datacenter were offline on April 30 from 8:30 PM MST - 9:50 PM MST and again on May 1 from 10:44 AM MST - 11:24 AM MST.
These issues have been identified and stem from problems we’ve had with our back end ZFS file system. A decision has been made to replace the Nexenta platform currently in use with a NetApp FAS2020 to serve as the storage facility for VPS containers. We’ve had perfect reliability with NetApps in the past and expect that trend to continue.
Despite the VPS products being in beta stage, we again apologize for any inconvenience this may have caused for the small number of affected customers. We will report further updates following the implementation of the NetApp solution. Thank you again for your patience.
11 VPS (beta) containers in our SLC1 datacenter were offline from 9:04PM MST to 10:45PM MST, affecting a total of 8 customers.
This outage was caused by the same issue which affected the same VPS containers on April 26, 2011.
We are deeply sorry for any inconvenience this may have caused. Our engineers continue to investigate the root cause of this problem and are working to develop a solution
A small number of VPS containers in our SLC1 datacenter were offline from 11:03 AM MST to 11:25 MST.
Without warning, a storage server which provides disk access for VPS containers suddenly flipped one of its filesystems into read-only mode. Not only did this prevent containers from being able to write files, it also prevented containers from being started, stopped or restarted.
The hardware which hosts those containers was quickly brought down in order to attempt to re-mount the filesystem. After the filesystem was remounted RW, containers were restarted and all services were restored by 11:25 AM MST.
We apologize sincerely for this unexpected outage. Engineers continue to investigate the root cause and will move containers storage away from the affected storage server if a systemic issue is discovered.
For a short period of time over the weekend, customers were not able to access their billing page through the Stackable Control panel. This issue was first brought to our attention on Sunday, April 17, at 1:02 PM MST and was resolved by 2:38 PM MST.
We believe this issue was caused by an upgrade to our third party billing system.
We apologize for any inconvenience this may have cause.
The Stackable Control Panel is not functioning correctly as of 9:00 AM MST, Monday April 11th.
Users may experience high wait times and may be unable to upgrade/downgrade or purchase new containers during this period.
We believe this issue to have been caused by an upgrade to our 3rd party billing software which was undertaken by our vendor a day earlier than was scheduled. We are working with the vendor to resolve the issue.
At approximately 5:20 AM MST disc in a server in our SLC1 datacenter crashed, bringing a critical machine offline. A number of customer containers were affected and all provisioning capabilities to existing containers were brought offline.
Systems engineers were immediately alerted to the problem and were on-site shortly after. The machine was brought fully back online by 7:11 AM MST and as of 7:24 AM MST, most customer containers are back online and provisioning services for all customer containers are being restored.
Obviously, it’s not normal for one of our servers to be brought down by a single disc failure. The server in question was configured with a RAID10 array and should have stayed up despite its condition. We are working with the vendor to determine why the disc array did not act as it was designed to.
As always, we apologize for any interruption in service. We take these events very seriously and will post additional updates as they become available.