~ServerPoint~
New Member
Is it reachable when your site is down?
No ( That's why I had said that you shacked my mind to have another lokk on the things. That could be big problem
Is it reachable when your site is down?
Its not a "big" problem. Only problem is the budget your willing to spend on it - technicalities are quite easy to overcome provided you have the $$$.No ( That's why I had said that you shacked my mind to have another lokk on the things. That could be big problem
Hey,
Checking is run every 5 minutes, and if at a check, the site cannot be reached, an SMS alert is sent to 5 people who have the ability to update this. I'm thinking about doing something like the NY NOC where they have a seperate website hosted off-site with network downtime reports and updates.
And it isn't something that should really be in a welcome email. When people buy hosting they expect the sites will stay up, so having an "in the event of an outage yada........" in the welcome email might be scary Maybe it could be mentioned in a say monthly news letter as well as any other contact details.
Is the 1-800 number listed in the welcome email?However typically to answer Jan's question we have our 1-800 number which is reachable 24/7 no matter what the issue which allows you to be in contact if there was a problem. Since the new solution isn't offered yet thats our main contact.
Where are your list of contact options? On the site?If you can't download a program to reach anybody via instant messenger..use ebuddy and/or meebo. I think having a email account separate from your domain helps. For Example, having a gmail account so that you can check it via POP3 to get your clients help.
It appears that a few hosts in here have elected to provide phone support and not provide an off network support area. The only issue with that is your lines coudl easily become tangled up. I personally rather know who contacted us and be able to keep the information on record.
People don't understand... just by putting the support system on a different system and then pointing the A record of support.domain.com to the other server doesn't resolve the issue.
When your server goes down, your DNS server also goes down along with it. Hence the support help desk wont be resolvable by your clients.
I just did a WHOIS lookup of your domains and 3 of 5 providers have NS delegated to only 1 server (doesn't matter if you have it pointing to 2 different IPs or 200 of them). Despite your effort to add redundancy to your help desk, everything will be a waste when your server actually goes down.
Anyone here has any idea what Multicast is? We haven't yet had the chance to deploy this level of redundancy cause it requires approval from RIPE NCC. And our routers aren't specifically designed for multicast routing either. It isn't expensive at all... honestly, it will be cheaper than most other solutions but issue is being approved for doing it
Why would I be disappointed?[UW]Glenn;1042154 said:Sorry not to disappoint you Jan
Why would I be disappointed?
If someone noticed their/your site was down at 2am your time, would you answer your mobile?