Web Hosting Talk







View Full Version : How is the VDI now?


ebird
04-24-2001, 09:34 PM
Hi,

I think WHT, Below10host and VDI.net, cpanel.net were all down this afternoon. Someone said VDI would improve it's service today.

So, how is it now?

ebird

Sesran
04-24-2001, 09:43 PM
Word has it that they will finish upgrades tonight after 12:00 Midnight EST. Then it should be an uphill climb from there.

superiorhost
04-25-2001, 12:21 AM
well,,, we were supposed to be down right now for 30 minutes while they did the upgrade... 15 after and nothing yet.

Tim L.

netrose
04-25-2001, 12:26 AM
There was a post on VDI's forums that the upgrade was going to be done at midnight between Wednesday and Thursday. So, go to bed and don't wait for it tonight. :mad:

superiorhost
04-25-2001, 12:28 AM
That is the point I am trying to make... it is supposed to be going on right this minute... but WHT is on a VDI server, and we are still in the site... not down...


Tim L :confused:

KDAWebServices
04-25-2001, 11:31 AM
Apparently VDI can't tell the time, 12 midnight on Wednesday is between Tuesday and Wednesday, but VDI obviously believe it is between Wednesday and Thursday.

dherman76
04-25-2001, 11:35 AM
We are on the VDI network and have had no problems. They seem to be rectifying the problem with minimal down time.

MattF
04-25-2001, 01:03 PM
No Problems

I call fluctuating connection reliability a problem - a major problem, one minute its fine, the next minute 75% packet loss. There is a problem that has be acknowledged. :angry:

superiorhost
04-26-2001, 02:07 AM
Well,, The major part of the upgrade is now completed... lets see how things go now. There is still more to be done, but this upgrade was needed to complete the rest.

Let's all cross the fingers and toes !!

Tim L :cool:

KDAWebServices
04-26-2001, 08:16 AM
Yeah, lots cross our fingers that VDI don't unplug anyone elses whole rack of servers because they are to lazzy to walk to the rack and unplug a single server from the switch, when they have a damn good idea which server is causing the problem because they did the exact same thing the day before.