We had a a routing issue today, which is resolved, and more info coming as soon as possible.
As for other issues in last months we are aware, had a few DDOS attacks and some issues on the 2003 servers. All the 2003 servers are going away in the coming months as the EOL if finalized in 2014 for them with Microsoft. We've already got about 10 servers moved off 2003 with good success.
This change is helping a lot and we're moving them to new hardware with higher storage, memory, CPU etc and looking forward to launching new complimentary services and offerings that can tie in in early 2014.
I just wanted to address your concern with us and let you know we are working here to fix as well. You can even request a move to the new servers before we move the servers as a whole if you like.
stephen - another good suggestion would be for you to put a monitor and alert to check if the sites go down - I should not have to notice it
We already do this per minute on every server, but it is impossible to do it for every site, it would overload any monitoring system we put in place. However we do this occasionally for 1 or 2 weeks if an ongoing issue. The best way to handle is to escalate your ticket using helpline (AT) jodohost.com that sends an email to on shift and company managers if you feel something is not handled well, and we will take a look. Thank you for your feedback, and welcome to continue it there via our official means, I don't want to take this thread off topic or get point hit for saying any more, but we will aid/asssist/address any issue.
As for moving some already, if classic ASP we've seen some items cause some pool crashes but we have some workarounds for that, just need to know the details to check. Some classic ASP commands seem to trigger the IIS 7.5 rapid fail protection when they are otherwise running properly and not failing, and after a series of failures rapid fail stops the pool, making sites down with a 503. (others may find that useful if they see similar issue)
it's all site specific -- most of the time - but the issue is even if it's up now - nothing was fixed to prevent for the future and it's giving me a bad name for my clients
We certainly do fix for future, but it takes knowing it is happening to resolve. It sounds to me that it is likely asp classic and we need to modify the rapid fail parameters, but I will need info to check and correct this, the techs are also starting to set this earlier on now for classic ASP sites. If you can send a mail to helpline, or give me ticket ID I'll have it checked, but this isn't our support desk so I won't request more than this here. Thanks