Tony

After an investigation this appears to have been caused by a failing power supply. We will be most likely replacing the power supply on this server at a later date to avoid a similar situation in the future.

This has been completed.

Softlayer is already IPv6 compatible and has been for a long time.

a) cPanel does not support ipv6. So if we wished to support it before they have support for it there would be no control panels anymore for users. Unlikely cpanel ETA is not until the end of this year I believe. You can read the feature request that's been with them for I believe 7 years now: http://forums.cpanel.net/f145/case-10334-make-cpanel-ipv6-compatible-35453.html

Starting on Monday February 14th we will be migrating Mercury shared hosting accounts over to a new shared hosting specific server Cougar with the hostname cougar.hawkhost.com. The reason for this is currently Mercury is one of our mixed servers which over the course of 2011 we hope to migrate all mixed servers to act as strictly one specific service rather than being for both shared and reseller. The one major advantage is once migrated over shared hosting users will have access to the shared hosting specific features that are currently not available on our mixed servers. It also means no longer will reseller users be able to affect services with their user accounts. Since all our IP addresses are routed to our VLAN's rather than a specific server we can make this migration very seamless. We will migrate data then re-route the IP address over to the new server. This dramatically reduces the chances of data sync issues which are usually associated with server moves due to IP addresses changing. That is not to say it cannot happen but we are available to assist with any issues users may run into if for whatever reason their data does go out of sync. As for any downtime associated with the migration we estimate it'll be about 1 minute at most as we need to remove the IP from the old server and route it to the new one which can take us about a minute. How the migration will work is we will start migrating users on dedicated IP's first starting on Monday. After that is completed we will move onto users with shared IP addresses. We hope that this entire migration will only last two days we hope but we've created a window of three days. The only thing to keep in mind is once migrated it is not advised to be connecting to the mercury hostname if you currently are. While the data will stay there for now eventually all shared hosting user data will be removed from the Mercury server as it will be fully converted to a reseller hosting only server. So make sure to connect to the cougar.hawkhost.com server once the window has been completed. If you have any questions regarding the maintenance do not hesitate to contact us. Our system administration department is available to answer any questions regarding this. Start Date: 02/14/2011 End Date: 02/17/2011 Estimated Down Time: less than 5 minutes Duration: 3 days

This was completed during the window.

The network has been fine again for a while. We're still awaiting word on what exactly the cause of these issues were. What we've been told is it is believed the issues were caused by a cisco bug and communication with cisco eventually lead to network stability again. As to what was done we're still waiting on answers to that.

This feature is not available and we've stopped advertising it. The reason is we found it extremely unreliable which resulted in complaints and increased ticket load due to this. The feature simply did not mature as we had hoped so eventually we just had to drop it as it was just causing more problems then it was worth having as a feature.

This has been completed. All shared hosting users are now on the Panther server.

What I'd advise doing is making an email account then using gmails option to check pop3 email accounts. The reason being is otherwise all forwarded spam they consider potentially spam from the server you're on which is not good. The pop3 method is much better as it'll just filter it like they filter the email sent directly to your gmail account.

The migration has started.

This has been completed. We hope this will be the end of the random crashes from MySQL.

We will be upgraded Spitfire's MySQL immediately (7:20AM PST) to hopefully resolve a crash but that has been happening in increasing frequency the past week. We are going to switch to a new MySQL build that will allow us to track abuse much easier as well. We estimated MySQL may be unavailable for approximately 5 minutes while we do the switch over. We hope once completed MySQL will no longer be crashing at random on this server. Date: 01/21/2010 Start time (PST): 7:20am End time (PST): 7:30am Estimated Down Time: 5 minutes

Our own cPanel theme with right now additional information and maybe additional features at a later date. Various features work properly and as expected like upgrading between plans. SSH is enabled on all accounts there is no requesting it. Then obviously with being strictly with our shared hosting customers no worries of resellers not screening customers properly and causing random issues on machines. It's something we've been doing the past year as we had grown to a point where we could have either service fill machines pretty quickly so it was no longer a waste of resources.

This has been completed.

408 request timeouts are when the web server is waiting for content from an application (php, perl etc.) or page itself and it never comes and eventually it has to timeout the page for the user rather than continuing to hang. If that is happening on a static page something is very wrong there I'd recommend making a ticket about that and providing us with a url to the page the bot got a 408 on.

Starting on Saturday January 22nd we will be migrating Jupiter shared hosting accounts over to a new shared hosting specific server Panther. The reason for this is currently Jupiter is one of our mixed servers which over the next 12 months we hope to migrate all mixed servers to act as strictly one specific service rather than being for both shared and reseller. The one major advantage is once migrated over shared hosting users will have access to the shared hosting specific features that are currently not available on our mixed servers. It also means no longer will reseller users be able to affect services with their user accounts. Since all our IP addresses are routed to our VLAN's rather than a specific server we can make this migration very seamless. We will migrate data then re-route the IP address over to the new server. This dramatically reduces the chances of data sync issues which are usually associated with server moves due to IP addresses changing. That is not to say it cannot happen but we are available to assist with any issues users may run into if for whatever reason their data does go out of sync. As for any downtime associated with the migration we estimate it'll be about 1 minute at most as we need to remove the IP from the old server and route it to the new one which can take us about a minute. How the migration will work is we will start migrating users on dedicated IP's first starting on Saturday. After that is completed we will move onto users with shared IP addresses. We hope that this entire migration will only last the weekend but we've given ourselves a window to Wednesday just in case it does not go as fast as our typical migrations. The only thing to keep in mind is once migrated it is not advised to be connecting to the jupiter hostname if you currently are. While the data will stay there for now eventually all shared hosting user data will be removed from the Jupiter server as it will be fully converted to a shared hosting only server. If you have any questions regarding the maintenance do not hesitate to contact us. Our system administration department is available to answer any questions regarding this. Start Date: 01/22/2011 End Date: 01/26/2011 Estimated Down Time: less than 5 minutes Duration: 4 days

The silence says it all. It's all about the content of the email and the reputation of the server. So you have a forum software IPB and it sends out an email that looks identical to every other IPB based board. It also looks similar to that of every forum software. So thats a lot of volume of the same type of email and which is why it gets flagged as spam no matter who is sending it. Not a whole lot one can do to resolve that other than changing the template and building a reputation as a reputable sender domain.

This has been completed.

This maintenance has been postponed until Monday, January 17, 2011 to ensure there are no complications during the maintenance window.

Network Maintenance SEA01 [01/18/2011] Date: Tuesday, January 18, 2011 (01/18/2011) Start Time: 12:00 AM PST End Time: 06:00 AM PST Services affected: Public Network Connectivity Location: SEA01 Duration: 6 hours Event ID: 5281 Date: Sunday, January 18th, 2011 Start time: 00:00 PST End time: 06:00 PST Duration: 6 hours Service Affected: Public Network Connectivity Reason: Capacity Increase, Additional Redundancy Device: bbr02.wb01.sea01 Location: SEA01 ================================================== SoftLayer Engineers will be conducting maintenance on the transport network that provides connectivity between the SEA01 datacenter and the Westin building. During this window, Engineers will be bringing a new backbone router online (bbr02.wb01.sea01), as well as adding an additional 40 Gigabits-per-second capacity between SEA01 and WB01. The following services may be impacted during this maintenance: - Public network connectivity for the SEA01 facility - Public / Private connectivity to other SoftLayer facilities from the SEA01 facility During this maintenance, Engineers will make every effort to mitigate the impact to customer traffic; however, customers may see routing anomalies, packet-loss, and/or increased latency. ==================================================

Network Maintenance [01/16/2011] Date: Sunday, January 16, 2011 (01/16/2011) Start Time: 01:00 AM EST End Time: 04:00 AM EST Services affected: Public Network Connectivity Location: WDC01 Duration: 3 hours ================================================== * Short Notice Maintenance * SoftLayer Engineers will be conducting maintenance on the fiber transport network that provides connectivity between the WDC01 datacenter and the Equinix facility in Ashburn. During this window, Engineers will be expanding transport circuits from existing gear further increasing capacity and redundancy. While we expect no impact from this maintenance, the following services will be involved: - Public network connectivity for the WDC01 facility - Public / Private connectivity to other SoftLayer facilities from the WDC01 facility During this maintenance, Engineers will make every effort to mitigate the impact to customer traffic; however, customers may see routing anomalies, packet-loss, and increased latency as routes shift to other redundant circuits. ==================================================

I think it's the fact they're animated. We probably should make some non animated ones.

This has been completed.

This has been completed.