http://www.whwebhosting.com/whmsys/announcements.php Fri, 11 Nov 2011 10:02:09 CST http://www.whwebhosting.com/whmsys/announcements.php?id=5 Fri, 11 Nov 2011 00:00:00 CST We have received valuable feedback in response to our announcement of the upcoming migration of legacy The Planet server traffic to the SoftLayer backbone network.As announced, this migration is planned in order to provide legacy servers the improved performance, stability, peering, and network reach provided through hardware and network capacity upgrades in the SoftLayer backbone.Some customers voiced concerned that the work was scheduled too close to holiday shopping periods at the end of November, such as Black Friday and Cyber Monday.In consideration of these concerns we are accelerating the maintenance so that all phases will be completed before the U.S. Thanksgiving holiday. Please note the revised schedule below.Once again, we do not anticipate any downtime related to this work. The migration is planned in a series of steps to gracefully shift inbound and outbound traffic to peers and ISPs across our various data centers. Customers may notice a change in Internet traffic paths to and from servers as we progress through this migration.The revised timeline will be:Wednesday, November 16 2011 12:00AM - 4:00AM CST(06h00 – 10h00 UTC 16-NOV-2011)Preparation work to configure NetFlow export on the DSRs in Dallas and Houston: During this window there will be no changes made to traffic paths, however configuration will be applied to the aggregation routers to prepare for the final topology. Since these routers handle the aggregate of all customer traffic, this work is scheduled for off-peak times as a precaution.Thursday November 17, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 17-NOV-2011)Ingress changes, phase 1: During this window we will begin to shift ingress traffic from the Internet over to the SoftLayer backbone. Traffic paths into legacy Planet servers will take SoftLayer peers and backbone ISPs.Friday November 18, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 18-NOV-2011)Ingress changes, phase 2: During this window we will complete the shift of ingress traffic from the Internet over to the SoftLayer backbone. We will cease all ingress traffic via the legacy Planet peers and ISPs.Monday November 21, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 21-NOV-2011)Egress changes, phase 1: During this window we will begin to shift egress traffic to the Internet over to the SoftLayer backbone. Traffic paths from legacy Planet servers will egress a mix of SoftLayer peers and legacy Planet ISP links, based on best available route.Tuesday November 22, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 22-NOV-2011)Egress changes, phase 2: During this window we will continue to shift egress traffic to the Internet over to the SoftLayer backbone. Some traffic paths from legacy Planet servers will be shifted over to the SoftLayer ISPs.Wednesday November 23, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 23-NOV-2011)Egress changes, phase 3: During this window we will complete the shift of all egress traffic to the Internet over to the SoftLayer backbone. We will cease all egress traffic via legacy Planet ISPs in Dallas and Houston. Thank you, http://www.whwebhosting.com/whmsys/announcements.php?id=4 Wed, 09 Nov 2011 00:00:00 CST Earlier this summer, our data center made additional investments in the data center backbone network through hardware and network capacity upgrades. We’re now prepared to provide the benefit of the improved performance, stability, peering, and network reach to the servers located in the legacy Planet Houston and Dallas datacenters. A similar activity is planned for the servers located in London, and a similar notification will be sent in the future for that data center.Throughout November, our data center network engineering team will be making network routing changes to migrate Internet traffic for legacy Planet US servers from the previous ISP uplinks onto the data center backbone. In order to minimize risk of any impact to customers, this change will consist of a series of piecemeal steps, gracefully shifting inbound and outbound traffic to each of our peers and ISPs across the various data centers.We do not anticipate any downtime related to this work. Customers may notice a change in Internet traffic paths to and from your servers as we progress through this migration.Here is the planned timeline of events:Wednesday, November 16 2011 12:00AM - 4:00AM CST(06h00 – 10h00 UTC 16-NOV-2011)Preparation work to configure NetFlow export on the DSRs in Dallas and Houston: During this window there will be no changes made to traffic paths, however configuration will be applied to the aggregation routers to prepare for the final topology. Since these routers handle the aggregate of all customer traffic, this work is scheduled for off-peak times as a precaution.Monday November 21, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 21-NOV-2011)Ingress changes, phase 1: During this window we will begin to shift ingress traffic from the Internet over to the data center backbone. Traffic paths into legacy Planet servers will take SoftLayer peers and backbone ISPs.Tuesday November 22, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 22-NOV-2011)Ingress changes, phase 2: During this window we will complete the shift of ingress traffic from the Internet over to the SoftLayer backbone. We will cease all ingress traffic via the legacy Planet peers and ISPs.Egress changes, phase 1: During this window we will begin to shift egress traffic to the Internet over to the SoftLayer backbone. Traffic paths from legacy Planet servers will egress a mix of SoftLayer peers and legacy Planet ISP links, based on best available route.Monday November 28, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 28-NOV-2011)Egress changes, phase 2: During this window we will continue to shift egress traffic to the Internet over to the SoftLayer backbone. Some traffic paths from legacy Planet servers will be shifted over to the SoftLayer ISPs.Tuesday November 29, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 29-NOV-2011)Egress changes, phase 3: During this window we will complete to shift all egress traffic to the Internet over the SoftLayer backbone. We will cease all egress traffic via legacy Planet ISPs in Dallas and Houston.We have also scheduled the following times as contingencies to handle any additional issues we may encounter during the scheduled changes:Sunday, November 20, 2011 12:00AM - 4:00AM CST(06h00 – 10h00 UTC 20-NOV-2011)Off-peak for any high risk or potentially intrusive changesSunday, November 27, 2011 12:00AM - 4:00AM CST(06h00 – 10h00 UTC 27-NOV-2011)Off-peak for any high risk or potentially intrusive changesWednesday November 30, 2011 10:00AM – 2:00PM CST(16h00 – 20h00 UTC 30-NOV-2011)Daytime window for graceful traffic shifts or other configuration adjustmentsThursday, December 1, 2011 12:00AM - 4:00AM CST(06h00 – 10h00 UTC 01-DEC-2011)Off-peak for any high risk or potentially intrusive changesWe will carefully monitor network performance and capacity through this process.Thank you, http://www.whwebhosting.com/whmsys/announcements.php?id=3 Wed, 06 Jul 2011 00:00:00 CDT We wish to inform our customers that we changed some of our terms of service. Below are summaries.Added:More examples of unacceptable material on all Shared and Reseller servers include: TopsitesIRC Scripts/BotsProxy Scripts/AnonymizersPirated Software/WarezImage Hosting Scripts (similar to Photobucket or Tinypic)AutoSurf/PTC/PTS/PPC sitesIP ScannersBruteforce Programs/Scripts/ApplicationsMail Bombers/Spam ScriptsBanner-Ad services (commercial banner ad rotation)File Dump/Mirror Scripts (similar to rapidshare)Commercial Audio Streaming (more than one or two streams)Escrow/Bank DebenturesHigh-Yield Interest Programs (HYIP) or Related SitesInvestment Sites (FOREX, E-Gold Exchange, Second Life/Linden Exchange, Ponzi, MLM/Pyramid Scheme)Sale of any controlled substance without prior proof of appropriate permit(s)Prime Banks ProgramsLottery/Gambling SitesMUDs/RPGs/PBBGsHacker focused sites/archives/programsSites promoting illegal activitiesForums and/or websites that distribute or link to warez/pirated/illegal contentBank Debentures/Bank Debenture Trading ProgramsFraudulent Sites (Including, but not limited to sites listed at aa419.org & escrow-fraud.com)Mailer ProBroadcast or Streaming of Live Sporting Events (UFC, NASCAR, FIFA, NFL, MLB, NBA, WWE, WWF, etc) Tell A Friend ScriptsServer usage.We have found most our customers to stay within "reasonable limits" However, to maintain the integrity of our service, we must state the following restrictions: To all our accounts applies the following restrictions: 1. Multiple hosts resolving at an IP or domain name that we provide without our prior permission. 2. Sites with cgi's running from their domain used on other domains. 3. Use 25% or more of system resources for longer then 90 seconds. There are numerous activities that could cause such problems; these include: CGI scripts, FTP, PHP, HTTP, etc. 4. Run stand-alone, unattended server-side processes at any point in time on the server. This includes any and all daemons, such as IRCD.5. Run any type of web spider or indexer (including Google Cash / AdSpy) on shared servers. 6. Run any software that interfaces with an IRC (Internet Relay Chat) network.7. Run any bit torrent application, tracker, or client. You may link to legal torrents off-site, but may not host or store them on our shared servers. 8. Participate in any file-sharing/peer-to-peer activities 9. Run any gaming servers such as counter-strike, half-life, battlefield1942, etc 10. Run cron entries with intervals of less than 15 minutes. 11. Run any MySQL queries longer than 15 seconds. MySQL tables should be indexed appropriately. 12. When using PHP include functions for including a local file, include the local file rather than the URL. Instead of include("http://yourdomain.com/include.php") use include("include.php") 13. To help reduce usage, do not force html to handle server-side code (like php and shtml). 14. Only use https protocol when necessary; encrypting and decrypting communications is noticeably more CPU-intensive than unencrypted communications.Reseller: Client ResponsibilityResellers are responsible for supporting their clients. We does not provide support to our Reseller's Clients. If a reseller's client contacts us, we reserve the right to place the client account on hold until the reseller can assume their responsibility for their client. All support requests must be made by the reseller on their clients' behalf for security purposes. Resellers are also responsible for all content stored or transmitted under their reseller account and the actions of their clients'. We will hold any reseller responsible for any of their clients actions that violate the law or the terms of service.Full terms of service can be found here:http://www.whwebhosting.com/terms.php http://www.whwebhosting.com/whmsys/announcements.php?id=2 Wed, 17 Nov 2010 00:00:00 CST We have setup new routers at one of our data centers to improve network utilization and to handle an increased amount of traffic. We want to move the existing traffic to these routers and for this we would need a downtime of approximately an hour. We expect the downtime experienced to be less than 45 minutes, however we have kept the additional buffer to ensure that the changes are thoroughly tested. Services will be available intermittently during the downtime.During this downtime, you will not be able access or manage your emails and you will not be able to resolve or manage websites which are on our Plesk and cPanel hosting servers. The downtime is scheduled as mentioned below -Date : 7th December, 2010Time : 1400GMT http://www.whwebhosting.com/whmsys/announcements.php?id=1 Sat, 06 Nov 2010 00:00:00 CDT Regular MaintenanceSaturday Nov 13, 2010Our 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. We appreciate your patience as we make these pro-active changes.Change Details:Change ID: 7100304Window Start Date & Time (24h CST/CDT): Saturday Nov 13, 2010 00:01Window End Date & Time (24h CST/CDT): Saturday Nov 13, 2010 05:00Department: NetworkingChange Activity Details: We are completing a round of code upgrades on our Internet Border Routers. We will be working on three of these during this maintenance window. ibr01.hstntx2 ibr02.hstntx2 ibr02.hstntx1 Each router requires a reboot to load the new code. To ensure uninterrupted service we will reroute customer traffic around a router before we reboot it. However, we have seen from our previous code upgrades there is a possibility that rebooting/isolating one of these routers will causes another one of these particular routers to reboot unexpectedly. This behavior has been attributed to a bug that is corrected in the upgraded code.Impact Statement: In the event that one of the 3 routers unexpectedly reboots; some customers may experience a brief period of packet loss and latency, to and from their server. This will be due to route convergence as traffic takes a different path while the router reboots, and then switches back to the original path after the router has come back online. This interval should be less then 5 minutes. However, most customers will not experience interruptions in service while we are performing this work.