VaporNode vaporizes Phoenix
You are receiving this email today because you currently have one or more active VPS services with us. Back in May 2016, we announced that the future addition of a Tampa, FL datacenter was coming soon...
We are now ready to begin migrating VPS customers from Phoenix, AZ to Tampa, FL. This is a mandatory migration - all customers must have their VPS services moved to our infrastructure in Tampa.
Why is this good for you? Like always, we own all the hardware in Tampa. There is nobody else but VaporNode that needs to be relied on when it comes to the servers and networking gear. The Tampa location is in a new tier 3 datacenter facility and on a very nice network with direct peering points in Atlanta, Miami, and Los Angeles. We have also switched our core network devices from HP to Juniper due to their high performance and reliability for high-traffic environments. Furthermore, the actual VPS hardware nodes are newer machines and we have modified our networking setup to allow for more complex networking schemes on each VPS if necessary.
Why is this bad for you? Unfortunately, this migration will cause all VPSs to undergo a few minutes of downtime and an IP address reassignment. We estimate about 30-45 minutes of downtime per VPS. This allows us time to shutdown your VPS cleanly, compress the disk image, transfer it to Tampa, then uncompress and boot your VPS. If your VPS uses DHCP IP assignments (KVM), you will automatically have your new IP address assigned to the VPS. If your VPS uses static IP assignments (KVM), you will need to manually change your IP address with the provided gateway, netmask, and IP (these will be provided for each customer during the migration). If your VPS uses OpenVZ, the new IP address will also be automatically applied.
When is the migration happening? This migration is scheduled to begin at October 1st, 2016 10:00AM EST and be completed at or before October 2nd, 2016 10:00AM EST. Your VPS will not be offline during this whole period - only for the 30-45 minutes it should take to complete the transfer. If you would like to schedule a different time to move your VPS, please contact us and we may be able to work out a better date. We have provided a 24 hour window to provide ample time to move all VPSs.
What if I have an OpenVZ VPS? Due to changes in our virtualization backend, we will no longer support or offer OpenVZ services after the migration has been completed. Instead, we will convert all existing OpenVZ containers to LXC containers. LXC virtualization is very similar to OpenVZ. From an end-user's perspective, you will not notice much of a difference. The OpenVZ to LXC conversion is straightforward and is not expected to result in any data loss.
If you have any questions or concerns about the migration, please let us know. We are here for you 24/7.
My 2 cents:
I really do not get it.
Why would a customer who chose service for the Phoenix location want to move to the other side of the US and be on a completely differently routed network?
Besides that, I thought this was to be an addition, not a replacement... Sound to me like they spent too much money on their build-out in Florida and can no longer afford to sustain their original location. As such, I know I will be looking to cancel the services I have with them. If they can't even sustain both locations it doesn't bread much hope they will be around long. In addition to that, I ordered my services in Phoenix, AZ for a reason,not Florida and the new location will not be acceptable for my use. I am not sure why these groups keep doing this, its like they enjoy hemorrhaging customers and money.
- Does it bother you when a host forces you to migrate to a new location and new IP?49 votes
- No  8.16%
- I usually just cancel the service34.69%
- Location and IP don't really matter to me  4.08%