Welcome to the Achaea Forums! Please be sure to read the Forum Rules.

Bad Lag Spikes

NaverreNaverre Member Posts: 304 ✭✭✭✭ - Eminent
I live in central Texas, have Time Warner. Recently had some bad lag the past week or so, so much so that hunting easy stuff has become rather risky. I kept hoping that it would clear up, since it's happened to me occasionally. When it didn't, I decided to run a traceroute so I'd know if I should yell at TW, and it turns out it's Achaea. Occasionally, I get a clean one like this:
 Tracing route to www.achaea.com [69.65.42.198]
over a maximum of 30 hops:
  1     3 ms     8 ms     7 ms  192.168.0.1
  2    27 ms    29 ms    29 ms  70.114.0.1
  3    36 ms    49 ms    49 ms  xe-0-0-1.nbrntxlu03m.texas.rr.com [24.28.134.65]
  4    27 ms    29 ms    40 ms  be14.lvoktxad01r.texas.rr.com [24.175.33.56]
  5    28 ms    29 ms    37 ms  agg21.snavtxuu02r.texas.rr.com [24.175.32.144]
  6    39 ms    47 ms    33 ms  agg23.hstqtxl301r.texas.rr.com [24.175.32.156]
  7    28 ms    39 ms    39 ms  bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108]
  8    38 ms    48 ms    39 ms  bu-ether12.dllstx976iw-bcr00.tbone.rr.com [66.109.6.39]
  9    35 ms    41 ms    26 ms  0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
 10    38 ms    40 ms    48 ms  107.14.16.201
 11    55 ms    59 ms    59 ms  xe-2-3-0.er1.Chi2.Servernap.net [66.252.3.133]
 12    57 ms    64 ms    65 ms  po-12.csr2.Chi3.Servernap.net [66.252.0.69]
 13    63 ms    60 ms    69 ms  po-102.ddr1.Chi3.Servernap.net [66.252.0.130]
 14   137 ms   139 ms   139 ms  www.achaea.com [69.65.42.198]
But more often this:
Tracing route to www.achaea.com [69.65.42.198]
over a maximum of 30 hops:
  1     3 ms     9 ms     9 ms  192.168.0.1
  2    20 ms    15 ms    28 ms  70.114.0.1
  3    43 ms    41 ms    33 ms  xe-0-0-1.nbrntxlu03m.texas.rr.com [24.28.134.65]
  4    28 ms    29 ms    29 ms  be14.lvoktxad01r.texas.rr.com [24.175.33.56]
  5    28 ms    29 ms    29 ms  agg21.snavtxuu02r.texas.rr.com [24.175.32.144]
  6    38 ms    41 ms    36 ms  agg23.hstqtxl301r.texas.rr.com [24.175.32.156]
  7    34 ms    32 ms    24 ms  bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108]
  8    35 ms    38 ms    45 ms  bu-ether12.dllstx976iw-bcr00.tbone.rr.com [66.109.6.39]
  9    37 ms    33 ms    29 ms  0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
 10    33 ms    39 ms    39 ms  107.14.16.201
 11    55 ms    49 ms    59 ms  xe-2-3-0.er1.Chi2.Servernap.net [66.252.3.133]
 12    57 ms    60 ms    57 ms  po-12.csr2.Chi3.Servernap.net [66.252.0.69]
 13    56 ms    60 ms    59 ms  po-102.ddr1.Chi3.Servernap.net [66.252.0.130]
 14   137 ms     *      132 ms  www.achaea.com [69.65.42.198]
Or, this:
Tracing route to www.achaea.com [69.65.42.198]
over a maximum of 30 hops:
  1    10 ms    13 ms     8 ms  192.168.0.1
  2    16 ms    31 ms    20 ms  70.114.0.1
  3   270 ms    49 ms    49 ms  xe-0-0-1.nbrntxlu03m.texas.rr.com [24.28.134.65]
  4    27 ms    29 ms    29 ms  be14.lvoktxad01r.texas.rr.com [24.175.33.56]
  5    27 ms    30 ms    38 ms  agg21.snavtxuu02r.texas.rr.com [24.175.32.144]
  6    32 ms    22 ms    39 ms  agg23.hstqtxl301r.texas.rr.com [24.175.32.156]
  7    40 ms    38 ms    38 ms  bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108]
  8    36 ms    45 ms    23 ms  bu-ether12.dllstx976iw-bcr00.tbone.rr.com [66.109.6.39]
  9    51 ms    29 ms    39 ms  0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
 10    27 ms    39 ms    39 ms  107.14.16.201
 11    55 ms    59 ms    59 ms  xe-2-3-0.er1.Chi2.Servernap.net [66.252.3.133]
 12    57 ms    60 ms    58 ms  po-12.csr2.Chi3.Servernap.net [66.252.0.69]
 13    56 ms    59 ms    59 ms  po-102.ddr1.Chi3.Servernap.net [66.252.0.130]
 14   139 ms   128 ms     *     www.achaea.com [69.65.42.198]
 15   147 ms   132 ms     *     www.achaea.com [69.65.42.198]
 16   169 ms     *      145 ms  www.achaea.com [69.65.42.198]
Ran a bunch of them, and except for the occasional ~300 ms spike somewhere along the route (pretty rare), the routes follow these patterns. More often than not, I get a dropped packet on Achaea, and nowhere else. Also, not sure how significant the 60+ms jump just on Achaea's servers is. It's the first time I've run one on Achaea, so it may just be standard fare. Paging @Tecton (honestly not sure who else to page, sorry!).

Comments

  • AtalkezAtalkez Member Posts: 5,048 @@ - Legendary Achaean
    I've had this happen to be plenty of times. 

    Literally all things will be running fine, but Mudlet gets dc'd. Tracert on achaea shows dropped packets, and it clears up in 15-20 minutes.


    You hug Aurora compassionately.
    Praxides
  • NaverreNaverre Member Posts: 304 ✭✭✭✭ - Eminent
    Atalkez said:
    I've had this happen to be plenty of times. 

    Literally all things will be running fine, but Mudlet gets dc'd. Tracert on achaea shows dropped packets, and it clears up in 15-20 minutes.
    Yeah, me too, and it's always cleared up. But I've been playing quite a bit over the past few weeks, and it hasn't cleared up for even a little while.
  • AtalkezAtalkez Member Posts: 5,048 @@ - Legendary Achaean
    Naverre said:
    Atalkez said:
    I've had this happen to be plenty of times. 

    Literally all things will be running fine, but Mudlet gets dc'd. Tracert on achaea shows dropped packets, and it clears up in 15-20 minutes.
    Yeah, me too, and it's always cleared up. But I've been playing quite a bit over the past few weeks, and it hasn't cleared up for even a little while.
    Yeah I have no idea. I'll be running Forums, Skype, Espn and things like that. Literally the only thing that will drop is Mudlet. Sometimes I even have trouble reconnecting, even though nothing else is having trouble.

    It's super frustrating when I lag 15-20s and then it spits it all out at once on the screen -then- I get dc'd almost as if there was some sort of interruption and the overload crashed the connection. 

    Again, no other issues with other programs/connections, so it's pretty frustrating sometimes.


    You hug Aurora compassionately.
Sign In to Comment.