Server Status
Affecting Server - Solar
- 30/06/2015 06:13 - 01/11/2016 19:59
- Last Updated 30/06/2015 06:14
We are having a server problem on the node you are currently residing. Earlier today we are receiving a notification indicating there is a RAID problem. A repair attempt was made by our engineer, however it seems that one of the harddisk are failing. In light of this event, we are currently scheduling your data to be migrated to a new node.
Please expect an update from us in a few hours.
Affecting Server - r1
- 20/12/2012 15:56 - 30/12/2012 15:13
- Last Updated 19/12/2012 15:57
On December 20th, 2012 at 3 AM ET [GMT-5] we will be powering down the Icarus server to replace the raid controller battery back-up unit. We expect the maintenance to take no more than 15 minutes and expect no complications from this scheduled maintenance. The process will simply be a server power down (graceful), a part swap, and then powering the server back up.
Affecting Server - r3
- 19/06/2012 16:35 - 19/06/2012 16:49
- Last Updated 19/06/2012 16:36
We are aware of a networking issue on our Fresco server and our networking engineers are working on it.
Jack Curtis
Affecting Server - Server37
- 03/05/2012 22:00 - 03/05/2012 22:30
- Last Updated 09/05/2012 20:28
Our goal is to provide you with the most dependable and flexible hosting infrastructure in the industry. To ensure the most reliable service, we are planning a maintenance window which may temporarily affect your services. Improvements made in a controllable and pro-active fashion will significantly reduce the risk of unplanned incidents.
As such, we would like to advise you of scheduled maintenance on the following servers:
Altezza Fresco
On May 3, 2012, from 22:00 til 0600 CST ( 0300 - 1100 UTC). Please be aware, that the actual downtime for this upgrade will range from 10 - 30 minutes.
We will be upgrading this server to new version (CentOS 6.x) and we will also be doing an architecture change from 32bit to 64bit. This will allow higher memory usage by different services on the server itself, and will provide a more stable hosting platform for your sites and your clients.
Thank you for your understanding and cooperation. If you have any questions/concerns please submit a ticket ticket and we'll get back to you right away.
Affecting Server - r3
- 03/05/2012 22:00 - 03/05/2012 22:30
- Last Updated 09/05/2012 20:28
Our goal is to provide you with the most dependable and flexible hosting infrastructure in the industry. To ensure the most reliable service, we are planning a maintenance window which may temporarily affect your services. Improvements made in a controllable and pro-active fashion will significantly reduce the risk of unplanned incidents.
As such, we would like to advise you of scheduled maintenance on the following servers:
Altezza Fresco
On May 3, 2012, from 22:00 til 0600 CST ( 0300 - 1100 UTC). Please be aware, that the actual downtime for this upgrade will range from 10 - 30 minutes.
We will be upgrading this server to new version (CentOS 6.x) and we will also be doing an architecture change from 32bit to 64bit. This will allow higher memory usage by different services on the server itself, and will provide a more stable hosting platform for your sites and your clients.
Thank you for your understanding and cooperation. If you have any questions/concerns please submit a ticket ticket and we'll get back to you right away.
Affecting Server - r3
- 10/11/2010 19:10 - 10/11/2010 22:10
- Last Updated 04/12/2011 19:12
We are always striving to give our customers the absolute best service possible and as a result we're always looking for ways to improve the quality of our services. In the world of web hosting, hardware that was top notch a year ago will not be the best today. Many companies are fine with this but we prefer to give you the best experience at all times and upgrading servers to the latest technology is one way we achieve this.
After much consideration we've decided to transfer accounts on our Fresco server to new hardware. This transfer is going to be a very nice performance upgrade as the new server will be running Dual Quad Core Xeon 5620 Processors which have Hyper-Threading offering a total of 16 Logical cores per server with a minimum of 12 GB of system ram.
The transfers will take place somewhere between November 18th and November 25th from 9 PM EST to 7 AM EST (off-peak times). The wide time frame is to give you an idea of when the transfer is going to take place, however when we know the exact date we will send another notification email. We're very good at transferring accounts so you should not notice any discernible downtime. Once the transfer is complete all of the current login URLs and name servers will remain the same meaning no changes are required on your part.
If you have any questions or concerns about this transfer please leave a comment or send an email to support at zomex.com and we'll be happy to assist you.
Affecting Server - r3
- 20/10/2011 12:06
- Last Updated 24/10/2011 04:05
We have been having some intermittent issues with the Fresco server which we believe to be related to the system memory (RAM). Due to the potential for damage we're scheduling an emergency maintenance window to replace the RAM (and also, upgrading the ram in the process) within the hour. The estimated downtime for this process is only 5 to 10 minutes and we do apologize for the short notice.
We do believe that this short maintenance window will improve the stability of the server and help to make sure that your data does not become damaged.
If you have any questions at all, let us know.
Affecting Server - r3
- 20/06/2011 09:38 - 21/06/2011 09:34
- Last Updated 20/06/2011 09:41
The fresco server is currently under a DDoS attack which is sending about 110,000 attack packets per second. We're working on mitigating this attack at this time.
While shifting accounts off of the IP under attack the server crashed and upon reboot is requiring a file system check. We have not yet determined what caused the crash resulting in the file system check, however, there is no safe way for us to skip the file system check.
Once the check is completed we will reboot the server and then see where we stand, the check could take anywhere from 45 minutes to 6 hours (there is no ETA provided by the file system checker) and will vary greatly depending on how damaged (or not) the file system is.
Thank you for your patience during this matter. I will post an update as soon as this issue has been resolved.
