Random Timeouts on FG

Clegko

Clegko

Well-Known Member
DONOR
Joined
Oct 8, 2007
Messages
1,671
Location
Gaithersburg, MD
Car(s)
2016 Chevy Colorado, 1968 Mercury Monterey
Hi, all. Every now and again, when I try to access the site (and the forums, mind), I get random timeouts. For example, everything works great for a bit, then I click a link, and my browser times out. When I refresh, it works fine, but it's getting a bit annoying. I've tried multiple computers, browsers, and even my phone. All of which are having this problem. Anyone else having similar issues, or is it on my end?
 
I haven't noticed anything, but just for kicks, tell us what ISPs you've tried from. Many bonus points if you can post traceroute output that exhibits the problem.
 
I've tried from AT&T only, because thats all I (and my neighbor's <.<) have. As for my phone... it's on AT&T too. Heh.

Code: 
Traceroute has started ...

traceroute to finalgear.com (67.159.47.218), 64 hops max, 40 byte packets
 1  192.168.1.254 (192.168.1.254)  3.684 ms  1.821 ms  2.594 ms
 2  bras3-l0.okcyok.sbcglobal.net (151.164.182.200)  11.695 ms  11.600 ms  10.573 ms
 3  dist1-vlan50.okcyok.sbcglobal.net (151.164.23.130)  9.311 ms  23.836 ms  11.252 ms
 4  bb1-g1-3-0.rcfril.sbcglobal.net (151.164.190.114)  10.077 ms  20.527 ms  9.199 ms
 5  ex2-p1-1.eqchil.sbcglobal.net (151.164.189.82)  38.565 ms  28.870 ms  29.638 ms
 6  (no response)
 7  66.90.127.217 (66.90.127.217)  34.024 ms  35.932 ms  34.811 ms
 8   (66.90.127.177)  33.486 ms  33.784 ms  49.428 ms
 9   (67.159.47.218)  35.146 ms  37.731 ms  36.434 ms

Took a few tries, but that's what I came up with. Hope it helps?
 
Hmm, that timeout on step 6 is weird, what does it look like when the problem doesn't occur?
 
Just ran this one. I called at&t, and they refuse to admit a problem, even though the one it's dropping on, #6, is clearly their part of the connection. *sigh*

Code: 
Traceroute has started ...

traceroute to finalgear.com (67.159.47.218), 64 hops max, 40 byte packets
 1  192.168.1.254 (192.168.1.254)  3.115 ms  2.637 ms  1.544 ms
 2  bras3-l0.okcyok.sbcglobal.net (151.164.182.200)  13.132 ms  10.802 ms  10.201 ms
 3  dist1-vlan50.okcyok.sbcglobal.net (151.164.23.130)  8.319 ms  8.671 ms  8.853 ms
 4  bb1-g1-3-0.rcfril.sbcglobal.net (151.164.190.114)  10.374 ms  8.547 ms  8.664 ms
 5  ex2-p1-1.eqchil.sbcglobal.net (151.164.189.82)  30.684 ms  28.781 ms  28.918 ms
 6  asn4436-nlayer.eqchil.sbcglobal.net (151.164.249.110)  43.111 ms  28.421 ms  28.851 ms
 7  66.90.127.217 (66.90.127.217)  29.416 ms  29.078 ms  28.852 ms
 8   (66.90.127.177)  29.091 ms  137.770 ms  33.653 ms
 9   (67.159.47.218)  34.053 ms  29.320 ms  28.863 ms
 
That's annoying; AT&T should take care of it. Of course, actually contacting someone who is knowledgeable, or at least who cares, is the problem most of the time.

If this is a wider problem (with other AT&T users), we might be able to ask our uplink provider to lean on them. If anyone else on AT&T can help us out with a working and timing-out traceroute, that would be great.
 
I've had random timeouts as well in the last days.
 
me too
 
me three
 
vikiradTG2007 said:
Me four... Just happened here as well.
Click to expand...

Yours might have been because of a setting I was tweaking a couple of minutes ago (which seems to have angered Apache).



Anyone who experiences the problem, please open a cmd window (Terminal if you use OSX, and you know how to do it if you run Linux), and type "tracert www.finalgear.com" then paste the results here (OSX / Linux type "traceroute www.finalgear.com" or maybe "sudo traceroute www.finalgear.com". Make sure you try it multiple times so you get a "bad" and a "good" run (one that times out and one that doesn't). Without those traceroute reports it will be hard to diagnose the problem.
 
For OS X, there's also the built in Network Tools program. To use it, Applications >> Utilities >> Network Utility.

Took me only two tries to get a good and bad run with Traceroute.
Good:
Code: 
Traceroute has started ...

traceroute to finalgear.com (67.159.47.218), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  3.372 ms  2.132 ms  1.619 ms
 2  adsl-70-233-159-254.dsl.okcyok.sbcglobal.net (70.233.159.254)  8.847 ms  8.656 ms  9.648 ms
 3  dist2-vlan60.okcyok.sbcglobal.net (151.164.23.163)  10.174 ms  10.224 ms  10.366 ms
 4  bb2-g1-0-2.rcfril.sbcglobal.net (151.164.93.172)  11.171 ms  9.364 ms  8.243 ms
 5  151.164.171.238 (151.164.171.238)  28.591 ms  28.525 ms  29.081 ms
 6  asn4436-nlayer.eqchil.sbcglobal.net (151.164.249.110)  28.750 ms  30.300 ms  28.321 ms
 7  66.90.127.217 (66.90.127.217)  28.693 ms  30.194 ms  28.806 ms
 8   (66.90.127.177)  29.036 ms  78.745 ms  183.283 ms
 9   (67.159.47.218)  49.019 ms  29.615 ms  48.257 ms
Bad:
Code: 
Traceroute has started ...

traceroute to finalgear.com (67.159.47.218), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  2.252 ms  2.083 ms  1.385 ms
 2  adsl-70-233-159-254.dsl.okcyok.sbcglobal.net (70.233.159.254)  9.232 ms  8.942 ms  8.808 ms
 3  dist2-vlan60.okcyok.sbcglobal.net (151.164.23.163)  8.618 ms  11.192 ms  8.680 ms
 4  (no response)
 5  151.164.171.238 (151.164.171.238)  61.801 ms  210.124 ms  208.279 ms
 6  asn4436-nlayer.eqchil.sbcglobal.net (151.164.249.110)  27.810 ms  28.814 ms  30.226 ms
 7  66.90.127.217 (66.90.127.217)  28.840 ms  28.118 ms  28.805 ms
 8   (66.90.127.177)  29.157 ms  28.250 ms  28.190 ms
 9   (67.159.47.218)  28.013 ms  28.733 ms  29.025 ms
Seems to be happening on #4 for me now... -_-
 
Thanks clegg, hopefully some of the other people who responded above will paste theirs in too, and then we can see if our ISP will bother AT&T about it.
 
PacketCollision said:
Anyone who experiences the problem, please open a cmd window (Terminal if you use OSX, and you know how to do it if you run Linux), and type "tracert www.finalgear.com" then paste the results here (OSX / Linux type "traceroute www.finalgear.com" or maybe "sudo traceroute www.finalgear.com". Make sure you try it multiple times so you get a "bad" and a "good" run (one that times out and one that doesn't). Without those traceroute reports it will be hard to diagnose the problem.
Click to expand...
Will do that. :)
 
Good one
Code: 
Sporer rute til www.finalgear.com [67.159.47.164]
over et maksimum af 30 hop:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     7 ms     7 ms     6 ms  lo1.vgnxx6.ip.tele.dk [80.166.139.121]
  3     7 ms     6 ms     7 ms  ge-0-1-0-40.1000M.vgnxu4.ip.tele.dk [83.88.15.225]
  4    42 ms    43 ms    43 ms  pos0-1-1-0-2488M.arcnqh1.ip.tele.dk [83.88.26.1]
  5    54 ms    47 ms    52 ms  te0-0-1-0-10G.arcnqh2.ip.tele.dk [83.88.22.130]
  6    57 ms   203 ms   208 ms  pos1-0-0-10G.asd9nxg2.ip.tele.dk [83.88.22.222]
  7    42 ms    42 ms    42 ms  ge5-0-0-10G.asd9nxg1.ip.tele.dk [83.88.15.129]
  8    43 ms    42 ms    43 ms  ams-ix.ae1.cr1.ams2.nl.nlayer.net [195.69.145.219]
  9    51 ms    51 ms    61 ms  xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
 10   113 ms   113 ms   113 ms  xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
 11   133 ms   133 ms   133 ms  xe-2-1-0.cr2.ord1.us.nlayer.net [69.22.142.6]
 12   133 ms   133 ms   134 ms  po3-54.ar2.ord1.us.nlayer.net [69.31.111.150]
 13   133 ms   138 ms   196 ms  66.90.127.217 [66.90.127.217]
 14   134 ms   134 ms   134 ms  . [66.90.127.177]
 15   133 ms   134 ms   133 ms  . [67.159.47.164]

Sporing fuldf?rt.

Bad one
Code: 
Sporer rute til www.finalgear.com [67.159.47.164]
over et maksimum af 30 hop:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     7 ms     7 ms     7 ms  lo1.vgnxx6.ip.tele.dk [80.166.139.121]
  3     6 ms     7 ms     7 ms  ge-0-1-0-40.1000M.vgnxu4.ip.tele.dk [83.88.15.225]
  4    43 ms    43 ms    43 ms  pos0-1-1-0-2488M.arcnqh1.ip.tele.dk [83.88.26.1]
  5    43 ms    43 ms    43 ms  te0-0-1-0-10G.arcnqh2.ip.tele.dk [83.88.22.130]
  6    43 ms    43 ms    42 ms  pos1-0-0-10G.asd9nxg2.ip.tele.dk [83.88.22.222]
  7    42 ms    42 ms    42 ms  ge5-0-0-10G.asd9nxg1.ip.tele.dk [83.88.15.129]
  8    42 ms    44 ms    43 ms  ams-ix.ae1.cr1.ams2.nl.nlayer.net [195.69.145.219]
  9    51 ms    51 ms    51 ms  xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
 10   113 ms   113 ms   113 ms  xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
 11   132 ms   133 ms   133 ms  xe-2-1-0.cr2.ord1.us.nlayer.net [69.22.142.6]
 12   133 ms   133 ms   134 ms  po3-54.ar2.ord1.us.nlayer.net [69.31.111.150]
 13     *      133 ms     *     66.90.127.217 [66.90.127.217]
 14     *        *        *     Anmodning fik timeout.
 15   133 ms   133 ms   133 ms  . [67.159.47.164]

Sporing fuldf?rt.
 
Bad:
Code: 
  7     4 ms     4 ms     4 ms  ge-5-1-242.hsa2.StLouis1.Level3.net 
  8     4 ms    10 ms     4 ms  ge-6-12.car2.stlouis1.level3.net

  9    22 ms    24 ms    11 ms  ae-4-4.ebr2.chicago1.level3.net
 10    27 ms    10 ms    10 ms  ae-23-52.car3.Chicago1.Level3.net
 11    13 ms    11 ms    11 ms  nlayer-level3-10ge.Chicago1.Level3.net
 12    14 ms    11 ms    18 ms  po3-54.ar2.ord1.us.nlayer.net
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *       11 ms [67.159.47.218]

Good (L3 hiccup aside):
Code: 
  7   456 ms   403 ms   447 ms  ge-5-1-242.hsa2.StLouis1.Level3.net 
  8    12 ms     8 ms    16 ms  ge-6-12.car2.stlouis1.level3.net
  9    22 ms    16 ms    24 ms  ae-4-4.ebr2.chicago1.level3.net
 10    16 ms    16 ms    16 ms  ae-23-52.car3.Chicago1.Level3.net
 11    41 ms    23 ms    16 ms  nlayer-level3-10ge.Chicago1.Level3.net
 12    19 ms    24 ms    18 ms  po3-54.ar2.ord1.us.nlayer.net
 13    16 ms    16 ms    16 ms  66.90.127.217
 14    18 ms    16 ms    16 ms  [66.90.127.177]
 15    16 ms    16 ms    16 ms  [67.159.47.218]
 
bad:
Code: 
  2    33 ms    35 ms    39 ms  bras1.dus.qsc.de [213.148.133.202]
  3    29 ms    30 ms    30 ms  core4.dus.qsc.de [87.234.11.137]
  4    29 ms    30 ms    29 ms  core1.dus.qsc.de [213.148.134.105]
  5    30 ms    30 ms    29 ms  ddf-b2-link.telia.net [213.248.73.1]
  6    33 ms    33 ms    33 ms  adm-bb1-link.telia.net [80.91.249.88]
  7    34 ms    34 ms    33 ms  adm-b3-link.telia.net [80.91.254.125]
  8    34 ms    34 ms    33 ms  xe-2-3-0.cr1.ams2.nl.nlayer.net [213.248.67.158]
  9    52 ms    47 ms    41 ms  xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
 10   119 ms   120 ms   119 ms  xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
 11   130 ms   130 ms   129 ms  xe-2-1-0.cr2.ord1.us.nlayer.net [69.22.142.6]
 12   130 ms   130 ms   131 ms  po2.ar1.ord1.us.nlayer.net [69.31.111.138]
 13   137 ms   136 ms   137 ms  66.90.127.217 [66.90.127.217]
 14   147 ms   136 ms   136 ms  . [66.90.127.177]
 15     *        *        *     Zeit?berschreitung der Anforderung.
 16     *        *        *     Zeit?berschreitung der Anforderung.
 17     *        *        *     Zeit?berschreitung der Anforderung.
 18     *        *        *     Zeit?berschreitung der Anforderung.
 19     *        *        *     Zeit?berschreitung der Anforderung.
 20     *        *        *     Zeit?berschreitung der Anforderung.
 21     *        *        *     Zeit?berschreitung der Anforderung.
 22     *        *        *     Zeit?berschreitung der Anforderung.
 23     *        *        *     Zeit?berschreitung der Anforderung.
 24     *        *        *     Zeit?berschreitung der Anforderung.
 25     *        *        *     Zeit?berschreitung der Anforderung.
 26     *        *        *     Zeit?berschreitung der Anforderung.
 27     *        *        *     Zeit?berschreitung der Anforderung.
 28     *        *        *     Zeit?berschreitung der Anforderung.
 29     *        *        *     Zeit?berschreitung der Anforderung.
 30     *        *        *     Zeit?berschreitung der Anforderung.
Only getting bad ones at the moment, always hangs at the 66.90.127.177.
 
Last edited:
Just had like a 1.5 hour timeout, same problem as before:
Code: 
  2    72 ms    59 ms    39 ms  bras1.dus.qsc.de [213.148.133.202]
  3    30 ms    36 ms    35 ms  core4.dus.qsc.de [87.234.11.137]
  4    56 ms    46 ms    52 ms  core1.dus.qsc.de [213.148.134.105]
  5    32 ms    30 ms    30 ms  ddf-b2-link.telia.net [213.248.73.1]
  6    42 ms    52 ms    49 ms  adm-bb1-link.telia.net [80.91.251.197]
  7    33 ms    41 ms    56 ms  adm-b3-link.telia.net [80.91.253.90]
  8    32 ms    41 ms    36 ms  xe-2-3-0.cr1.ams2.nl.nlayer.net [213.248.67.158]
  9    74 ms    89 ms    64 ms  xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
 10   132 ms   124 ms   153 ms  xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
 11   160 ms   150 ms   158 ms  xe-2-1-0.cr2.ord1.us.nlayer.net [69.22.142.6]
 12   156 ms   158 ms   161 ms  po3-54.ar2.ord1.us.nlayer.net [69.31.111.150]
 13   162 ms   136 ms   147 ms  66.90.127.217 [66.90.127.217]
 14   172 ms   167 ms   163 ms  . [66.90.127.177]
 15     *        *        *     Zeit?berschreitung der Anforderung.
 16     *        *        *     Zeit?berschreitung der Anforderung.
 17     *        *        *     Zeit?berschreitung der Anforderung.
 18     *        *        *     Zeit?berschreitung der Anforderung.
 19     *        *        *     Zeit?berschreitung der Anforderung.
 20     *        *        *     Zeit?berschreitung der Anforderung.
 21     *        *        *     Zeit?berschreitung der Anforderung.
 22     *        *        *     Zeit?berschreitung der Anforderung.
 23     *        *        *     Zeit?berschreitung der Anforderung.
 24     *        *        *     Zeit?berschreitung der Anforderung.
 25     *        *        *     Zeit?berschreitung der Anforderung.
 26     *        *        *     Zeit?berschreitung der Anforderung.
 27     *        *        *     Zeit?berschreitung der Anforderung.
 28     *        *        *     Zeit?berschreitung der Anforderung.
 29     *        *        *     Zeit?berschreitung der Anforderung.
 30     *        *        *     Zeit?berschreitung der Anforderung.
 
Me too, just about half an hour ago. Did the trace and it had no timeouts, tried 3 times in between trying to get on the forum, forum timed out.
 
You must log in or register to reply here.
Top