Inconsistent Lag

[[BTF]Defiant!]

I'm getting frequent and significant lag spikes.  Bad enough I sometimes only turn part way around or am rubber banded somewhere finding I didn't make a jump.

Tracert is ugly. netgraph looks like an uncut lawn.

I've shutdown every internet using device except the gaming machine.  I'm on an upgraded cable connection 100+mbs/20mbs in the southwest.  I don't think the problem is on my side.

I'm willing to help pay, maybe we could pool cash in some periodic manner.

Advice?  Options?
Appreciated,
[BTF]Defiant!

[Punk_FAS]

I believe others have expressed interest in pitching in for a server upgrade/improvement as well. I can't commit to that right now, but I know Defiant isn't the only one that has expressed interest in such a thing.

[quadz]

It's not the server.

My netgraph is a flat green line, consistently:



And I'm 1000 miles from the datacenter.

So, it's got to be a particular route to the server that's clogged.

I'll need your traceroutes. And ideally screenshots of your netgraphs as well.

Accumulating data points on the route being affected is important, so I can submit a trouble ticket with concrete examples.

Otherwise, it's just me saying "yeah everything's fine for me but I'm hearing other folks are having issues."

[Punk_FAS]

Nothing has stood out as far as connection issues for me. Netgraph is smooth, without any red lines really that I have noticed (I noticed like a single one, but I believe that was during a map change, which happens sometimes).

[[BTF]Defiant!]

Code: [Select]

Tracing route to tastyspleen.net [23.227.170.222]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    80 ms    22 ms    83 ms  <ME>
  3   113 ms    31 ms    19 ms  100.127.73.182
  4   181 ms    25 ms    40 ms  100.120.100.10
  5   232 ms    36 ms    33 ms  68.1.4.252
  6    79 ms   127 ms    65 ms  100ge16-2.core1.lax1.he.net [216.218.224.117]
  7   152 ms    58 ms    84 ms  100ge14-1.core1.lax2.he.net [72.52.92.122]
  8    46 ms    48 ms    61 ms  100ge8-2.core1.phx2.he.net [184.105.81.178]
  9    84 ms    47 ms    57 ms  100ge10-1.core1.dal1.he.net [184.105.81.174]
 10   166 ms   176 ms   152 ms  hivelocity-ventures-corp.e0-11.switch3.dal2.he.net [216.66.79.226]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17    84 ms    60 ms    47 ms  tastyspleen.net [23.227.170.222]

Code: [Select]

Pinging tastyspleen.net [23.227.170.222] with 32 bytes of data:
Reply from 23.227.170.222: bytes=32 time=76ms TTL=52
Reply from 23.227.170.222: bytes=32 time=146ms TTL=52
Reply from 23.227.170.222: bytes=32 time=76ms TTL=52
Reply from 23.227.170.222: bytes=32 time=76ms TTL=52
Reply from 23.227.170.222: bytes=32 time=68ms TTL=52
Reply from 23.227.170.222: bytes=32 time=55ms TTL=52
Reply from 23.227.170.222: bytes=32 time=74ms TTL=52
Reply from 23.227.170.222: bytes=32 time=44ms TTL=52
Reply from 23.227.170.222: bytes=32 time=120ms TTL=52
Reply from 23.227.170.222: bytes=32 time=50ms TTL=52
Reply from 23.227.170.222: bytes=32 time=53ms TTL=52
Reply from 23.227.170.222: bytes=32 time=48ms TTL=52
Reply from 23.227.170.222: bytes=32 time=55ms TTL=52
Reply from 23.227.170.222: bytes=32 time=73ms TTL=52
Reply from 23.227.170.222: bytes=32 time=115ms TTL=52
Reply from 23.227.170.222: bytes=32 time=92ms TTL=52
Reply from 23.227.170.222: bytes=32 time=46ms TTL=52
Reply from 23.227.170.222: bytes=32 time=60ms TTL=52
Reply from 23.227.170.222: bytes=32 time=47ms TTL=52
Reply from 23.227.170.222: bytes=32 time=70ms TTL=52
Reply from 23.227.170.222: bytes=32 time=187ms TTL=52
Reply from 23.227.170.222: bytes=32 time=102ms TTL=52
Reply from 23.227.170.222: bytes=32 time=43ms TTL=52
Reply from 23.227.170.222: bytes=32 time=251ms TTL=52
Reply from 23.227.170.222: bytes=32 time=240ms TTL=52
Reply from 23.227.170.222: bytes=32 time=130ms TTL=52
Reply from 23.227.170.222: bytes=32 time=64ms TTL=52

Update May 2020 - Yes it was outside my home network at hop 1 to my service provider.  Smooth as a fresh cut lawn now.

Def

[Admin]

Hmm,

Code: [Select]

Tracing route to tastyspleen.net [23.227.170.222]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    80 ms    22 ms    83 ms  <ME>
  3   113 ms    31 ms    19 ms  100.127.73.182
  4   181 ms    25 ms    40 ms  100.120.100.10
  5   232 ms    36 ms    33 ms  68.1.4.252
 17    84 ms    60 ms    47 ms  tastyspleen.net [23.227.170.222]

Frankly not what I was anticipating.

If one can't get a good/reliable ping within one's own cable plant, then nothing after it can (necessarily) be expected to make sense.

In other words, if your local cable router "<ME>" is showing extreme variance, then everything following it is potentially suspect, especially if the final hop (17) shows similar variance.


I was hoping to see an anomaly in the latter hop (or two) of your route. But if the anomaly begins at hop (2) then… it may be something closer to home.

I guess we could try traceroutes to other Q2 servers where you have good/stable ping, to compare?

[0rbisson]

For the last 2 months pings have jumped dramatically. not just for 1 p[layer but a few, especially overseas players.

I used to ping 210-220 to dm but now it's 280-330

I ping 220 to pf-tdm-co

winmtr trace results (expires in 1 week)

DM -
https://pastebin.com/WFekXwTN

pf-tdm-co -
https://pastebin.com/7EfTadMh

[0rbisson]

 

[Zeppelin]

nothing we can do, Alpha.
Australia is very far away from everything 

[yahoo]

turn off hax
heheh

[[BTF]Defiant!]

SOLVED

Yes it was outside my home network at hop 1 to my service provider.  Smooth as a fresh cut lawn now.

Def

[Sgt. Dick]

Vae had this problem once 

[otg]

I have constant pj and packet drops. XXX is IP information i blocked out.

Code: [Select]

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                                   name -    0 |  178 |  178 |    0 |    0 |   18 |    0 |

|                           xxx -    0 |  178 |  178 |    9 |   17 |  100 |   15 |

|  wxxx -    2 |  166 |  163 |    8 |   12 |   51 |   15 |

|  xxx-    0 |  178 |  178 |    9 |   13 |   44 |   16 |

|            xxxm -    0 |  178 |  178 |    9 |   14 |   48 |   16 |

|  10gigabitethernet9-9.core1.tor1.he.net -    0 |  178 |  178 |    9 |   16 |   55 |   15 |

|              100ge9-2.core2.chi1.he.net -    0 |  178 |  178 |   19 |   23 |   67 |   27 |

|              100ge8-2.core1.mci3.he.net -    0 |  178 |  178 |   31 |   35 |   72 |   38 |

|             100ge15-2.core1.dal1.he.net -    0 |  178 |  178 |   41 |   45 |   89 |   47 |

|hivelocity-ventures-corp.e0-11.switch3.dal2.he.net -    0 |  178 |  178 |   42 |   46 |   73 |   50 |

|                   No response from host -  100 |   35 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   35 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   35 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   35 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   35 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   35 |    0 |    0 |    0 |    0 |    0 |

|                         tastyspleen.net -    0 |  178 |  178 |   42 |   46 |   89 |   51 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[quadz]

Hi - unfortunately (for diagnostic purposes) the traceroute is perfect: 178 packets sent to tastyspleen; 178 received.

I'd recommend running WinMTR while you are in game, during the time when you are experiencing packetloss in-game. Hopefully some will then be captured in the traceroute.

[ex]

This problem has been happening a lot lately for many people too.  I don't notice it real bad but it does sometimes feel.. sticky might be a good descriptor.  Here's my traceroute just done here.

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    23 ms    14 ms    11 ms  <me>
  3    18 ms    31 ms    20 ms  tge0-0-0.msqutx1202h.texas.rr.com [24.164.211.97]
  4    20 ms    18 ms    15 ms  agg38.dllbtxlb02r.texas.rr.com [24.175.50.9]
  5    20 ms    18 ms    26 ms  agg21.hstqtxl301r.texas.rr.com [24.175.49.8]
  6    29 ms    18 ms    17 ms  66.109.9.88
  7    43 ms    24 ms    14 ms  lag-11.bear1.Houston1.Level3.net [4.59.126.33]
  8     *        *        *     Request timed out.
  9    25 ms    21 ms    39 ms  HIVELOCITY.ear1.Dallas1.Level3.net [4.14.16.38]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15    20 ms    19 ms    14 ms  tastyspleen.net [23.227.170.222]

in-game feels smooth, it's just occasionally there's weird sticky lag that won't show up on netgraph (no red lines, no green spikes/mountains, no jitter).  I'm noticing a ton of timeouts here though.. maybe it's some of the main servers not sending a ping back that's causing the issues for everyone.

Also Spectrum (time warner) sucks.  How am I going to live in the city with the server and get routed down to Houston then back up to Dallas