375 replies to this topic

[Fake News]

Still dealing with this, any chance of getting a POP on US soil?
thanks!

[Boost]

I recently moved to a new city in NC and I currently use TWC (50 Mbps download / 5 Mbps upload) as they're the only ISP available in my area. As others have experienced in the past based on this thread (and others here on MWO forums and elsewhere), it seems like I am having severe latency issues when specifically playing MWO. My baseline ping will be in the 30's, but I'll get intermittent to constant lag spikes that increase my ping to the 100's or 1000's. This phenomenon once was prevalent only during peak internet usage hours (I live in an apartment complex), but now it occurs most of the time.

I did the basic diagnostic workup - first making sure my wireless router and network adapter work functioning properly. Long story short, it seems like I am having my connection throttled with excessive network buffering based on some network tests.

After trying some suggestions seen other websites that have not resolved the latency issue, I've just resorted to using my iPhone's personal hotspot (AT&T LTE) when playing MWO.

[NocturnalBeast]

I have pretty much learned to accept that my ping is worse since the server move. However, my ping is very stable now, it stays around 110ms - 120ms with very few spikes, compared to a few months ago when it was spiking to 500 + ms intermittently.

ebolachan, on 14 May 2015 - 05:03 PM, said:

Still dealing with this, any chance of getting a POP on US soil?
thanks!

Yeah, the big slowdown for me is through Chicago and across the border.

[Quicksilver Aberration]

Hate to necro threads, but this problem has been occurring frequently lately with Time Warner users, at least within SJR (myself and Ares, so bit of hyperbole on my part).

Edited by Quicksilver Kalasa, 19 February 2016 - 07:27 PM.

[Aresye]

Quicksilver Kalasa, on 19 February 2016 - 07:27 PM, said:

Hate to necro threads, but this problem has been occurring frequently lately with Time Warner users, at least within SJR (myself and Ares, so bit of hyperbole on my part).

Yup.

I normally have a stable ping between 40-70, but sometimes I'll end up on a server with 300-400 ping. I only play NA servers btw.

It's odd because it's just within a single match this is an issue. My theory is that for some of the MWO servers Time Warner takes a way different path than others.

[Moomtazz]

I'll just leave this here..

[NocturnalBeast]

My connection has greatly improved over the past few months, I get sub 100ms ping again most of the time.

[Kin3ticX]

Quicksilver Kalasa, on 19 February 2016 - 07:27 PM, said:

Hate to necro threads, but this problem has been occurring frequently lately with Time Warner users, at least within SJR (myself and Ares, so bit of hyperbole on my part).

I will keep an eye out for this. You may want to grab the IP of the game server when you notice you are getting throttled. I use Wireshark but im sure there are many ways

[Cabbage Merchant]

Kin3ticX, on 20 February 2016 - 03:34 AM, said:

I will keep an eye out for this. You may want to grab the IP of the game server when you notice you are getting throttled. I use Wireshark but im sure there are many ways

Wireshark is probably the easiest and best solution for watching packet traffic.

Also I'm still having this issue with TWC where my average ping is 30-50ms, but spikes randomly to as high as 1700ms. Usually doesn't have a huge impact on my games, but sometimes I'll teleport between two Dires or something similar.

[Kodyn]

I'm on TWC and had some issues with ping for a day or so right after the most recent patch, but it stopped occurring right before the hotfix....so I have really no clue what could have caused it.

Was really disconcerting when it happened, because it would be the middle of a match, going from 35-40 ping to 350-400 without warning, on and off for a day. Knock on wood, it was a temporary thing.

[MaximusPayne]

I've been experiencing 300+ pings as of late as well, and yes I'm on TWC in Ohio, but its not been on every drop though. Below is my tracert results for what its worth...

====================================================================
(mwomercs.com)
3 35 ms 17 ms 27 ms cpe-65-24-48-1.columbus.res.rr.com [65.24.48.1]
4 27 ms 34 ms 34 ms tge7-4.pttpoh0104h.midwest.rr.com [24.95.87.101]
5 29 ms 22 ms 28 ms be26.clmcohib01r.midwest.rr.com [24.33.162.8]
6 30 ms 31 ms 28 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
7 47 ms 47 ms 33 ms bu-ether37.vinnva0510w-bcr00.tbone.rr.com [107.14.19.58]
8 35 ms 32 ms 43 ms 0.ae0.pr0.dca20.tbone.rr.com [107.14.19.65]
9 1449 ms * * 66.109.7.162
10 42 ms 43 ms 38 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 38 ms 37 ms 41 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
12 213 ms 197 ms 206 ms be100-101.nwk-1-a9.nj.us [178.32.135.18]
13 81 ms 90 ms 87 ms be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
14 72 ms 72 ms 73 ms bhs-g5-a9.qc.ca [198.27.73.231]
15 118 ms 71 ms 71 ms mwomercs.com [192.99.109.192]

Trace complete.

(google.com)
3 37 ms 27 ms 38 ms cpe-65-24-48-1.columbus.res.rr.com [65.24.48.1]
4 38 ms 27 ms 33 ms tge7-4.pttpoh0104h.midwest.rr.com [24.95.87.101]
5 28 ms 34 ms 25 ms be26.clmcohib01r.midwest.rr.com [24.33.162.8]
6 33 ms 31 ms 31 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
7 39 ms 84 ms 51 ms bu-ether27.vinnva0510w-bcr00.tbone.rr.com [107.14.19.14]
8 36 ms 32 ms 32 ms 0.ae1.pr0.dca20.tbone.rr.com [66.109.6.167]
9 38 ms 36 ms 38 ms 216.50.76.41
10 73 ms 92 ms 93 ms 216.156.116.202.ptr.us.xo.net [216.156.116.202]
11 50 ms 34 ms 41 ms 209.85.252.46
12 35 ms 39 ms 58 ms 209.85.143.112
13 57 ms 50 ms 37 ms 209.85.143.115
14 43 ms 37 ms 46 ms 209.85.143.108
15 46 ms 42 ms 43 ms 216.239.51.227
16 40 ms 44 ms 37 ms ord31s22-in-f4.1e100.net [216.58.216.228]

Trace complete.
==========================================================================

So far, its just been a MWO issue and I've just been putting my head down and playing through it. But it is wearing on me. If it keeps up, I'm probably gonna move on to other things until it gets resolved.

[Quicksilver Aberration]

Traceroute to a server when I got 200+ ping.

tracert 198.27.85.230
Tracing route to ns7000401.ip-198-27-85.net [198.27.85.230]
over a maximum of 30 hops:
  1	<1 ms	<1 ms	<1 ms  192.168.0.1
  2	20 ms	13 ms	14 ms  cpe-108-167-64-1.kc.res.rr.com [108.167.64.1]
  3	38 ms	27 ms	32 ms  tge0-0-1.kscdmo1501h.kc.rr.com [98.156.46.194]
  4	15 ms	 4 ms	14 ms  agg40.ksczmogn01r.kc.rr.com [98.156.43.156]
  5	31 ms	29 ms	29 ms  agg36.dllatxl301r.kc.rr.com [98.156.42.126]
  6	30 ms	28 ms	30 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.10
9.6.88]
  7	27 ms	28 ms	24 ms  0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
  8	44 ms	40 ms	41 ms  ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.
97]
  9	89 ms	85 ms	78 ms  if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5
]
10	82 ms	82 ms	76 ms  if-23-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
120]
11	88 ms	89 ms	 *	 if-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.
2]
12   101 ms	94 ms	96 ms  be100-152.chi-5-a9.il.us [198.27.73.69]
13	91 ms	84 ms	90 ms  be10-1218.bhs-g2-a9.qc.ca [198.27.73.89]
14	92 ms	94 ms	93 ms  bhs-s4-6k.qc.ca [198.27.73.146]
15   190 ms   192 ms   196 ms  ns7000401.ip-198-27-85.net [198.27.85.230]
Trace complete.

Traceroute to a server when I have a normal 70-90 ping.

tracert 198.27.85.228
Tracing route to ns7000399.ip-198-27-85.net [198.27.85.228]
over a maximum of 30 hops:
  1	<1 ms	<1 ms	<1 ms  192.168.0.1
  2	14 ms	16 ms	20 ms  cpe-108-167-64-1.kc.res.rr.com [108.167.64.1]
  3	32 ms	31 ms	31 ms  tge0-0-1.kscdmo1501h.kc.rr.com [98.156.46.194]
  4	14 ms	16 ms	15 ms  agg40.ksczmogn01r.kc.rr.com [98.156.43.156]
  5	35 ms	32 ms	29 ms  agg36.dllatxl301r.kc.rr.com [98.156.42.126]
  6	32 ms	29 ms	32 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.10
9.6.88]
  7	28 ms	47 ms	26 ms  0.ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
  8	38 ms	40 ms	38 ms  ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.
97]
  9	94 ms	 *	   85 ms  if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5
]
10	81 ms	80 ms	75 ms  if-23-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
120]
11	98 ms	90 ms	89 ms  if-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.
2]
12   117 ms   100 ms   104 ms  be100-152.chi-5-a9.il.us [198.27.73.69]
13	93 ms	90 ms	95 ms  be10-1218.bhs-g2-a9.qc.ca [198.27.73.89]
14   351 ms   334 ms   332 ms  bhs-s3-6k.qc.ca [198.27.73.142]
15	93 ms	99 ms	95 ms  ns7000399.ip-198-27-85.net [198.27.85.228]
Trace complete.

Edited by Quicksilver Kalasa, 20 February 2016 - 06:31 PM.

[Dagorlad13]

Remember that it could be a program like Windows Update or something downloading updates in the background that could cause intermittent lag spikes as well.

[Quicksilver Aberration]

IronClaws, on 25 February 2016 - 06:32 PM, said:

Remember that it could be a program like Windows Update or something downloading updates in the background that could cause intermittent lag spikes as well.

It isn't, I keep an eye through TS and through ping commands and the only wonky ping is in-game, and it is persistent for an entire match, and then is gone the next match (provided I don't hit the same server).

[Jeffrey Wilder]

Yup, bad graphic card drivers is also one of them.

Windows desktop can also cause problems with the game if the desktop crashes in memory.

[Dagorlad13]

My ping is much lower and more stable now that Time Warner is now Spectrum in my area.