Unfortunately moving servers is part of the business. We don't take the decision lightly and there's a good reason to put all of us through this or we wouldn't do it.
Any web hosting company that is popular is going to have to move servers occasionally. We are growing and we outgrow facilities at times. We are growing because we provide a service at a price that is attractive enough to draw customers.
We don't offer the kind of service that warrants putting up a site that yields thousands of dollars an hour. If you want protection for that kind of site there are hosting companies that charge hundreds or thousands of dollars a month to provide that level of service.
I sent out roughly 3,800 emails to our customers with notification of the impending move. I sent out these notifications twice. About 10% of them bounced with either mailbox full, or mail user doesn't exist. No, I'm not going to research 380 emails to try to figure out where else to send the email.
There are other ways to protect yourself on a move too. If you take the time to research the way DNS works you can manage your own DNS and not have to worry about major propagation delays. It's not a light subject, in fact it is probably the most misunderstood subject about TCP/IP networking. But if it's important enough to you then the research is worth it. We don't support it because it can be a nightmare, but with the right tools it can be done efficiently.
The servers are now pinging one by one. The DNS is updating with a lot of the delay dependent on factors beyond our control. Some sites will come up right away, some will take longer. If the server is configured the same for all domains it should be obvious that something else must be causing delays for some. We set the TTLs (Time To Live, or refresh rate) on the zones to one hour a few days before the move. In theory this tells all the nameservers worldwide to check back with us every hour to see if anything has changed. If every nameserver in the world set their TTL to 1 hour, the DNS system would grind to a halt. So, many nameservers won't honor the TTL of an end-point to reduce the network load. In those cases we are stuck with the default TTL in the nameserver you use to resolve DNS (your ISP's nameserver, or another up the chain).
As of right now, 3, 5, 6, 7, 8, 9, 11, 14, 16, 18, 19, 20 are all pinging and resolving. They are being brought up one-by-one. In my case the sites are resolving, but that doesn't necessarily mean they will resolve in your case due to the factors in the last paragraph. But rest assured they are being brought up as fast as they can considering the need to make double-checks of information to make sure nothing starts propagating with the wrong DNS information.
-Bug