Current Time: 15:26:04 EST
 

Windows Shared Hosting Outage – Resolved

Posted In: Outage — Oct 20th, 2014 at 11:49 pm EST by IX: Alan M.

Incident Description:

Our system administrators have identified a large number of Windows servers which are experiencing issues. Our administrators are looking into this issue now to attempt to get this resolved as soon as possible.

Here is a list of the affected servers:

Affected Server Current status
iis1001 UP
iis1002cf UP
iis1003 UP
iis1004 UP
iis1005 UP
iis1006 UP
iis1007 UP
iis1008 UP
iis1009 UP
iis1010 UP
iis1011 UP
iis1012 UP
iis1013 UP
iis1014 UP
iis1015 UP
iis1016 UP
iis1017 UP
iis1018 UP
iis1019 UP
iis1020 UP
iis1021 UP
iis1022 UP
iis1023 UP
iis1024 UP
iis1025 UP
iis1026 UP
iis1027 UP
iis1028 UP
iis1029 UP
iis12 UP
iis132 UP
iis133 UP
iis134 UP
iis138 UP
iis139 UP
iis140 UP
iis300 UP
iis301 UP
iis302cf UP
iis303 UP
iis304 UP
iis305 UP
iis306 UP
iis307 UP
iis309 UP
iis310 UP
iis311 UP
iis312 UP
iis313 UP
iis314 UP
iis315cf UP
iis316 UP
iis317 UP
iis318 UP
iis319 UP
iis323 UP
iis324 UP
iis325 UP
iis400 UP
iis401cf UP
iis403 UP
iis404 UP
iis405 UP
iis406 UP
iis407 UP
iis408 UP
iis409 UP
iis410 UP
iis411 UP
iis414 UP
iis415 UP
iis5 UP
iis500cf UP
iis501 UP
iis502 UP
iis503 UP
iis504 UP
iis505 UP
iis506 UP
iis507 UP
iis508 UP
iis509 UP
iis510 UP
iis511 UP
iis512 UP
iis513CF UP
iis514 UP
iis515 UP
iis516 UP
iis517 UP
iis518cf UP
iis519 UP
iis520 UP
iis521 UP
iis522 UP
iis523 UP
iis524 UP
iis525 UP
iis526 UP
iis527 UP
iis601 UP
iis602 UP
iisn101 UP
iisn102 UP
iisn103 UP
iisn104 UP
iisn105 UP
iisn201 UP
iisn202 UP
iisn203 UP
iisn204 UP
iisn205 UP
iisn206 UP
iisn301 UP
iisn302 UP
iisn303 UP
iisn304 UP
iisn305 UP
iisn306 UP
iisn307 UP
iisn308 UP
iisn309 UP
iisn310 UP
iisn311 UP
iisn401 Up
iisn402 Up
iisn403 Up
iisn404 Up
iisn405 Up
iisn406 Up
iisn407 Up
iisn408 Up
iisn409 Up
iisn410 Up
iisn411 Up
iisn412 Up
iisn413 Up
mssql1001 UP
mssql1002 UP
mssql1003 up
mssql1004 up
mssql1005 up
mssql1006 up
mssql1007 up
mssql20 up
mssql21 up
mssql22 up
mssql23 up
mssql24 up
mssql300 Up
mssql301 Up
mssql302 Up
mssql303 Up
mssql304 Up
mssql305 Up
mssql400 Up
mssql401 Up
mssql402 Up
mssql403 Up
mssql500 Up
mssql501 Up
mssql502 Up
mssql503 Up
mssql504 Up
mssql505 Up
mssql506 Up
mssql507 Up

 

Which Customers are Impacted?

All customers on the listed servers.

How are Customers Impacted?

Many customer sites will be slow or inaccessible.  Customer control panels may inaccessible as well.

How often will we be updated?

As information becomes available

Time to Resolution (ETA)

At current pace we expect all servers to be online by 8 AM EST.

Incident Updates

  • 2014/10/21 01:00 AM EDT  - Our administrators have compiled detailed logs from all affected machines and are currently working with our hypervisor vendor to determine the cause of the issue.
  • 2014/10/21 01:40 AM EDT - Our administrators have analyzed 77% of the logs with our hypervisor vendor.
  • 2014/10/21 02:00 AM EDT - We have applied patches recommended by our hypervisor vendor but this has not resolved the issue.  We are continuing to work with the vendor’s engineers to resolve the issue.
  • 2014/10/21 03:43 AM EDT - We have implemented another set of changes provided by our vendor to patch the network drivers on each blade. We are currently in the process of testing these updates if they have resolved the issue by restarting 1 blade. We will have further details in 15 minutes.
  • 2014/10/21 04:06 AM EDT - 1 blade has been started and currently our administrators are working on bringing up each VM to see if the current update has resolved the issue.
  • 2014/10/21 04:25 AM EDT - Our administrators are working on bringing up all servers. We will be updating the list above as servers come up.
  • 2014/10/21 05:13 AM EDT - After working with the engineers from our hypervisor vendor, we have isolated specific network drivers that needed to be replaced on the hypervisor hosts.  In addition to this, we have also reduced the number of virtual network interfaces on each hypervisor host server in order to improve the performance and reliability of the network interfaces on the virtual servers affected by this outage.  Admins have also made some optimizations to the storage connection to improve reboot speed so that we can get these VMs back up as quickly as possible.
  • 2014/10/21 5:30 AM EDT - 38 of 167 UP. 126 Down
  • 2014/10/21 5:40 AM EDT - 45 of 167 UP. 118 Down
  • 2014/10/21 5:50 AM EDT - 56 of 167 UP. 104 Down
  • 2014/10/21 6:00 AM EDT - 72 of 167 UP. 90 Down
  • 2014/10/21 6:10 AM EDT - 88 of 167 UP. 75 Down
  • 2014/10/21 6:25 AM EDT - 104 of 167 UP. 57 Down
  • 2014/10/21 6:46 AM EDT - 131 of 167 UP. 36 Down.
  • 2014/10/21 6:58 AM EDT - 137 of 167 UP. 30 Down.
  • 2014/10/21 7:05 AM EDT - 148 of 167 UP. 19 Down.
  • 2014/10/21 7:15 AM EDT - 161 of 167 UP. 6 Down.
  • 2014/10/21 7:30 AM EDT - All servers except for iis1004 are back up and running.  iis1004 is currently in CHKDSK status.
  • 2014/10/21 7:42 AM EDT - All servers are back up and running.  Issue has been resolved.

Resolution Description

n/a

Phone Provider Issues – Resovled

Posted In: Outage — Oct 20th, 2014 at 3:14 pm EST by IX: Alan M.

Incident Description:

Our Phone Service Provider is currently recently sent us a service alert:

There is a major fiber cut with a Tier 1 Internet carrier that is affecting Internet connectivity in many areas of the United States. This is creating call quality issues for some of our customers. We are actively working to reroute traffic around the impacted carriers.”

This means that you may not be able to connect with us via phone for support. If you are having an issue that requires immediate attention please contact us via Live Chat Support, or Create a ticket.

SSL 3.0 Flaw Update

Posted In: Security Issues — Oct 17th, 2014 at 1:22 pm EST by IX: Kevin N.

Incident Description:

Earlier this week Google announced a flaw in the design of the SSL v3 protocol.

This flaw could result in a hacker gaining access to private information when sent over an encrypted connection using the SSL v3 protocol. As soon as they read the announcement, our System Administration team began working on a fix for our customers.

We have now disabled the vulnerable protocol on all of our shared hosting servers.

So, what does this mean for our customers? Your visitors are now safe when browsing your websites protected by an SSL certificate. Visitors using extremely old versions of web browsers, specifically IE6 and older and Opera 4 and older, will likely get errors when viewing any websites. Google estimates that this is less than 1% of all users on the internet. To give you an idea of how old these browsers are, the next version up that works correctly was released in 2006 for IE and 2000 for Opera.

So, the vast majority of visitors (over 99%) should not experience any issues as a result of the changes we’ve made.

If you have any questions or concerns regarding these changes please feel free to contact our support staff.

web1114 – Down – Resolved

Posted In: Outage — Oct 16th, 2014 at 1:21 pm EST by IX: Ryan D.

Incident Description:

Our administrators have identified errors with Web1114 that are causing the server to be unreachable. The system has been rebooted, and is currently in File System Check (fsck).  We will keep this post updated with further information as we receive it from our administrators.

Which Customers are Impacted?

All customers on web1114.

How are Customers Impacted?

Services will be unavailable.

How often will we be updated?

2 hours.

Time to Resolution (ETA)

2 hours.

Incident Updates

  • 2014/10/16 4:49PM EDT: FSCK is 77% done

Resolution Description

Server is up

PgSql4 – Down – Raid Rebuild – Resolved

Posted In: Outage — Oct 12th, 2014 at 7:05 pm EST by IX: Alan M.

Incident Description:

Our Administrators have found an issue where our server PgSql4 is inaccessible. We are working to get it back online as soon as possible.

Which Customers are Impacted?

All customers using PgSql4

How are Customers Impacted?

Sites may be inaccessible during this down time.

How often will we be updated?

As updates become available.

Time to Resolution (ETA)

N/A

Incident Updates

  • 2014/10/13 12:16 AM EDT - Our administrators are still working on repairing raid on this server. We do not have an ETA at this time.
  • 2014/10/13 04:45 AM EDT - Raid is currently rebuilding on this server. ETA for completion 3-4 hours
  • 2014/10/13 07:15 AM EDT - Raid rebuild currently is at 52%

Resolution Description

Our administrators were able to get the server back up and running in all functionality. Thank you for your patience.

Live Chat Maintenance – Sunday, October 12 – Resolved

Posted In: Maintenance — Oct 10th, 2014 at 9:38 pm EST by IX: John B.

Incident Description:

Our live chat system will be brought offline on Sunday, October 12 from 3am to 5am (Eastern Time) for maintenance.  Customers can still contact us during this time via phone call or ticket.

Which Customers are Impacted?

Any customer that tries to use our live chat system.

How are Customers Impacted?

Live chat will be down for the duration.

How often will we be updated?

2 hours

Time to Resolution (ETA)

2 hours (3am-5am ET)

Incident Updates

n/a

Resolution Description

Maintenance has completed.

Scheduled Maintenance on Control Panel and Support Infrastructure Databases – Completed

Posted In: Outage — Oct 10th, 2014 at 5:26 pm EST by IX: Brooke T.

Incident Description:

On Saturday October 18th from 2AM to 6AM EST, we will be performing a scheduled maintenance on databases supporting your account dashboard and our support infrastructure.

During maintenance, these databases will be migrated to newer and faster hardware to improve performance and reliability of these systems.  While we migrate and test these databases, you will not be able to log in to your account dashboard and livechat, ticket, and phone support will be unavailable.

Your websites and email will not be affected by this maintenance and will remain in service.

Which Customers are Impacted?

All customers

How are Customers Impacted?

You will not be able to login to your account dashboard and livechat, ticket, and phone support will be offline.

How often will we be updated?

This blog will be updated when the maintenance window is closed.

Time to Resolution (ETA)

The maintenance window will occur on Saturday October 18th from 2AM to 6AM EST

Incident Updates

  • 10/18/2014 02:12AM - Maintenance was initiated.

Resolution Description

As of 05:15AM, maintenance of our databases were successfully migrated to newer hardware. Testing has been completed and everything is working as normal.

iis522 – Down – Resolved

Posted In: Outage — Oct 07th, 2014 at 11:42 am EST by IX: Angela A.

Incident Description:

This server was part of the recent Windows Server Outage.  Unlike other servers involved in the outage, this server failed to bring up necessary network interfaces upon reboot and when admins attempt to reinstall them, the server throws errors.  Our System Administrators are investigating this issue and will have the server back up as soon as possible.

Which Customers are Impacted?

All customers on iis522.

How are Customers Impacted?

Sites are unavailable because the server is currently down.

How often will we be updated?

30 minutes

Time to Resolution (ETA)

~ 1 Hour

Incident Updates

  • 2014/10/07 12:31PM: The server is rebooting at this time.
  • 2014/10/07 1:21PM: The private interface is up. We are adding IPs to the public interface right now.

Resolution Description

The server is now online.

Windows Shared Hosting Outage – Resolved

Posted In: Outage — Oct 05th, 2014 at 6:47 pm EST by IX: John B.

Incident Description:

Our system administrators have identified a large number of Windows servers which are experiencing issues related to the tools software that is provided with the hypervisor running on the host system. These errors are resulting in servers experiencing degraded performance or locking up.

Multiple patches and hotfixes supplied by the vendor of this hypervisor have been applied but a permanent solution has yet to be found. We are working directly with our hypervisor vendor to identify the root cause of these errors and will provide more information as as it becomes available.

UPDATE: We will be re-installing the virtualization tools for each server. Until this is complete websites may load slowly. This process will require a restart of each server which will take approximately 5 minutes.

Here is a list of the affected servers:

iis1001 up
iis1002cf up
iis1003 up
iis1004 up
iis1005 up
iis1006 up
iis1007 up
iis1008 up
iis1009 up
iis1010 up
iis1011 up
iis1012 up
iis1013 up
iis1014 up
iis1015 up
iis1016 up
iis1017 up
iis1018 up
iis1019 up
iis1020 up
iis1021 up
iis1022 up
iis1023 up
iis1024 up
iis1025 up
iis1026 up
iis1027 up
iis1028 up
iis1029 up
iis12 up
iis132 up
iis133 up
iis134 up
iis138 up
iis139 up
iis140 up
iis300 up
iis301 up
iis302cf up
iis303 up
iis304 up
iis305 up
iis306 up
iis307 up
iis309 up
iis310 up
iis311 up
iis312 up
iis313 up
iis314 up
iis315cf up
iis316 up
iis317 up
iis318 up
iis319 up
iis323 up
iis324 up
iis325 up
iis400 up
iis401cf up
iis403 up
iis404 up
iis405 up
iis406 up
iis407 up
iis408 up
iis409 up
iis410 up
iis411 up
iis414 up
iis415 up
iis5 up
iis500cf up
iis501 up
iis502 up
iis503 up
iis504 up
iis505 up
iis506 up
iis507 up
iis508 up
iis509 up
iis510 up
iis511 up
iis512 up
iis513CF up
iis514 up
iis515 up
iis516 up
iis517 up
iis518cf up
iis519 up
iis520 up
iis521 up
iis522 up
iis523 up
iis524 up
iis525 up
iis526 up
iis527 up
iis601 up
iis602 up
iisn101 up
iisn102 up
iisn103 up
iisn104 up
iisn105 up
iisn201 up
iisn202 up
iisn203 up
iisn204 up
iisn205 up
iisn206 up
iisn301 up
iisn302 up
iisn303 up
iisn304 up
iisn305 up
iisn306 up
iisn307 up
iisn308 up
iisn309 up
iisn310 up
iisn311 up
iisn401 up
iisn402 up
iisn403 up
iisn404 up
iisn405 up
iisn406 up
iisn407 up
iisn408 up
iisn409 up
iisn410 up
iisn411 up
iisn412 up
iisn413 up
mssql1001 up
mssql1002 up
mssql1003 up
mssql1004 up
mssql1005 up
mssql1006 up
mssql1007 up
mssql20 up
mssql21 up
mssql22 up
mssql23 up
mssql24 up
mssql300 up
mssql301 up
mssql302 up
mssql303 up
mssql304 up
mssql305 up
mssql400 up
mssql401 up
mssql402 up
mssql403 up
mssql500 up
mssql501 up
mssql502 up
mssql503 up
mssql504 up
mssql505 up
mssql506 up
mssql507 up

Which Customers are Impacted?

All customers on the listed servers.

How are Customers Impacted?

Many customer sites will be slow or inaccessible..  Customer control panels may inaccessible as well.

How often will we be updated?

As information becomes available

Time to Resolution (ETA)

n/a

Incident Updates

  • 2014/10/05 9:00 PM EST - Our system admins are still investigating the root cause of the issue.  No ETA as of yet.
  • 2014/10/05 10:55 PM EST - The system admins are still working on a fix for this issue.  No ETA as of yet.
  • 2014/10/05 11:29 PM EST - Our Administrators are still attempting to determine the cause of the issue so they can address it accordingly. At this time, there is still no ETA.
  • 2014/10/06 12:20 AM EST - System Administrators are narrowing down the problem and testing by applying patches to the system's spare hypervisor in attempt to resolve the issue.  So far, we have attempted 4 patches to this server and have made some small improvements but have not yet corrected the overall problem.  The most recent of these patches were related to network configuration and  we are currently waiting on the server to complete config changes and reboot.
  • 2014/10/06 12:43 AM EST - Our administrators are attempting further network changes as the previous changes did not completely resolve the issue.
  • 2014/10/06 1:20 AM EST - The list of affected servers has been updated by our administrators as some servers that were not previously affected are now experiencing similar issues.
  • 2014/10/06 1:47 AM EST - Our administrators are continuing to work to resolve this issue.
  • 2014/10/06 2:22 AM EST - Our administrators have been able to bring a small number of these servers back online and are working to confirm that they are working properly.
  • 2014/10/06 3:11 AM EST - The servers that have been brought back online are currently functioning with some virtualization features disabled.  Our administrators have applied some changes to the hosts for this pool of servers to resolve these issues.
  • 2014/10/06 3:54 AM EST - One of the servers that were brought back online has been rebooted to restore the features that were not working.  This attempt was unsuccessful and the server is being rebooted with these features disabled again.  These features do not affect website functionality.
  • 2014/10/06 4:39 AM EST - Our administrators are continuing to perform tests using spare hosts to resolve this issue.  The server that was previously rebooted is now back online again with the virtualization features disabled.
  • 2014/10/06 5:53 AM EST - The servers that were brought back online have started experiencing issues again so our administrators are continuing to work toward a solution to this issue.
  • 2014/10/06 6:25 AM EST - Our administrators are now bringing the affected servers online with some advanced virtualization tools disabled which will allow websites to function normally while they continue to work on a permanent solution to this issue.
  • 2014/10/06 9:15 AM EST - Our administrators are working directly with the vendor of our hypervisor to get to the root of this issue as all possible documented solutions have been exhausted.  We are currently attempting to bring as many of these servers online as possible with these tools disabled.  This should allow websites and databases to function correctly but may have an impact on server performance.
  • 2014/10/06 10:22 AM EST - Our administrators have narrowed down a specific update version of the server OS that appears to be conflicting with the version of hypervisor tools installed on the server.  In some cases this conflict causes servers to slowdown while in others it results in the server freezing.  Identifying this conflict allows us to further focus on servers that will have the greatest impact.
  • 2014/10/06 10:55 AM EST - The affected servers list has been updated to reflect the current status of each affected server and will be updated as the status of servers change.
  • 2014/10/06 12:15 AM EST - The process of bringing the affected servers back online is taking some time.  This is because our administrators are uninstalling the conflicting hypervisor tool software and reboot the server (vm).  Since these are virtual machines, this software controls the network adapter for the server, which means that the virtual adapter must be recreated and all associated IP addresses added back to the server manually.  Our entire system administration team is working very methodically to prevent errors, but also as quickly as possible to ensure servers come up as soon as possible.  There are 168 servers that need this process to be performed and our administrators anticipate that this process could take up to 15 hours. This means that servers will be coming on-line as they are completed, with new servers coming online throughout this period.  All servers are expected to be up and running by 2014/10/07 2:45 AM EST.  Our System Administrators are working with the hypervisor tool vendor to try to speed this process up and we will keep you informed of any new developments.
  • 2014/10/06 12:40 PM EST - 41 of 168 servers have successfully been brought back online.
  • 2014/10/06 1:35 PM EST - 44 of 168 servers have successfully been brought back online.
  • 2014/10/06 2:55 PM EST - 47 of 168 servers have successfully been brought back online.
  • 2014/10/06 3:55 PM EST - 49 of 168 servers have successfully been brought back online.
  • 2014/10/06 4:55 PM EST - 51 of 168 servers have successfully been brought back online.
  • 2014/10/06 5:45 PM EST - 54 of 168 servers have successfully been brought back online.
  • 2014/10/06 6:46 PM EST - 59 of 168 servers have successfully been brought back online.
  • 2014/10/06 7:46 PM EST - 62 of 168 servers have successfully been brought back online.
  • 2014/10/06 8:46 PM EST - 65 of 168 servers have successfully been brought back online.
  • 2014/10/06 9:55 PM EST - 79 of 168 servers have successfully been brought back online.
  • 2014/10/06 10:06 PM EST -  81 of 168 servers have successfully been brought back online.
  • 2014/10/06 10:40 PM EST -  90 of 168 servers have successfully been brought back online.
  • 2014/10/06 11:06 PM EST  -  We are continuing to evaluate the pace that we are bringing these servers back online.  While we have increased the pace that we are bringing servers back online over the last few hours, the estimate for having all servers back online has been changed to 2014/10/07 8:00 AM EST.
  • 2014/10/06 11:13 PM EST -  94 of 168 servers have successfully been brought back online.
  • 2014/10/07 12:16 AM EST -  99 of 168 servers have successfully been brought back online.
  • 2014/10/07 01:08 AM EST -  118 of 168 servers have successfully been brought back online.
  • 2014/10/07 01:30 AM EST - The engineers from our hypervisor vendor have resolved the issue that has caused these servers to lock up and our administrators are now bringing servers back online with the virtualization tools running.
  • 2014/10/07 02:08 AM EST -  121 of 168 servers have successfully been brought back online.
  • 2014/10/07 04:50 AM EST - Our administrators are still working on getting servers back up with virtualization tools running. Almost all servers are up and running at this time with just a few remaining.
  • 2014/10/07 05:10 AM EST - At this time our administrators are installing the virtualization software to the servers. There will be times where the server is unavailable as this requires the server to be restarted.
  • 2014/10/07 08:25 AM EST - All servers are up at this time except IIS522 which is experiencing issues with network drivers. Some servers may still experience minor performance issues until our administrators complete the process of reinstalling the virtualization tools on the servers that were brought back up without them.

Resolution Description

All servers are up

CP 9 – 14 System Maintenance – Resolved

Posted In: Maintenance — Sep 30th, 2014 at 3:12 am EST by IX: Antonio S.

Incident Description:

Due to the possibility of degraded communication between virtual machines and the storage network, our system administrators will be performing urgent system maintenance within the virtual environments that CP9 -CP14 servers reside on. Administrators are performing this maintenance with the utmost care to prevent downtime to any customer facing servers but some servers may require a reboot and file system check during this process.

We will be providing updates on a server by server basis as they go under maintenance and as maintenance is completed.

Please feel free to contact support via live chat or phone should there be any concerns or questions regarding the maintenance.

List of servers to be worked on by our administrators will be as follows:

WEB1001 – Maintenance Completed
MYSQL1009 – Maintenance Completed
WEB1007 – Maintenance Completed
MAIL1011 – Maintenance Completed
MYSQL1003 – Maintenance Completed
MYSQL1012 – Maintenance Completed
WEB1021 – Maintenance Completed

WEB1004 – Maintenance Completed
MAIL1013 – Maintenance Completed
MAIL1002 – Maintenance Completed
MAIL1009 – Maintenance Completed
WEB1011 – Maintenance Completed
MAIL1015 – Maintenance Completed
MAIL1001 – Maintenance Completed
MAIL1018 – Maintenance Completed

WEB1409 – Maintenance Completed
MYSQL1406 – Maintenance Completed
MYSQL1407 – Maintenance Completed
MYSQL1421 – Maintenance Completed
MAIL1405 – Maintenance Completed
WEB1420 – Maintenance Completed
MYSQL1409 – Maintenance Completed
WEB1416 – Maintenance Completed
MAIL1423 – Maintenance Completed
WEB1422 – Maintenance Completed
MYSQL1416 – Maintenance Completed

WEB1029 – Maintenance Completed
WEB1014 – Maintenance Completed
MYSQL1010 – Maintenance Completed
WEB1018 – Maintenance Completed
MAIL1012 – Maintenance Completed
MAIL1014 – Maintenance Completed
PGSQL1002 – Maintenance Completed

MYSQL1011 – Maintenance Completed
WEB1028 – Maintenance Completed
MAIL1016 – Maintenance Completed
MAIL1017 – Maintenance Completed
MYSQL1014 – Maintenance Completed
WEB1002 – Maintenance Completed
WEB1003 – Maintenance Completed

MAIL1313 – Maintenance Completed
MYSQL1310 – Maintenance Completed
WEB1309 – Maintenance Completed
MYSQL1306 – Maintenance Completed
MAIL1311 – Maintenance Completed
WEB1317 – Maintenance Completed
DB2.WEBMAIL – Maintenance Completed
WEB1308 – Maintenance Completed
MAIL1314 – Maintenance Completed
MAIL1305 – Maintenance Completed
WEB1326 – Maintenance Completed
MAIL1422 – Maintenance Completed
MAIL1417 – Maintenance Completed
MYSQL1428 – Maintenance Completed
MAIL1411 – Maintenance Completed
MAIL1408 – Maintenance Completed
WEB1432 – Maintenance Completed
MAIL1419 – Maintenance Completed
MAIL1424 – Maintenance Completed
WEB1415 – Maintenance Completed
WEB1402 – Maintenance Completed
MYSQL1413 – Maintenance Completed
MYSQL1424 – Maintenance Completed
MAIL1412 – Maintenance Completed
MAIL1403 – Maintenance Completed
WEB1401 – Maintenance Completed
MAIL1404 – Maintenance Completed

Which Customers are Impacted?

All customers on CP9 - CP14.

How are Customers Impacted?

There may be some slowness while the server is under maintenance.  A few servers may also require reboot during this maintenance.  If maintenance requires a server reboot, we expect a file system check to run and services will be unavailable until this completes.

How often will we be updated?

Servers will be added as they come under maintenance.

Time to Resolution (ETA)

N/A

Incident Updates

  • 2014/09/30 03:08:14 AM EST - These VMs were moved without downtime MAIL1313, MYSQL1310, WEB1309 ,MYSQL1306, MAIL1311 ,WEB1317WEBMAIL ,WEB1308 ,MAIL1314, MAIL1305, WEB1326,MAIL1422, MAIL1417, MYSQL1428 ,MAIL1411, MAIL1408, WEB1432,MAIL1419, MAIL1424 WEB1415,WEB1402, MYSQL1413, MYSQL1424,MAIL1412, MAIL1403, WEB1401,MAIL1404
  • 2014/09/30 03:08:14 AM EST - The next  set for maintenance is as follows: WEB1409, MYSQL1406, MYSQL1407, MYSQL1421, MAIL1405 WEB1420, MYSQL1409, WEB1416, MAIL1423,WEB1422, MYSQL1416
  • 2014/09/30 03:37 AM EST - These VMs were moved without downtime: MYSQL1011, WEB1028, MAIL1016, MAIL1017 MYSQL1014, WEB1002,WEB100
  • 2014/09/30 03:37 AM EST - The next  set for maintenance is as follows: WEB1029, WEB1014, MYSQL1010WEB1018, MAIL1012, MAIL1014,PGSQL100
  • 2014/09/30 04:05 AM EST - The  VMs  were moved with no downtime.
  • 2014/09/30 04:05 AM EST - The next  set for maintenance is as follows: WEB1004, MAIL1013, MAIL1002, MAIL1009,WEB1011, MAIL1015, MAIL1001,MAIL1018
  • 2014/09/30 05:05 AM EST - Previous VMs were successfully migrated. Blade was rebooted.
  • 2014/09/30 05:05 AM EST -  The next  set for maintenance is as follows: WEB1001, MYSQL1009, WEB1007, MAIL1011 MYSQL1003 MYSQL1012 WEB1021

Resolution Description

VMs were moved without downtime. Maintenance has been finished.

Web520 – Down – Resolved

Posted In: Outage — Sep 29th, 2014 at 5:59 pm EST by IX: Alan M.

Incident Description:

Our administrators have identified errors with Web520 and is causing the server to be unreachable. We are currently investigating the cause and will update once further information is obtained.

Which Customers are Impacted?

All customers on Web520

How are Customers Impacted?

All services on Web520 are unreachable

How often will we be updated?

N/A

Time to Resolution (ETA)

N/A

Incident Updates

N/A

Resolution Description

Web 520 is up and running now.

CP 9 – 14 System Maintenance – Resolved

Posted In: Maintenance — Sep 29th, 2014 at 2:08 am EST by IX: Kevin Mb.

Incident Description:

Our system administrators will be performing system maintenance for servers within CP9 – CP14. Administrators are performing this maintenance with the utmost care to prevent downtime to any customer, but some servers may require a reboot and file system check during this process.

We will be providing updates on a server by server basis as they go under maintenance and as maintenance is completed. Below is a list of the servers that will be receiving this maintenance:

WEB929 - Maintenance finished
WEB916 - Maintenance finished
WEB904 - Maintenance finished
WEB918 - Maintenance finished
mail-13 - Maintenance finished
MAIL914 - Maintenance finished
WEB933 - Maintenance finished
WEB1013 - Maintenance finished
MYSQL1006 - Maintenance finished
WEB1009 - Maintenance finished
MAIL1004 - Maintenance finished
MYSQL1008 - Maintenance finished
WEB1010 - Maintenance finished
WEB1025 - Maintenance finished
mail-22 - Maintenance finished
MYSQL1206 - Maintenance finished
MYSQL1218 - Maintenance finished
WEB410 - Maintenance finished
WEB1201 - Maintenance finished
WEB1228 - Maintenance finished
MAIL1208 - Maintenance finished
MYSQL1209 - Maintenance finished
MAIL1212 - Maintenance finished
WEB1213 - Maintenance finished
WEB1232 - Maintenance finished
MYSQL1215 - Maintenance finished
MAIL1215 - Maintenance finished
WEB1223 - Maintenance finished
WEB305 - Maintenance finished
MYSQL1302 - Maintenance finished
WEB1312 - Maintenance finished
WEB1301 - Maintenance finished
WEB1333 - Maintenance finished
WEB1330 - Maintenance finished
MAIL1315 - Maintenance finished
WEB1318 - Maintenance finished
WEB1310 - Maintenance finished
MAIL1319 - Maintenance finished
MAIL1420 - Maintenance finished
WEB1439 - Maintenance finished
WEB1413 - Maintenance finished
WEB1403 - Maintenance finished
WEB1426 - Maintenance finished
MAIL1402 - Maintenance finished
MYSQL1414 - Maintenance finished
WEB1406 - Maintenance finished
WEB1429 - Maintenance finished
WEB1433 - Maintenance finished
MYSQL1430 - Maintenance finished
MAIL1409 - Maintenance finished
WEB927 - Maintenance finished
mail-44 - Maintenance finished
MAIL912 - Maintenance finished
WEB908 - Maintenance finished
MAIL911 - Maintenance finished
WEB939 - Maintenance finished
WEB943 - Maintenance finished
MYSQL907 - Maintenance finished
MAIL908 - Maintenance finished
MAIL916 - Maintenance finished
WEB946 - Maintenance finished
WEB1024 - Maintenance finished
MYSQL1015 - Maintenance finished
MAIL1008 - Maintenance finished
MYSQL1017 - Maintenance finished
WEB1006 - Maintenance finished
MAIL1005 - Maintenance finished
MYSQL1016 - Maintenance finished
WEB1026 - Maintenance finished
MAIL1010 - Maintenance finished
MYSQL1005 - Maintenance finished
WEB1012  - Maintenance finished
MYSQL913 - Maintenance finished
WEB937 - Maintenance finished
mail-23  - Maintenance finished
WEB1030 - Maintenance finished
MAIL1006 - Maintenance finished
MYSQL1013  - Maintenance finished
WEB1019  - Maintenance finished
WEB1027 - Maintenance finished
MYSQL1001  - Maintenance finished
WEB1208  - Maintenance finished
WEB1212  - Maintenance finished
MYSQL1208 - Maintenance finished
MYSQL1205  - Maintenance finished
WEB1214  - Maintenance finished
WEB1229 - Maintenance finished
WEB1215  - Maintenance finished
MAIL1216  - Maintenance finished
MYSQL1207 - Maintenance finished
WEB12125  - Maintenance finished
MYSQL1201  - Maintenance finished
MAIL51 - Maintenance finished
WEB1202  - Maintenance finished
WEB1313  - Maintenance finished
WEB1305 - Maintenance finished
MAIL1304 - Maintenance finished
MAIL1318  - Maintenance finished
WEB1323 - Maintenance finished
WEB1336  - Maintenance finished
WEB1315  - Maintenance finished
MYSQL1303 - Maintenance finished
WEB1306  - Maintenance finished
WEB1304  - Maintenance finished
MAIL1421  - Maintenance finished
WEB1412  - Maintenance finished
MYSQL1403 - Maintenance finished
WEB1427  - Maintenance finished
MAIL1401  - Maintenance finished
WEB1421 - Maintenance finished
WEB1437  - Maintenance finished
WEB1425  - Maintenance finished
MYSQL1420 - Maintenance finished
MAIL1425  - Maintenance finished
MAIL1414  - Maintenance finished
MYSQL901 - Maintenance finished
WEB925  - Maintenance finished
MAIL917 - Maintenance finished
WEB913  - Maintenance finished
MYSQL918  - Maintenance finished
MAIL906 - Maintenance finished
MYSQL909  - Maintenance finished
MYSQL906  - Maintenance finished
WEB931 - Maintenance finished
WEB935  - Maintenance finished
MYSQL1004  - Maintenance finished
MAIL1003  - Maintenance finished
WEB1017 - Maintenance finished
WEB1016  - Maintenance finished
MAIL1007  - Maintenance finished
PGSQL1001 - Maintenance finished
WEB1015  - Maintenance finished
WEB1005  - Maintenance finished
WEB1238  - Maintenance finished
WEB1230  - Maintenance finished
WEB1206 - Maintenance finished
mail-42  - Maintenance finished
WEB1210  - Maintenance finished
WEB1221 - Maintenance finished
PGSQK1201  - Maintenance finished
WEB1219  - Maintenance finished
WEB1234 - Maintenance finished
MYSQL1202  - Maintenance finished
WEB1233  - Maintenance finished
mail-52 - Maintenance finished
MYSQL1203 - Maintenance finished
MAIL1302  - Maintenance finished
WEB1324  - Maintenance finished
MYSQL1308  - Maintenance finished
MAIL1309  - Maintenance finished
MAIL1320  - Maintenance finished
WEB1322 - Maintenance finished
MYSQL1304  - Maintenance finished
MYSQL1307  - Maintenance finished
WEB1334 - Maintenance finished
MAIL1307  - Maintenance finished
MYSQL1301  - Maintenance finished
MYSQL1404  - Maintenance finished
MYSQL1423  - Maintenance finished
MYSQL1415  - Maintenance finished
MYSQL1412  - Maintenance finished
WEB1436  - Maintenance finished
WEB1411 - Maintenance finished
MAIL1407  - Maintenance finished
WEB1423  - Maintenance finished
WEB1408 - Maintenance finished
WEB1430  - Maintenance finished
MAIL904 - Maintenance finished
WEB917  - Maintenance finished
WEB948 - Maintenance finished
WEB903  - Maintenance finished
WEB938  - Maintenance finished
WEB911 - Maintenance finished
MAIL903  - Maintenance finished
PGSQL902 - Maintenance finished
WEB945  - Maintenance finished
WEB941  - Maintenance finished
MAIL1217  - Maintenance finished
WEB1236  - Maintenance finished
MYSQL1210  - Maintenance finished
WEB1226  - Maintenance finished
WEB312  - Maintenance finished
WEB1204 - Maintenance finished
WEB1220  - Maintenance finished
MAIL37  - Maintenance finished
mail-11 -  Maintenance finished
MAIL1206  -  Maintenance finished
WEB1237  -  Maintenance finished
WEB1222 - Maintenance finished
mail-21  - Maintenance finished
MAIL1203  - Maintenance finished
MYSQL1419  - Maintenance finished
MYSQL1402  - Maintenance finished
MYSQL1410  -  Maintenance finished
WEB1414  - Maintenance finished
MAIL1418  - Maintenance finished
WEB1435 - Maintenance finished
WEB1410  - Maintenance finished
MYSQL1427  - Maintenance finished
WEB1405 - Maintenance finished
MAIL1406  - Maintenance finished
MYSQL1408  - Maintenance finished
MAIL1416 - Maintenance finished
MYSQL1426  - Maintenance finished
WEB1434 - Maintenance finished
PGSQL901 - Maintenance finished
MAIL910 - Maintenance finished
WEB924 - Maintenance finished
MYSQL910 - Maintenance finished
WEB923 - Maintenance finished
WEB928 - Maintenance finished
WEB932 - Maintenance finished
MYSQL915 - Maintenance finished
MAIL913 - Maintenance finished
WEB914 - Maintenance finished
WEB942 - Maintenance finished
MYSQL920 - Maintenance finished
WEB922 - Maintenance finished
WEB905 - Maintenance finished
WEB934 - Maintenance finished
mail-12 - Maintenance finished
MYSQL1212 - Maintenance finished
WEB1224 - Maintenance finished
MAIL1209 - Maintenance finished
WEB1231 - Maintenance finished
mail-31 - Maintenance finished
WEB1211 - Maintenance finished
WEB1235 - Maintenance finished
MYSQL1219 - Maintenance finished
WEB1205 - Maintenance finished
MYSQL1211 - Maintenance finished
MAIL1207 - Maintenance finished
MYSQL1204 - Maintenance finished
MAIL1201 - Maintenance finished
MYSQL1216 - Maintenance finished
WEB1424 - Maintenance finished
MYSQL1411 - Maintenance finished
WEB1431 - Maintenance finished
WEB1404 - Maintenance finished
WEB1428 - Maintenance finished
MYSQL1405 - Maintenance finished
MAIL1410 - Maintenance finished
MYSQL1401 - Maintenance finished
WEB1419 - Maintenance finished
MYSQL1422 - Maintenance finished
PGSQL1401 - Maintenance finished
MYSQL1429 - Maintenance finished

Which Customers are Impacted?

All customers on CP9 - CP14.

How are Customers Impacted?

There may be some slowness while the server is under maintenance.  A few servers may also require reboot during this maintenance.  If maintenance requires a server reboot, we expect a file system check to run and services will be unavailable until this completes.

How often will we be updated?

Servers will be added as they come under maintenance.

Time to Resolution (ETA)

N/A

Incident Updates

  • 2014/09/29 02:45:14 AM EST - These VMs were moved without downtime: WEB929, WEB916, WEB904, WEB918, mail-13, MAIL914, WEB933, WEB1013, MYSQL1006, WEB1009, MAIL1004, MYSQL1008, WEB1010, & WEB1025.
  • 2014/09/29  03:15:03 AM EST - Maintenance is complete on following servers: mail-22, MYSQL1206, MYSQL1218, WEB410, WEB1201, WEB1228, MAIL1208, MYSQL1209, MAIL1212, WEB1213, WEB1232, MYSQL1215, MAIL1215, WEB1223, WEB305, MYSQL1302, WEB1312, WEB1301, WEB1333, WEB1330 , MAIL1315, WEB1318, WEB1310, MAIL1319, MAIL1420, WEB1439, WEB1413, WEB1403, WEB1426, MAIL1402, MYSQL1414, WEB1406, WEB1429, WEB1433, MYSQL1430, and MAIL1409. No down time experienced.
  • 2014/09/29 4:00AM EST - Maintenance is complete on the following servers: WEB927, mail-44, MAIL912, WEB908, MAIL911, WEB939, WEB943, MYSQL907, MAIL908, MAIL916, WEB946, WEB1024, MYSQL1015, MAIL1008, MYSQL1017, WEB1006, MAIL1005, MYSQL1016, WEB1026, MAIL1010, MYSQL1005, and WEB1012. No downtime.
  • 2014/09/29  04:43:26 AM EST - These VMs were moved without downtime: WEB1030, MAIL1006, MYSQL1013, WEB1019, WEB1027, MYSQL1001, WEB1208, WEB1212, MYSQL1208, MYSQL1205, WEB1214, WEB1229, WEB1215, MAIL1216, MYSQL1207, WEB12125, MYSQL1201, MAIL51, WEB1202, MYSQL913, WEB937, mail-23, WEB1313, WEB1305, MAIL1304, MAIL1318, WEB1323, WEB1336, WEB1315, MYSQL1303, WEB1306, WEB1304, MAIL1421, WEB1412, MYSQL1403, WEB1427, MAIL1401, WEB1421, WEB1437, WEB1425, MYSQL1420, MAIL1425, and MAIL1414.
  • 2014/09/29   07:06:18 AM EST - The following list of VMs have been moved without downtime: MYSQL901, WEB925, MAIL917, WEB913, MYSQL918, MAIL906, MYSQL909, MYSQL906, WEB931, WEB935, MYSQL1004, MAIL1003, WEB1017, WEB1016, MAIL1007, PGSQL1001, WEB1015, WEB1005, WEB1238, WEB1230, WEB1206, mail-42, WEB1210, WEB1221, PGSQL1201, WEB1219, WEB1234, MYSQL1202, WEB1233, mail-52, MYSQL1203, MAIL1302, WEB1324, MYSQL1308, MAIL1309, MAIL1320, WEB1322, MYSQL1304, MYSQL1307, WEB1334, MAIL1307, MYSQL1301, MYSQL1404, MYSQL1423, MYSQL1415, MYSQL1412, WEB1436, WEB1411, MAIL1407, WEB1423, WEB1408, and WEB1430.
  • 2014/09/29   07:20:19 AM EST - Maintenance for the following VMs has completed: MAIL1217, WEB1236, MYSQL1210, WEB1226, WEB312, WEB1204, WEB1220, MAIL37, mail-11, MAIL1206, WEB1237, WEB1222, mail-21, MAIL1203, MYSQL1419, MYSQL1402, MYSQL1410, WEB1414, MAIL1418, WEB1435, WEB1410, MYSQL1427, WEB1405, MAIL1406, MYSQL1408, MAIL1416, MYSQL1426, and WEB1434.
  • 2014/09/29   09:42 AM EST - Maintenance on all servers has finished

Resolution Description

Maintenance has been completed successfully.

DNS Name Servers Under DDoS Attack – Resolved

Posted In: Outage — Sep 27th, 2014 at 1:55 am EST by IX: Kevin N.

Incident Description:

Our Name Servers are currently experiencing a large Denial of Service attack. This is causing DNS queries to become slow or fail for some domains on our DNS servers. Our system administration team is working to identify the source and block this attack. We are working to resolve this issue as quickly as possible.

Which Customers are Impacted?

Customers using any of our web, email or database services.

How are Customers Impacted?

Services may be slow or down.

How often will we be updated?

As information becomes available.

Time to Resolution (ETA)

N/A

Incident Updates

  • 2014/09/27 02:33 AM EDT: Our administrators have mitigated a portion of the attack and accessibility of impacted services is continuing to improve.  Some users might still experience intermittent service unavailability until this issue is completely resolved.
  • 2014/09/27 10:59 AM EDT: Our administrators have narrowed the impact of this attack to a small subset of customers using the n23.ixwebhositng.com and ns24.ixwebhosting.com nameservers.
  • 2014/09/27 1:23 PM EDT: ns23 and ns24.ixwebhosting.com are still being attacked by this massive DDoS which continues to cause intermittent connection issues on some cp12 customer sites.

Resolution Description

Our administrators have verified that this DDoS attack has been completely resolved. All services should be back to normal.Thank you for your patience and cooperation during this time.

web255 – FSCK – Resolved

Posted In: Maintenance,Outage — Sep 26th, 2014 at 10:06 pm EST by IX: Antonio S.

Incident Description:

web255 is currently unresponsive, and our system admins are currently investigating.  We will update with more info as soon as it becomes available.

Which Customers are Impacted?

All customers on web255

How are Customers Impacted?

All websites will be unreachable during the downtime.

How often will we be updated?

N/A

Time to Resolution (ETA)

N/A

Incident Updates

9/26/2014 10:00PM EST - The server had to be restarted, and is currently undergoing a mandatory file system check (FSCK).

Resolution Description

FSCK finished. Server is online.

CP 9 – 14 Urgent System Maintenance – Resolved

Posted In: Maintenance — Sep 25th, 2014 at 10:31 pm EST by IX: Antonio S.

Incident Description:

Due to the possibility of degraded communication between virtual machines and the storage network, our system administrators will be performing urgent system maintenance within the virtual environments that CP9 -CP14 servers reside on. Administrators are performing this maintenance with the utmost care to prevent downtime to any customer facing servers but some servers may require a reboot and file system check during this process.

We will be providing updates on a server by server basis as they go under maintenance and as maintenance is completed.

Please feel free to contact support via live chat or phone should there be any concerns or questions regarding the maintenance.

 

List of servers to be worked on by our administrators will be as follows:

WEB1125 - Maintenance Completed
MYSQL1113 - Maintenance Completed
MAIL1114 - Maintenance Completed
WEB1124 - Maintenance Completed
MYSQL1117 - Maintenance Completed
MAIL1122 - Maintenance Completed
WEB1115 - Maintenance Completed
MAIL1123 - Maintenance Completed
WEB1122 - Maintenance Completed
MYSQL1105 - Maintenance Completed
WEB1104 - Maintenance Completed
CP11 - Maintenance Completed

WEB930 – Maintenance Completed
MYSQL911 – Maintenance Completed
MAIL902 – Maintenance Completed
MYSQL908 – Maintenance Completed
WEB901 – Maintenance Completed
WEB919 – Maintenance Completed
WEB907 – Maintenance Completed
MYSQL905 – Maintenance Completed
WEB947 – Maintenance Completed
MAIL901 – Maintenance Completed
WEB936 – Maintenance Completed
WEB909 – Maintenance Completed
WEB912 – Maintenance Completed
MYSQL912 – Maintenance Completed
MYSQL1116 – Maintenance Completed
MYSQL1127 – Maintenance Completed
WEB1101 – Maintenance Completed
WEB1135 – Maintenance Completed
MAIL1118 – Maintenance Completed
WEB1110 – Maintenance Completed
WEB1138 – Maintenance Completed
WEB1139 – Maintenance Completed
MAIL1108 – Maintenance Completed
MYSQL1126 – Maintenance Completed
MAIL1110 – Maintenance Completed
WEB1140 – Maintenance Completed
MYSQL1112 – Maintenance Completed
WEB1109 – Maintenance Completed
WEB1208 – Maintenance Completed
WEB1212 – Maintenance Completed
MAIL51 – Maintenance Completed
MYSQL1205 – Maintenance Completed
WEB1214 – Maintenance Completed
MYSQL1208 – Maintenance Completed
WEB1215 – Maintenance Completed
MAIL1216 – Maintenance Completed
WEB1229 – Maintenance Completed
WEB1225 – Maintenance Completed
MYSQL1201 – Maintenance Completed
MYSQL1207 – Maintenance Completed
WEB1202 – Maintenance Completed

MAIL907 – Maintenance Completed
WEB921 – Maintenance Completed
MAIL918 – Maintenance Completed
WEB906 – Maintenance Completed
WEB944 – Maintenance Completed
WEB920 – Maintenance Completed
MAIL909 – Maintenance Completed
MYSQL902 – Maintenance Completed
WEB1227 – Maintenance Completed
PGSQL1202 – Maintenance Completed
MAIL1211 – Maintenance Completed
WEB1216 – Maintenance Completed
mail-32 – Maintenance Completed
MAIL1218 – Maintenance Completed
WEB1207 – Maintenance Completed
MYSQL1214 – Maintenance Completed
MAIL1202 – Maintenance Completed
MYSQL1220 – Maintenance Completed
WEB1218 – Maintenance Completed
WEB1217 – Maintenance Completed
mail-41 – Maintenance Completed
MAIL1213 – Maintenance Completed
MAIL1205 – Maintenance Completed
WEBMAIL – Maintenance Completed
YSQL1305 – Maintenance Completed
WEB1320 – Maintenance Completed
WEB1314 – Maintenance Completed
PGSQL1302 – Maintenance Completed
WEB1307 – Maintenance Completed
WEB1325 – Maintenance Completed
PGSQL1301 – Maintenance Completed
MAIL1317 – Maintenance Completed
MAIL1310 – Maintenance Completed
WEB1440 – Maintenance Completed
MAIL1415 – Maintenance Completed
MAIL1413 – Maintenance Completed
MYSQL1417 – Maintenance Completed
MYSQL1418 – Maintenance Completed
WEB1417 – Maintenance Completed
MYSQL1425 – Maintenance Completed
WEB1407 – Maintenance Completed
WEB1418 – Maintenance Completed
WEB1438 – Maintenance Completed
MAIL1404- Maintenance Completed

WEB926- Maintenance Completed
WEB910- Maintenance Completed
WEB940- Maintenance Completed
MYSQL914- Maintenance Completed
WEB902- Maintenance Completed
WEB915- Maintenance Completed
MAIL1101- Maintenance Completed
WEB1129- Maintenance Completed
MAIL1115- Maintenance Completed
MAIL1109- Maintenance Completed
WEB1136- Maintenance Completed
WEB1113- Maintenance Completed
WEB1102- Maintenance Completed
WEB1116- Maintenance Completed
WEB1130- Maintenance Completed
WEB1105- Maintenance Completed
WEB1108- Maintenance Completed
WEB1227- Maintenance Completed
PGSQL1202- Maintenance Completed
MAIL1211- Maintenance Completed
WEB1216- Maintenance Completed
mail32- Maintenance Completed
MAIL1218- Maintenance Completed
WEB1207- Maintenance Completed
MYSQL1214- Maintenance Completed
MAIL1202- Maintenance Completed
MYSQL1220- Maintenance Completed
WEB1218- Maintenance Completed
WEB1217- Maintenance Completed
mail41- Maintenance Completed
MAIL1213- Maintenance Completed
MAIL1205- Maintenance Completed
WEB1337- Maintenance Completed
WEB1311- Maintenance Completed
WEB1329- Maintenance Completed
MYSQL1309- Maintenance Completed
WEB1303- Maintenance Completed
WEB1302- Maintenance Completed
MAIL1303- Maintenance Completed
MAIL1316- Maintenance Completed
WEB1327- Maintenance Completed
WEB1332- Maintenance Completed
MAIL1417- Maintenance Completed
MAIL1420- Maintenance Completed
WEB1439- Maintenance Completed
WEB1413- Maintenance Completed
WEB1403- Maintenance Completed
WEB1426- Maintenance Completed
MAIL1402- Maintenance Completed
MYSQL1414- Maintenance Completed
WEB1406- Maintenance Completed
WEB1429- Maintenance Completed
WEB1433- Maintenance Completed
MYSQL1430- Maintenance Completed
MAIL1409- Maintenance Completed

Which Customers are Impacted?

All customers on CP9 - CP14

How are Customers Impacted?

There may be some slowness while the server is under maintenance.  A few servers may also require reboot during this maintenance.  If maintenance requires a server reboot, we expect a file system check to run and services will be unavailable until this completes.

How often will we be updated?

Servers will be added as they come under maintenance.

Time to Resolution (ETA)

N/A

Incident Updates

  • 2014/09/26 03:27 AM EST - Maintenance was started and following VMs are being moved -  WEB1125,  MYSQL1113, MAIL1114, WEB1124,  CP11,  MYSQL1117, MAIL1122,  WEB1115,  MAIL1123, WEB1122,  MYSQL1105,  WEB1104.
  • 2014/09/26 04:14 AM EST  - Second set for maintenance is as follows: WEB930, MYSQL911, MAIL902, MYSQL908,  WEB901, WEB919, WEB907,  MYSQL905,  WEB947, MAIL901,  WEB936,  WEB909,WEB912, MYSQL912, MYSQL1116, MYSQL1127, WEB1101, WEB1135,  MAIL1118,  WEB1110,WEB1138, WEB1139,  MAIL1108,, MYSQL1126,  MAIL1110, WEB1140, MYSQL1112 WEB1109 , WEB1208,  WEB1212,  MAIL51, MYSQL1205, WEB1214 , MYSQL1208,WEB1215, MAIL1216, WEB1229, WEB1225, MYSQL1201, MYSQL1207,WEB1202, webxxx2_server.
  • 2014/09/26 05:40 AM EST -  Second set of servers have been moved and VM is booting up.
  • 2014/09/26 05:52 AM EST - Third  set for maintenance is as follows: MAIL907, WEB921, MAIL918, WEB906, WEB944, WEB920 ,MAIL909,  MYSQL902 ,WEB1227, PGSQL1202, MAIL1211, WEB1216, mail-32, MAIL1218, WEB1207, MYSQL1214, MAIL1202, MYSQL1220, WEB1218 , WEB1217, mail-41, MAIL1213,  MAIL1205, WEBMAIL, MYSQL1305, WEB1320, WEB1314, PGSQL1302, WEB1307, WEB1325,  PGSQL1301, MAIL1317, MAIL1310, WEB1440,  MAIL1415 ,MAIL1413, MYSQL1417, MYSQL1418, WEB1417, MYSQL1425. WEB1407, WEB1418, WEB1438, MAIL1404
  • 2014/09/26 06:50 AM EST - Third set of servers have been moved and VM is booting up.
  • 2014/09/26 06:50 AM EST -  Fourth set for maintenance is as follows: WEB926, WEB910, WEB940, MYSQL914 ,WEB902, WEB915, MAIL1101 WEB1129,  MAIL1115, MAIL1109, WEB1136, WEB1113, WEB1102, WEB1116, WEB1130, WEB1105, WEB1108, WEB1227, PGSQL1202, MAIL1211, WEB1216, mail-32, MAIL1218, WEB1207, MYSQL1214, MAIL1202,  MYSQL1220, WEB1218, WEB1217, mail-41, MAIL1213, MAIL1205, WEB1337 WEB1311, WEB1329,MYSQL1309, WEB1303, WEB1302, MAIL1303, MAIL1316, WEB1327, WEB1332,  MAIL1417, MAIL1420, WEB1439, WEB1413 WEB1403, WEB1426, MAIL1402, MYSQL1414, WEB1406, WEB1429 ,WEB1433, MYSQL1430, MAIL1409

Resolution Description

The blade has been rebooted and maintenance is now over.

 
© 2011 IX Web Hosting.