TTORA Forum banner

1 - 14 of 14 Posts

·
Registered
Joined
·
489 Posts
Discussion Starter #1
The past 2 weeks or so I've sometimes not been able to get to ttora and usually when I can, it takes about 5 minutes to load a page, including on the forums. I know its not my connection as I can get to every other website just fine. Are there any known issues going on right now?
 

·
Registered
Joined
·
489 Posts
Discussion Starter #4
Run a trace route and see if there is a bad router somewhere between you and the TTORA servers.
i did a quick traceroute and heres what came up:

traceroute to ttora.com (209.209.29.210), 64 hops max, 40 byte packets
1 128.61.112.1 (128.61.112.1) 1.933 ms 1.310 ms 1.278 ms
2 128.61.111.233 (128.61.111.233) 1.802 ms 1.242 ms 1.485 ms
3 campus1-rtr.gatech.edu (130.207.254.137) 3.803 ms 2.590 ms 2.328 ms
4 gateway1-rtr.gatech.edu (130.207.254.113) 1.770 ms 1.810 ms 1.763 ms
5 143.215.194.81 (143.215.194.81) 1.808 ms 2.086 ms 2.168 ms
6 te2-1--225.tr01-asbnva01.transitrail.net (137.164.131.153) 16.329 ms 16.727 ms 16.217 ms
7 cogent-peer.asbnva01.transitrail.net (137.164.130.122) 15.664 ms 16.121 ms 16.181 ms
8 te7-2.mpd01.dca02.atlas.cogentco.com (154.54.1.77) 15.716 ms te8-2.mpd01.dca02.atlas.cogentco.com (154.54.2.49) 48.953 ms te7-4.mpd01.dca02.atlas.cogentco.com (154.54.7.157) 16.126 ms
9 vl3493.ccr02.dca01.atlas.cogentco.com (154.54.7.229) 15.950 ms te7-2.mpd01.dca01.atlas.cogentco.com (154.54.1.69) 15.880 ms vl3492.mpd01.dca01.atlas.cogentco.com (66.28.4.85) 16.284 ms
10 te9-4.ccr02.iah01.atlas.cogentco.com (154.54.24.22) 30.199 ms te7-3.ccr02.iah01.atlas.cogentco.com (66.28.4.90) 30.273 ms 29.870 ms
11 te4-1.ccr01.aus01.atlas.cogentco.com (154.54.1.65) 33.563 ms te7-4.ccr02.lax01.atlas.cogentco.com (154.54.5.194) 65.814 ms te7-4.mpd01.lax01.atlas.cogentco.com (154.54.2.198) 66.865 ms
12 te3-4.ccr01.lax04.atlas.cogentco.com (154.54.2.238) 66.088 ms te4-4.ccr01.lax04.atlas.cogentco.com (154.54.6.242) 65.985 ms te4-1.ccr01.phx02.atlas.cogentco.com (154.54.1.166) 55.250 ms
13 pac-west-telecomm_inc.demarc.cogentco.com (38.99.205.86) 66.678 ms 66.660 ms 66.404 ms
14 te4-1.ccr01.sna02.atlas.cogentco.com (154.54.25.125) 66.862 ms csc12001-gig3-1.lsan.mdsg-pacwest.com (63.93.65.1) 66.381 ms 65.671 ms
15 * te3-4.mpd01.lax01.atlas.cogentco.com (154.54.3.38) 66.639 ms *
16 csc6501r-vlan2.oak.mdsg-pacwest.com (63.93.97.4) 75.317 ms 74.876 ms 74.518 ms
17 66-42-9-226.oak.mdsg-pacwest.com (66.42.9.226) 75.391 ms 75.352 ms 75.358 ms
18 209-209-11-6.oak.inreach.net (209.209.11.6) 77.172 ms 75.586 ms csc12001-gig3-1.lsan.mdsg-pacwest.com (63.93.65.1) 66.558 ms
19 * * *
20 * * *
21 66-42-9-226.oak.mdsg-pacwest.com (66.42.9.226) 75.752 ms * *
22 209-209-11-6.oak.inreach.net (209.209.11.6) 77.804 ms * *
23 * * *
24 * * *
25 * * *
26 * * *


and then lots more steps of just stars

it seems to get off campus fine and then starts REALLY messing up within pacwest and inreach.

any ideas?
 

·
Random Dude
Joined
·
1,043 Posts
That traceroute looks fine to me. The big jumps in latency are when you cross large geographical regions. The speed of light is fast, but only so fast. Try it from India :)

If the website is super super slow the very first time you connect each day then that sounds like it could be a DNS problem.

If it just kind of stalls out from time to time but more or less works then that sounds more like a packet loss problem. I'd try a binary search along the hosts in that traceroute. So when the website is slow ping ttora.com for ~30 seconds and then see if there was packet loss. If there was, jump to a host midway through the traceroute output and try pinging it for ~30 seconds. Do that until you find the host that is losing your packets.
 

·
Registered
Joined
·
489 Posts
Discussion Starter #7
its running bad slow right now and taking over 5 minutes to do ANYTHING related to ttora.com. Trying a ping of www.ttora.com gives no return. It resolves the IP to 209.209.29.210 instantly so the DNS seems to be working fine. The problem stays around all day, not just the very first time each day. I had a buddy off campus on Comcast do a ping and he got the same results as me, so I know it's not my campus connection.

i started pinging each IP in the traceroute and step 8, Cogentco, is where the loss is. Everything up to cogent responds in under 15 ms, but Cogentco doesnt respond at all. None of its IPs respond. All the various domains AFTER cogentco respond fine, so the problem is at Cogentco.

Any ideas?
 

·
Registered
Joined
·
489 Posts
Discussion Starter #8
oh and just to clarify, when i say no respone, that means no response within 30 seconds or so....5 minutes later it might respond if im lucky
 

·
Random Dude
Joined
·
1,043 Posts
Some hosts will pass ping traffic but not respond to pings themselves. Most likely that's what's happening with those cogentco boxes. If you can get to a machine after one that doesn't ping that's most likely what's happening.

If I were in your situation now I'd be playing with telnet and tcpdump. I'd setup tcpdump and then telnet to ttora.com on port 80. I'd do that to replicate the problem there. Are SYN packets going unanswered? Does the SYN/ACK come back and then nothing else? These all indicate different problems.

I'd look at the headers in the HTTP response for evidence that my provider is sending the traffic through a proxy of some sort that could be broken or misbehaving.

Is ttora.com/forum the only part of ttora.com that's slow? Or do other parts of ttora.com work ok?
 

·
Big tars, little bed.
Joined
·
8,407 Posts
i finally got on today, been trying since noon. has the site been down?
 

·
Registered
Joined
·
489 Posts
Discussion Starter #11
Some hosts will pass ping traffic but not respond to pings themselves. Most likely that's what's happening with those cogentco boxes. If you can get to a machine after one that doesn't ping that's most likely what's happening.

If I were in your situation now I'd be playing with telnet and tcpdump. I'd setup tcpdump and then telnet to ttora.com on port 80. I'd do that to replicate the problem there. Are SYN packets going unanswered? Does the SYN/ACK come back and then nothing else? These all indicate different problems.

I'd look at the headers in the HTTP response for evidence that my provider is sending the traffic through a proxy of some sort that could be broken or misbehaving.

Is ttora.com/forum the only part of ttora.com that's slow? Or do other parts of ttora.com work ok?
its all of ttora, not just the forum directory. ill see what i can do as far as what you suggested and let you know

i finally got on today, been trying since noon. has the site been down?
same with me, its running ok right now
 

·
Registered
Joined
·
414 Posts
on a windows box, you can also try :

pathping www.ttora.com

it'll give you a tracert and ping each point along the route and generate some stats for you. Kinda handy for figuring out stuff like this. (and its included in XP and Vista)

M
 
1 - 14 of 14 Posts
Top