Many customers have reported network stability issues, high packetloss, inconsistent or slow network speeds as well as unexpected/unannounced VM reboots after the migration from Naaldwijk to Amsterdam.
Unfortunately, after the migration began, network related issues occurred that were not present in the initial testing/benchmarking phase of the new location. Only after live-traffic was present on the network did these issues being to appear, which has led to the issues you have experienced.
This has impacted our Shared Hosting, Virtual Private Server, DNS, and VPN service in the Netherlands equally.
Friday, July 11th, there is planned maintenance to correct these issues. Scheduled to arrive at the datacenter in Amsterdam tomorrow is new hardware which will be used to replace what we believe is some faulty components. We do believe that this will correct the issue moving forward. There will be downtime during this maintenance, but we do believe that this will resolve the issue moving forward. We do not know the exact time of this maintenance, it will occur sometime after the scheduled delivery of the hardware (6AM EST / 12PM CEST).
!!!! UPDATE !!!! July 12th, the package that was intended to arrive today by 6AM EST (12PM CEST) to the datacenter in Amsterdam has taken an unfortunate detour to Italy, per the FedEx tracking number. It is unlikely to arrive today by the end of the day. We will post further updates related to this here.
We understand the frustration of all of those impacted by this, and we are quite frustrated by the situation ourselves. Our Netherlands based services have always been top notch and of high quality, and after the migration the quality fell well below not only our standard, but the standard of any serious business. We cannot apologize enough for the inconvenience caused by this and are working diligently on restoring service to a production quality state.
Please do not open a ticket regarding this issue We have been and continue to be aware of the situation. We, like you, are waiting for a fix as well. We remain hopeful that tomorrow's maintenance will correct this.
