K so I am just curious, how many people are having random lag spikes on jc?

getting spikes here and on ebon, dunno what's going on.

Klinti what ISP do you use?

Feb 20th - 10:41 PM server time, currently can't stayed logged in due to lag, Cox Internet. Geographic location: Phoenix AZ

Feb 20th - 10:41 PM server time, currently can't stayed logged in due to lag, Cox Internet. Geographic location: Phoenix AZ

 

 

A wild Caprcia appears

My guess would be it's ISP or geographic issues because i've had no problems.. been on all night... and that's actually a rarity for me (usually have some serious lag because of my ISP...)

 

My Oil Slick brings all the Caprica's to the yard.

Only had them imp side, pub side was fine.

I work for TWC and have been having several issues with lag spikes for about 2 weeks. I contacted our IT dept, showed them my pathping and traceroutes. They fixed an issue with one of their relay's, however the lag still persists on one of the relay points near jedi covenant server. The problem is not persistent and seems to be more prevalent when there is a higher traffic volume. Currently all that customer service tells me is it is ISP side, again everything I see points to their servers. Considering I saw the same issues while connected to AT&T, verizon and TWC now you guys are posting cox is also having similar issues.

Charter here, having issues as well today.

Lag spikes here too on TWC in TX.

 

For me it looked to be a crapload of additional servers on my route to the East coast server (159.153.92.28) last night (25 hops vs the 16 from end of last year). Also, they look to have added an additional EA server (159.153.92.69) between my route and the actual East coast server last night. Every time I'm having a big lagspike night it turns out the zayo.com servers are in my path.

 

This is what I was experiencing last night:

  5    16 ms    28 ms    13 ms  agg32.ausxtxir02r.texas.rr.com [24.175.43.239] 
 6    29 ms    28 ms    26 ms  agg22.hstqtxl301r.texas.rr.com [24.175.41.48] 
 7    30 ms    33 ms    30 ms  bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108] 
 8    29 ms    29 ms    33 ms  bu-ether22.dllstx976iw-bcr00.tbone.rr.com [107.14.19.216] 
 9    28 ms    24 ms    34 ms  0.ae0.pr1.dfw10.tbone.rr.com [107.14.17.232] 
10    38 ms    24 ms    23 ms  66.109.11.22 
11    29 ms    30 ms    29 ms  ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233] 
12    33 ms    48 ms    45 ms  ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62] 
13    48 ms    49 ms    56 ms  ae3.mpr3.atl6.us.zip.zayo.com [64.125.20.174] 
14    78 ms    56 ms    54 ms  ae4.mpr4.atl6.us.zip.zayo.com [64.125.31.198] 
15     *        *        *     Request timed out.
16     *       98 ms   100 ms  xe-5-3-0.mpr1.mem1.us.zip.zayo.com [64.125.26.18] 
17     *       94 ms   107 ms  xe-8-1-1.er1.ord7.us.zip.zayo.com [64.125.21.69] 
18     *        *       99 ms  ae4.cr1.ord2.us.zip.zayo.com [64.125.28.49] 
19   143 ms     *        *     ae6.cr1.lga5.us.zip.zayo.com [64.125.24.33] 
20   196 ms   131 ms     *     ae1.cr2.lga5.us.zip.zayo.com [64.125.29.38] 
21     *      173 ms     *     ae4.cr2.dca2.us.zip.zayo.com [64.125.26.105] 
22   137 ms   142 ms     *     ae1.er2.iad10.us.zip.zayo.com [64.125.20.122] 
23   162 ms   161 ms   164 ms  64.125.199.190.t00673-02.above.net [64.125.199.190] 
24   163 ms     *        *     159.153.92.69 
25   169 ms   153 ms   150 ms  159.153.92.28 

 

This was this morning:

  5    25 ms    14 ms   128 ms  agg32.ausxtxir02r.texas.rr.com [24.175.43.239] 
 6    27 ms    25 ms    23 ms  agg22.hstqtxl301r.texas.rr.com [24.175.41.48] 
 7    30 ms    29 ms    24 ms  bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108] 
 8    24 ms    27 ms    26 ms  bu-ether22.dllstx976iw-bcr00.tbone.rr.com [107.14.19.216] 
 9    35 ms    22 ms    36 ms  0.ae0.pr1.dfw10.tbone.rr.com [107.14.17.232] 
10    20 ms    24 ms    27 ms  66.109.11.22 
11    36 ms    26 ms    29 ms  ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233] 
12    41 ms    36 ms    32 ms  ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62] 
13    55 ms    55 ms    59 ms  ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53] 
14    65 ms    69 ms    69 ms  ae1.er2.iad10.us.zip.zayo.com [64.125.20.122] 
15   187 ms    56 ms    60 ms  64.125.199.190.t00673-02.above.net [64.125.199.190] 
16    55 ms    58 ms    67 ms  159.153.92.69 
17    58 ms    63 ms    60 ms  159.153.92.28 

 

This was last November:

  5    17 ms    19 ms    24 ms  tge0-11-0-35.ausxtxir02r.texas.rr.com [24.175.42.222] 
 6    27 ms    36 ms    26 ms  agg22.hstqtxl301r.texas.rr.com [24.175.41.48] 
 7    31 ms    24 ms    30 ms  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 
 8    24 ms    34 ms    29 ms  ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39] 
 9    28 ms    29 ms    29 ms  107.14.19.97 
10    28 ms    22 ms    21 ms  ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97] 
11    28 ms    38 ms    35 ms  if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5] 
12    24 ms    27 ms    28 ms  66.110.56.18 
13    57 ms    60 ms    53 ms  0.ae4.XT1.DCA5.ALTER.NET [140.222.225.203] 
14    63 ms    69 ms    60 ms  TenGigE0-6-0-0.GW5.DCA5.ALTER.NET [152.63.37.110] 
15    60 ms    62 ms    60 ms  dft-gw.customer.alter.net [152.179.164.162] 
16    60 ms    63 ms    71 ms  159.153.92.28 

The fact that other ISPs are going through the same thing leads me to believe that something is going on with the server itself.