.... but the one last week lasted almost 5 hours during prime time, fixed itself, then took another hit just a few hours later. There's obviously something going on with the server.
You do realize the move takes minutes and there's no changes needed on your part whatsoever. It's all done outside of the VPS container. Just curious why you would want to stay on the server that's causing you issues. This is the beauty of Virtuozzo.I'll tough it out on this server
Now that I think back (and look through tickets and my welcome email), I believe I was thinking of our old host...with changing IPs when switching servers. I don't know...these years just blend together. That was my mistake.Could you please PM me a ticket # where you was forced to change IPs during the VPS migration to another machine within the same DC? I can't really imagine why this would be required unless if you wanted a clean system or a system with a different control panel or wanted to switch from CentOS 4 to CentOS 5.
Sounds good to me. Like I said, I've been EXTREMELY satisfied here. Anything to make things even better would just be an added bonus.Bryan, there might have been a disconnect between support and maintenance teams. Basically support first tries to resolve the problem inside the specific VPS (which is something that covers 99% if not more of tickets) and then passes the problem to maintenance if it appears that the issue might be outside of the VPS. At the same time if maintenance sees the global problem which can't be fixed / workaround right away the support team gets notified about the possible issue with specific machine so tickets can be handled appropriately. When this happens the problem also gets escalated to me to create a thread on our forums. This process might not be the best and I'll see what can be adjusted to make it better.