Hello Wa'il

I have read in another post, that you would like a Tracert, if we experience slow access to the site, so here we go:

It is now 03:43am UK time ( I know, I should be in bed ) and things have just slowed down.

C:\WINDOWS>tracert www.lowcarb.ca

Tracing route to lowcarb.ca [216.118.73.98]
over a maximum of 30 hops:

1 <10 ms 14 ms <10 ms 10.85.0.1
2 <10 ms 14 ms <10 ms gsr01-cr.blueyonder.co.uk 62.30.112.33]
3 13 ms 14 ms 14 ms atm7-1-cro-hsd-gsr-linx.cableinet.net [194.117.158.142]
4 13 ms <10 ms 14 ms e41-isp1-gw1-uk.cableinet.net [194.117.140.9]
5 13 ms * <10 ms rt-linx-a.thdo.bbc.co.uk [195.66.224.103]
6 <10 ms 14 ms 14 ms 212.58.239.130
7 110 ms 96 ms 110 ms nac-gw.thdo.bbc.co.uk [212.58.255.178]
8 110 ms * 110 ms a9-0-0-245.msfc1.oct.nac.net [209.123.11.217]
9 110 ms 96 ms 110 ms fa0-0.core1.pwebtech.com [207.99.8.198]
10 96 ms 110 ms 110 ms 216.118.73.98

Trace complete.

C:\WINDOWS>

All back to normal now. 03:49am

Hi Sabine,

Hmm, there must have been another problem. It is really good that you have taken a trace, the one you posted shows a good connection.

Wa'il

I'll let you know, if it happens again. The trace actually showed an excellent connection, as it went over the pond and still only showed 110ms for the return trip. I normally see about 120-150ms. Is your server based on the east coast ?

Yes, the server is in the east coast.

Wa'il

FYI, there were some MAJOR problems here in Canada this week.. many servers were down and routes were slow, I was unable to log onto mine for most of Wednesday as were many of the people who were at the meeting I was attending in Nfld. It might have been more widespread than we first thought.

Nat

Hmm, there were major problems at LINX as well. Weird.

Hmm, things were really slow again just now, for about 2 mins. I also got "page cannot be displayed"-error, when I went to the main page (forum.lowcarber.org).

Here is a trace route:
Tracing route to lowcarb.ca [216.118.73.98]
over a maximum of 30 hops:

1 13 ms <10 ms 14 ms 10.85.0.1
2 <10 ms 14 ms <10 ms gsr01-cr.blueyonder.co.uk [62.30.112.33]
3 14 ms 14 ms 13 ms atm6-1-cro-hsd-gsr-linx.cableinet.net [194.117.1
40.142]
4 14 ms 14 ms 14 ms e41-isp1-gw1-uk.cableinet.net [194.117.140.9]
5 * 13 ms 14 ms rt-linx-a.thdo.bbc.co.uk [195.66.224.103]
6 * <10 ms 14 ms 212.58.239.130
7 * 96 ms 110 ms nac-gw.thdo.bbc.co.uk [212.58.255.178]
8 96 ms * 96 ms a9-0-0-245.msfc1.oct.nac.net [209.123.11.217]
9 * 97 ms 109 ms fa0-0.core1.pwebtech.com [207.99.8.198]
10 96 ms 110 ms 96 ms 216.118.73.98

Trace complete.

Looks fine to me, maybe a tad busy, but return trips of 110ms are great.

Time: 10:32pm BST

It does look fine, quite good actually.

This implies the slow connection is not related to our site or netwwork. Unless this trace is after the fact?

If or when this happens again, calculate how long it is slow, and make several tracert while the reponse is slow. At the same time try to connect to other site to compare results. Make sure the test site is not a popular portal like Yahoo, since they are cached.

Wa'il