Anybody care to explain....

[plan2switch]

Look how frequent my downtime is and more importantly how long each lasts



And now as I'm posting this Chrome is down

[Susy]

We had been having problems with some user scripts . We think we still have some problems at our end. We have been checking through the different possibilities. We are upgrading some of the softwares at the server side to see if any of these could have caused the problem.

[Vin DSL]

Fair warning to JaguarPC. This <explicative deleted> is blasting you on the home page at NukeCops - 50,000+ page views a day. Here's the URL:

http://www.nukecops.com/

It'll probably rotate off the main page in the next 24-48 hours. In that case, the URL will be:

http://www.nukecops.com/article-773--0-0.html

If it was me, I'd kick their coolie asses off JagPC, but it's your rice bowl...

[lookout]

It's still a free country Vin. Not that this poster has been showing a high level of Netiquette. But I expect Jag and his staff all have pretty thick hides by now. It's a necessary characteristic in the support business.

I think the initial poster is relying much too much on the accuracy of a web server monitoring service. These are notoriously unreliable, no matter their endorsers say. In this case, the one being used (according to the Nuke cops post) queries the server every 15 minutes, with some follow ups after that. I wouldn't be surprised if the reported downtime interval is NEVER less than 15 minutes. There's plenty of reasons for falsely reported downtimes too. A server that's temporarily busy may deny some requests, or just not respond quickly enough. It may have too short a time out before reporting a failure (you see this with link checkers sometimes). The monitoring service itself may be having problems. There may be a problem elsewhere along their pipe to the monitored site. Maybe even a problem with the monitored host site itself (but not its server).

At best, these web monitoring services provide one with a heads up that the website may actually be experiencing problems. It's also possible that the web monitoring service itself may be contributing to the reported problems, if too aggressive in its monitoring.

[plan2switch]

Vin,

What I posted in Nuke Cops was true. It was a real experience. I've experienced it for a month now. And I've waited that long before I let it out. So you want me to just shut up and let more webmasters experience the same? I'm pretty sure there are better shared hosting out there. I don't want it to happen to other people. And as you can see the title of that article was a question (are you paying attention?). There's a difference.

The truth is that it wouldn't matter to me if there were frequent downtimes as long as they reboot the servers right away. It takes one hour before they reboot it. I have to create a ticket just to tell them that the server is down.

You're lucky you don't experience that kind of problem and you're lucky you're site's nature is not the same as mine. Seems to me that your site is a personal site while mine on the other hand is a web directory wannabee. I have a many visitors and regular members while yours seems to have little. Try checking out my site's alexa ranking, google pr, and google saturation just to show you how downtimes affect my site. I repeat I have many visitors and UPTIME is important. I've been embarrassed to a lot of people because of this frequent downtime because this doesn't happen before in my previous host.

If you love JAG PC so much and I understand that you're not having any problem with downtime then why don't we trade place in servers that is if you're on shared hosting too.

I have to remind you guys, that aside from an automated server monitor. I have a script that is installed that tells me the time from the last reboot plus I have a couple of people (regular die hard members) calling me often telling me "Hey, are the servers down again?", "Hey, the site's been down for more than an hour now" I guess they're unreliable too huh.

I'm on Chrome VinDSL, let's trade places. I'll transfer my site on your server and transfer yours to Chrome. If we do that then I'll take back what I said in Nuke Cops and I'll make an article referring to that article that it was a mistake and that there was a perfect explanation for the downtime and that now (thanks to the transfer) I'm not experiencing downtimes anymore.

[mattsiegman]

If your site is soooo important, you should get on a dedicated server. All shared hosting environments are bound to have problems.

If you go to your client login and look at the network status page it says this:

If at any time a server gives a failed reading, support will be alerted immediately.
Please do not contact support for known outages identified here, thank you.

did you decide not to read that part, or do you just not use the nwtork status page as an indicator of outages? If you don't, you should.

Now I don't know what exactly is wrong with your server, but it UP on the network status page right now. Mercury is entirely down, but Chrome is up.

Now I'm sorry if I seem like a little bitch right now, but I'm sick of this.

By the way, Jag hosts nukecops: http://jaguarpc.com/forums/showthrea...gh t=nukecops

[Vin DSL]

Originally posted by plan2switch
I'm on Chrome VinDSL, let's trade places. I'll transfer my site on your server and transfer yours to Chrome...

No thanks!

[edit]Vin, that was unneeded. I think that plan2switch understands that you hate his guts. -- Matt[/edit]

[Connie]

plan2switch,

I neither love nor hate JaguarPC. I have a site that has been hosted here since
mid 2000. It is an e-commerce site so up time is very important. I don't know
that the site is important but up time is. I get a lot of traffic from Google,
but I also spend about $800.00 per month in pay per click advertising. If the site is
down then I have paid for a click that results in a 404 error page, so up time
is very important to me personally. It cost me money in more ways than one when
the site is down.

Overall I think Jag does a very good job. I get p**d every once in a while, but
then I remember what it has been like with other host.

Susy acknowledged that there was a problem going on Chrome due to a script. It
seems strange to me that no one else is complaining about down time except you.
I was going to visit your web-site to find out why it was so important, but could
not find a link to it.

Any way I'm not belittling your problem. We all want 100% up time. We all want
10 minuet response time from support. The real world is that is not going to
happen. Especially on a shared server.

If I understood all of your comments correctly Jag is not your first host. Why did
you move the site to Jag if your previous host was all that good? If you have a
good host you stay there. If you don't you move.

Hope this works out for you whatever your decision is. Also, hope you reconsider
bad mouthing Jag. That seems to me to be very unprofessional on your part. That's
ok on this Forum. I don't think it professional to take your complaints somewhere
else.

Thats my 2 cents worth which isn't worth much.

[Vin DSL]

Originally posted by clssam
I was going to visit your web-site to find out why it was so important, but could not find a link to it...

• http://www.mukamo.com/

[Vin DSL]

Originally posted by mattsiegman
...Now I'm sorry if I seem like a little bitch right now, but I'm sick of this...

And, I'm sorry if I'm causing you problems as a mod, Matt, but his backstabbing pisses me off to the max. JagPC isn't just a mass webhoster. It's a community also. When this <explicative deleted> dis's JagPC on the Internet, he dis's us all.

And, planning2switchagain, or whatever the hell your nick is on this board, I suggest you check the importance of your own particular web site, before you start comparing it to others.

This info was taken from your own web site:

[JPC-Greg]

What server is this on plan2switch ?

I would never rely on a third party program completely. All it would take is one point in their isp route, or ours, to fail and cause incorrect posts. thats not to say they are always incorrect, heck they could be 100% ..... its just that wide of error margin .

Anyway, if the server your own is having frequent http problems we need to look at it. Also, http problems dont mean the server is down, just apache on that server. If your going to monitor a servers uptime completely make sure you check all its critical services : httpd, proftpd, mysql, exim, whm/cpanel, imapd, sshd, cppop ...and any others I cant recall right offhand.

[plan2switch]

I started hosting with Jag just last Sept 5 and I haven't registered yet with easymonitor.com. Right from the very start there was the frequent downtime problem or whatever you may call it. How did I know? I'm always online. I'm better than any monitoring system as far as knowing if my site is reachable or not because I'm always on to it. Plus I have mods who are also there posting messages and they can't reach the site so they call me if the server was down. Users from my site come from different part of the globe like the US, Japan, Hawaii, Middle East, you name a continent we have registered members in them. We all can't reach the site when there is a downtime. Now if that's not a legit downtime then I don't know what it is.

Then I registered on easymonitor late September as a verifying tool when I can't reach my site. I also have this php script http://www.mukamo.com/uptime.php
I also do ping checks and traceroute and they all they indicate that host is unreachable. Why did I resort to these tools? Because every so often we can't reach the site.

Ok I understand that I shouldn't rely on easymonitor. Should I also stop relying on myself and the other regular members that the site is down when we can't reach it?

I also understand that there are problems with shared hosting and having downtime is normal. Having frequent downtimes is not normal. I haven't seen Chrome up for more than 3 days using the php script.

Remember all these tools that I'm stating is just a support or as a validator when we ourselves the users and me the webmaster can't reach the site.

The network status says "If at any time a server gives a failed reading, support will be alerted immediately.
Please do not contact support for known outages identified here, thank you." Yeah I've read that a couple of times already but for me that's not true. If you wait for them to restart the server then it will take you an hour before you can reach your site again. If I create a ticket then apparently that's the time after a couple more minutes they reboot the server.

If you want to know the real story behind this, read my support tickets and perhaps you would understand why it all boiled down to this.

[plan2switch]

Originally posted by Vin DSL And, planning2switchagain, or whatever the hell your nick is on this board, I suggest you check the importance of your own particular web site, before you start comparing it to others.

Ok I checked and here it goes

As far as page views are concern, here's what I learned



What about Membership, here's what I learned



Alexa ranking?



you know why you beat me in the number of backlinks? because my site just started May 12, 2003. It's just 5 months old while yours seems to be up for ages with minimal activity and visitors.

[mattsiegman]

This is getting out of hand. Continue your discussion with Jag and figure out whats going wrong or start a new thread. This is turning into mud-slinging.