Take a look at the responses from Alerta for our little site:
10/12/2005 07:39:28 Chicago USA OK 24.1 0.53 369.63
10/12/2005 07:39:29 Oklahoma City USA OK 24.1 1.89 104.22
10/12/2005 07:39:28 Las Vegas USA OK 24.1 0.68 289.28
10/12/2005 07:39:28 Frankfurt GERMANY OK 24.1 0.73 269.99
10/12/2005 07:39:30 London UK OK 24.1 2.70 72.94
10/12/2005 07:39:29 Hong Kong CHINA OK 24.1 1.95 100.83
10/12/2005 07:39:27 Atlanta USA OK 24.1 0.12 1644.47
10/12/2005 07:39:28 Orlando USA OK 24.1 0.44 448.23
Basically timing out from half the world, and terribly slow from elsewhere.
You will need to submit a ticket with your website so we can investigate. I am not able to interpret that data and if the last bit is the response time in milliseconds. then your site is loading up in less than 1 second
And no, the response times are the ones in the column headed 30.45… that’s over 30 seconds!
Please bear in mind that we use dozens of hosts here and wouldn’t raise the issue in a forum unless is was both real and serious. I actually posted the Alerta data as an independent confirmation that there is an issue… as evidence that it is not a figment of our imagination.
I used tracert http://www.dnsstuff.com/ . It comes under 30 ms. Can you check tracert from where you are. Check Server Monitoring - server is running smoothly.
The traceroute is from a SINGLE destination. That is an important point… because I am NOT saying it is the server. I do not know what it is: could well be your local network or similar.
The FACTS however are above. Alerta shows this from different parts of the world, completely independently. I get the same problem from my BT account here. I get the same problem via a proxy. The site is simply timing out half the time.
So there IS a serious issue here… which has something to do with your hosting.
The traceroute looks OK:
Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
1 2 0 0 0.4 ms
66.36.240.2 AS0
IANA-RSVD-0 c-vl102-d1.acc.dca2.hopone.net. 255 US Unknown: 80d5187e
2 0 0 1 0.4 ms [+0ms]
66.36.224.226 AS0
IANA-RSVD-0 ge4-0.core1.dca2.hopone.net. 0 miles [+0] 254 US Unknown: 82c2d174
3 2 0 0 0.4 ms [+0ms]
66.36.224.227 AS0
IANA-RSVD-0 ge5-0.core2.dca2.hopone.net. 0 miles [+0] 254 US Unknown: 80b1cbc2
4 2 1 1 1.8 ms [+1ms]
66.36.224.185 AS0
IANA-RSVD-0 iar2-ge-2-0-0.washington.savvis.net. 0 miles [+0] 252 US Unix: 12:31:15.454
5 79 2 2 2.1 ms [+0ms]
206.24.226.98 AS0
IANA-RSVD-0 bcs2-loopback.washington.savvis.net. 0 miles [+0] 252 US Unix: 12:31:15.534
6 16 16 15 15 ms [+13ms]
204.70.192.53 AS6878
AS6878-T-Systems dcr1-so-3-0-0.atlanta.savvis.net. 0 miles [+0] 251 US Unix: 12:31:15.566
7 28 16 28 16 ms [+1ms]
204.70.193.189 AS0
IANA-RSVD-0 acr1-so-7-0-0.miami.savvis.net. 0 miles [+0] 248 US Unix: 12:31:15.646
8 30 28 28 28 ms [+11ms]
208.172.99.82 AS25248
BlueTone-AS bpr2-so-0-0-0.miamimit.savvis.net. 0 miles [+0] 248 US Unix: 12:31:15.697
9 34 28 33 28 ms [+0ms]
208.172.108.18 AS3
MIT-GATEWAYS internap.miamimit.savvis.net. 0 miles [+0] 248 US Unix: 12:31:15.735
10 31 29 28 28 ms [+0ms]
69.25.0.13 AS33631
PARC-ASN border5.pc1.bbnet1.mia003.pnap.net. 0 miles [+0] 246 US Unix: 12:31:15.760
11 31 28 28 28 ms [+0ms]
216.52.162.66 AS4323
TWTC webhosting-9.border5.mia003.pnap.net. 0 miles [+0] 245 US Unknown: 82bb2e4f
12 30 * * 30 ms [+2ms]
204.10.105.200 AS26608
LACNIC-26592
[Reached Destination]ns4.m****here.biz. 0 miles [+0] 54 US Unix: 12:40:10. 88
But clearly there is a serious issue… which needs to be resolved urgently.
Errr… so Alerta don’t know what they are doing eh?
That seems to be what you are saying. Maybe I should tell them.
The FACTS:
I timed out when I tried to access the site this morning. I checked with Alerta and it confirmed the problem. Then things seemed to speed up again so I let it pass.
I tried to access the site an hour ago. It timed out. Alerta confirmed the problem. This time I raised a ticket and came here, armed with the PROOF that there was a serious issue.
What do I get back? I get you guys going into denial mode, calling traceroute is fine, and asking “Where’s the issue?”, as though I was some sort of muppet.
Unless you are braindead surely you can see the issue… read above!
I provided not just a claim of a problem, but evidence to back it up… so please do not start asking me where the issue is. There IS or an issue, and it is YOUR job to determine what it is.
Perhaps it is intermittent (it looks that way)… in which case the appropriate response is to state that this may be the case, and monitor the server and network very very closely, to try to identify it.
The appropriate response is NOT to ask the customer “Where is the issue” when the customer has actually experienced the issue.
From your post, it was assumed that you are experiencing this issue, even as of now. Can you tell me what server you are on and I’ll check through its uptime history for today.
At the moment it is back to normal… but will it last? I frankly doubt it, as it didn’t last time.
Which server? No idea… no-one has told us that, and it wasn’t in our welcome email. Surely you can find that information from your end? When you do, perhaps you could let me know too?
OK. Web3 (hosted on UNIX5) had a few timeout issues this morning due to high load. The issue has been corrected and we are monitoring it. The timeouts lasted no more than 1 minute on each occasion.
I appologise for the incident. The issue is not of a regular nature and only happened this morning
Please note though: Alerta stats do not lie.
[/QUOTE]
As per our policy, we do not rely on alertra, siteuptime or any 3rd party stats system. In the past, they have given us conflicting results. We have installed our own system and websites are checked on all our servers from 2 locations every 60 seconds.
Steve, at JodoHost we face problems head-on. We solve them and move forward. If we had not been doing this and blaming everything that happens wrong on our customers, we will not be here.