drmike
100% Tier-1 Gogent
Since GreenValueHost gets so much coverage and is assumed to have some clients, everyone should beware of the following that went out via email and was forwarded to me by a customer.
Dear Valued Client,
We are deeply saddened to inform you today of an unfortunate mishap that has occurred today in regards to our ch1 Chicago node that has called for us to put emergency protocol precautions into place. This email will go into depth regarding what has happened and the measures that we are going to be taking to ensure that negative impact to your hosting experience is minimized as much as possible during this issue.
The IPv4 migration that is scheduled for June 19, 2014 (tomorrow) is greatly affected by this mishap. We have contacted our upstream provider for our ch1 node to announce a /24 IPv4 block to their ISPs earlier this month and unfortunately to our dismay and disappointment, the /24 block has not yet been announced according to BGP records. The existing IPs currently in use for ch1 are scheduled to be revoked/"unannounced" on June 21, 2014, which explains the urgency of the situation for renumbering.
This is as big of a problem/situation as it appears, and as such, the following stipulations have been put in place:
If the IPv4 announcement of our /24 block is not resolved TONIGHT,
> Clients will be immediately migrated to nodes in the ColoCrossing network tomorrow. IPs WILL change however IPv6 will NOT be available. The majority of clients will be migrated to a SATA server and remaining clients will be migrated to an SSD server. Eventually, clients that have been migrated tomorrow (if this stupulation is to occur) will all be consolidated into ONE SSD cached RAID-10 SATA node on the ColoCrossing network.
If the IPv4 announcement of our /24 block is RESOLVED TONIGHT,
> The scheduled IPv4 migration will occur as originally scheduled on the same network with the same upstream provider. However, eventually all clients will all be consolidated into ONE SSD cached RAID-10 SATA node on the ColoCrossing network, with IPv4 addresses changing again for a second time. This will take place near the end of June to the start of July. IPv6 will not be available on the ColoCrossing network.
We are very truly sorry about the inconveniences caused by this. I can assure you that we strive to satisfy all of our clients and ensure quality service, and that our main priority is making sure that our clients are always in safe hands. We believe that the above circumstantial stipulations are the best possible courses of actions to take for the well being of both our clients and the service that we provide.
If you have any questions or concerns, please contact us through our helpdesk and we would be more than happy to assist you.
Thank you,
Jon Nguyen, Operations Director
Key words: Clients will be immediately migrated to nodes in the ColoCrossing network tomorrow
Dear Valued Client,
We are deeply saddened to inform you today of an unfortunate mishap that has occurred today in regards to our ch1 Chicago node that has called for us to put emergency protocol precautions into place. This email will go into depth regarding what has happened and the measures that we are going to be taking to ensure that negative impact to your hosting experience is minimized as much as possible during this issue.
The IPv4 migration that is scheduled for June 19, 2014 (tomorrow) is greatly affected by this mishap. We have contacted our upstream provider for our ch1 node to announce a /24 IPv4 block to their ISPs earlier this month and unfortunately to our dismay and disappointment, the /24 block has not yet been announced according to BGP records. The existing IPs currently in use for ch1 are scheduled to be revoked/"unannounced" on June 21, 2014, which explains the urgency of the situation for renumbering.
This is as big of a problem/situation as it appears, and as such, the following stipulations have been put in place:
If the IPv4 announcement of our /24 block is not resolved TONIGHT,
> Clients will be immediately migrated to nodes in the ColoCrossing network tomorrow. IPs WILL change however IPv6 will NOT be available. The majority of clients will be migrated to a SATA server and remaining clients will be migrated to an SSD server. Eventually, clients that have been migrated tomorrow (if this stupulation is to occur) will all be consolidated into ONE SSD cached RAID-10 SATA node on the ColoCrossing network.
If the IPv4 announcement of our /24 block is RESOLVED TONIGHT,
> The scheduled IPv4 migration will occur as originally scheduled on the same network with the same upstream provider. However, eventually all clients will all be consolidated into ONE SSD cached RAID-10 SATA node on the ColoCrossing network, with IPv4 addresses changing again for a second time. This will take place near the end of June to the start of July. IPv6 will not be available on the ColoCrossing network.
We are very truly sorry about the inconveniences caused by this. I can assure you that we strive to satisfy all of our clients and ensure quality service, and that our main priority is making sure that our clients are always in safe hands. We believe that the above circumstantial stipulations are the best possible courses of actions to take for the well being of both our clients and the service that we provide.
If you have any questions or concerns, please contact us through our helpdesk and we would be more than happy to assist you.
Thank you,
Jon Nguyen, Operations Director
Key words: Clients will be immediately migrated to nodes in the ColoCrossing network tomorrow
Last edited by a moderator: