180 replies to this topic

[Jon Cunningham]

High ping? Lots of lag?



Please post a tracert to 192.99.109.192.

Note if you're having the problem right now or only sometimes (if sometimes, try to get the tracert when you are having the lag.)



Also: pings of 2000+ are almost always from logging in and not being fully loaded into the map yet. Not usually network problems, just FYI.

How to perform a traceroute:

http://www.mediacoll...traceroute.html

[Jin Ma]

i'm seeing some light mechs rubberband a bunch. Saw 2 light mechs over 4 days or so

[LazyAmerican]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\lazy>tracert 192.99.109.192

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 8 ms s**tpc [0.0.0.0]
3 8 ms 8 ms 9 ms host-149-6-220-24-static.midco.net [24.220.6.149
]
4 10 ms 18 ms 7 ms host-116-6-220-24-static.midco.net [24.220.6.116
]
5 10 ms 19 ms 11 ms host-114-6-220-24-static.midco.net [24.220.6.114
]
6 33 ms 17 ms 22 ms host-18-19-220-24-static.midco.net [24.220.19.18
]
7 28 ms 30 ms 36 ms host-0-19-220-24-static.midco.net [24.220.19.0]

8 93 ms * 98 ms eqx.snj.ovh.net [206.223.116.193]
9 93 ms 86 ms 90 ms 198.27.73.249
10 * * 95 ms 198.27.73.186
11 104 ms 108 ms 104 ms 198.27.73.181
12 107 ms 103 ms 100 ms bhs-g2-6k.qc.ca [198.27.73.7]
13 106 ms 117 ms 120 ms 198.27.73.233
14 106 ms 110 ms 111 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\lazy>

[BigBucket]

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 192.168.0.1
3 9 ms 11 ms 10 ms cpe-184-59-224-1.new.res.rr.com [184.59.224.1]
4 10 ms 9 ms 8 ms tge7-6.applwi3002h.midwest.rr.com [24.164.233.29
]
5 16 ms 18 ms 18 ms tge1-3-0-1.gnfdwibb01r.midwest.rr.com [65.29.44.
14]
6 20 ms 19 ms 19 ms ae-6-0.cr0.chi10.tbone.rr.com [66.109.6.204]
7 * 15 ms 26 ms ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
8 16 ms 16 ms 15 ms chi-b21-link.telia.net [213.248.76.97]
9 40 ms 40 ms 41 ms nyk-bb2-link.telia.net [62.115.140.102]
10 63 ms 51 ms 44 ms nyk-b2-link.telia.net [213.155.130.30]
11 * * * Request timed out.
12 40 ms 42 ms 45 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 42 ms 41 ms 41 ms 198.27.73.231
14 40 ms 48 ms 40 ms mwomercs.com [192.99.109.192]

Trace complete.

[Nathan Foxbane]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 192.99.109.192

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 3063 ms 1 ms 1 ms 192.168.0.1
2 2 ms 1 ms 1 ms 192.168.1.254
3 46 ms 47 ms 48 ms ppp-69-229-211-254.dsl.renocs.pacbell.net [69.22
9.211.254]
4 58 ms 51 ms 51 ms 12.83.78.181
5 56 ms 71 ms 52 ms 12.122.149.133
6 55 ms 60 ms 58 ms 192.205.32.210
7 * 142 ms 169 ms ae-1-51.edge3.Newark1.Level3.net [4.69.156.11]
8 141 ms * 140 ms ae-1-51.edge3.Newark1.Level3.net [4.69.156.11]
9 * * * Request timed out.
10 144 ms 148 ms 142 ms bhs-g1-6k.qc.ca [198.27.73.205]
11 145 ms 145 ms 144 ms 198.27.73.231
12 144 ms 144 ms 143 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Windows\System32>

It has steadily crept up from 125 at the end of summer to averaging 141 with plenty of spikes.

[Vassago Rain]

My ping's not changed, but laser hit detection is completely broken. I can't harm anyone with lasers, but they can't harm me, either. Rubberbanding is super common this patch.

[Impyrium]

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 37 ms 37 ms 39 ms 253.2.2.123.network.m2core.net.au [123.2.2.253]

3 38 ms 38 ms 40 ms be2-v417.bsr02.melbpri.vic.m2core.net.au [123.2.
2.65]
4 38 ms 37 ms 40 ms Bundle-Ether18.lon77.melbourne.telstra.net [139.
130.198.249]
5 41 ms 41 ms 39 ms bundle-ether11.exi-core10.melbourne.telstra.net
[203.50.11.113]
6 54 ms 54 ms 57 ms bundle-ether12.chw-core10.sydney.telstra.net [20
3.50.11.124]
7 55 ms 54 ms 55 ms Bundle-ether17.oxf-gw2.sydney.telstra.net [203.5
0.13.70]
8 56 ms 55 ms 55 ms bundle-ether1.sydo-core01.sydney.reach.com [203.
50.13.38]
9 54 ms 54 ms 56 ms i-0-6-0-6.sydo-core02.bi.telstraglobal.net [202.
84.223.38]
10 198 ms 196 ms 199 ms i-0-2-0-4.1wlt-core01.bx.telstraglobal.net [202.
84.249.54]
11 196 ms 195 ms 195 ms i-0-4-0-7.eqla01.bi.telstraglobal.net [202.40.14
9.254]
12 195 ms 197 ms 195 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.
159.61.26]
13 * 272 ms 273 ms xe-1-0-0.miami15.mia.seabone.net [195.22.199.5]

14 270 ms 270 ms 270 ms xe-1-2-0.miami15.mia.seabone.net [195.22.199.193
]
15 287 ms 359 ms 286 ms mia-1-6k.fl.us [178.32.135.208]
16 * * * Request timed out.
17 293 ms 292 ms 291 ms bhs-g1-6k.qc.ca [198.27.73.205]
18 291 ms 289 ms 290 ms 198.27.73.231
19 289 ms 289 ms 294 ms mwomercs.com [192.99.109.192]

Trace complete.

Used to have 260-270, now it's quite unstable and jumping around 300-340.

[CocoaJin]

What's up with the time outs prior to [198.27.73.205]?

Edit:
Did a search for "bhs-g1-6k.qc.ca [198.27.73.205]". Came up with a lot chatter on various forums about these guys taking a dump and screwing up packets into Canada. Apparently you can go to these game forums, substitute MWO for the game title and see carbon copies of our complaints.

Edited by CocoaJin, 12 November 2014 - 08:31 PM.

[Wolfhound22]

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 11 ms 12 ms rd1cv-tge0-5-0-0-1.gv.shawcable.net [64.59.162.1
69]
4 14 ms 12 ms 11 ms 66.163.68.102
5 * * * Request timed out.
6 * * 783 ms snj-2-6k.ca.us [178.32.135.162]
7 78 ms 79 ms 69 ms 198.27.73.249
8 68 ms * 67 ms 198.27.73.151
9 * 85 ms 85 ms 198.27.73.173
10 86 ms 87 ms 86 ms bhs-g2-6k.qc.ca [198.27.73.7]
11 88 ms 87 ms 87 ms 198.27.73.233
12 86 ms 97 ms 87 ms mwomercs.com [192.99.109.192]

Trace complete.

[That Dawg]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\>tracert 192.99.109.192

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 10 ms 7 ms dynamic-acs-24-112-183-1.zoominternet.net [24.11
2.183.1]
3 23 ms 17 ms 13 ms dynamic-acs-72-23-10-245.zoominternet.net [72.23
.10.245]
4 219 ms 22 ms 228 ms te-8-2.car2.Pittsburgh3.Level3.net [4.49.110.69]

5 * 31 ms 27 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
6 * * * Request timed out.
7 35 ms 36 ms 38 ms bhs-g1-6k.qc.ca [198.27.73.205]
8 34 ms 36 ms 35 ms 198.27.73.231
9 33 ms 33 ms 41 ms mwomercs.com [192.99.109.192]

Trace complete.

[That Dawg]

protip when you are looking at that small dos window, right click with mouse chose "select all". Now, on they keyboard, press CTRL+C (that copies it)
then, in the window you type in here, press CTRL+P (that pastes it here)

dont be a target drone and remove all personal information, typically you'll it twice in the information

p.s. I saw a trace report in a forum years ago that had "C:\user\moms computer\tracert"

bwahahaha. yes, no mercy was shown

[Rasc4l]

Jon Cunningham, on 12 November 2014 - 04:31 PM, said:

Please post a tracert to 192.99.109.192.

I was told by Kaffeangst that he moved within US and while his ping remained the same (55-70 ms), the new location had much worse hit detection. To me, this sounds like a proof of concept that the problem is at your end although he blamed his new Internet provider. But maybe you could look into HSR that it's doing everything it's supposed to? I still can't get over the feeling that I had my best SRM hit experience during the time before HSR but maybe it's just in my head...

Another thing: It is a common experience that private matches have worse hit registeration than PUG matches. Is PGI committing less resources for them than for public matches? If the resources are the same, perhaps private matches should have more resources, because people who use them are the paying customers.


For what it's worth, here's my tracert:

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.176.1
2 1 ms <1 ms 2 ms gw32.a400.priv.bahnhof.se [46.59.3.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 2 ms 2 ms 2 ms a400-gw-c.bahnhof.net [46.59.117.78]
6 3 ms 3 ms 2 ms a400-gw.bahnhof.net [46.59.117.79]
7 3 ms 2 ms 2 ms sto-kn71.sto-mar-ar1.bahnhof.net [46.59.112.142]
8 12 ms 12 ms 12 ms sto-mar-ar1.sto-cr3.bahnhof.net [46.59.112.156]
9 12 ms 12 ms 12 ms sto-cr3.sto-cr1.bahnhof.net [46.59.112.162]
10 12 ms 12 ms 12 ms sto-cr1.mmo-cr1.bahnhof.net [85.24.151.154]
11 27 ms * * decix.routers.ovh.net [80.81.192.209]
12 30 ms 30 ms 30 ms sbg-g2-a9.fr.eu [91.121.128.125]
13 31 ms 31 ms 31 ms 37.187.36.155
14 * * * Request timed out.
15 117 ms 117 ms 117 ms mwomercs.com [192.99.109.192]

Trace complete.

[MadPanda]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2	 8 ms	 6 ms	 9 ms  10.235.0.1
  3    51 ms    16 ms	 8 ms  hel5-sr3.dnaip.fi [62.78.106.136]
  4    15 ms	 6 ms    10 ms  hel5-tr3.dnaip.fi [62.78.107.116]
  5	 8 ms    10 ms	 7 ms  hel1-tr2.dnaip.fi [62.78.107.124]
  6    20 ms    14 ms    15 ms  hel5-tr3.dnaip.fi [62.78.107.125]
  7    16 ms    16 ms    19 ms  rai1-tr1.dnaip.fi [62.78.107.13]
  8    15 ms    23 ms    21 ms  tuk2-sr1.dnaip.fi [62.78.107.174]
  9    18 ms    18 ms    18 ms  te0-7-0-2.ccr21.sto01.atlas.cogentco.com [149.6.
168.129]
 10    16 ms    18 ms    14 ms  level3.sto01.atlas.cogentco.com [130.117.14.6]
 11	 *	    *	    *	 Request timed out.
 12	 *	    *	    *	 Request timed out.
 13	 *	    *	    *	 Request timed out.
 14    51 ms    49 ms    67 ms  sbg-g2-a9.fr.eu [91.121.128.125]
 15    48 ms    49 ms    53 ms  37.187.36.155
 16	 *	    *	    *	 Request timed out.
 17   259 ms   261 ms   260 ms  mwomercs.com [192.99.109.192]

Trace complete.

This kind of ping for someone living in civilized eu country with high speed internet is unacceptable. You make me sad pgi.

[Jon Cunningham]

MadPanda, on 13 November 2014 - 09:27 AM, said:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
 
  1	<1 ms	<1 ms	<1 ms  192.168.0.1
  2	 8 ms	 6 ms	 9 ms  10.235.0.1
  3	51 ms	16 ms	 8 ms  hel5-sr3.dnaip.fi [62.78.106.136]
  4	15 ms	 6 ms	10 ms  hel5-tr3.dnaip.fi [62.78.107.116]
  5	 8 ms	10 ms	 7 ms  hel1-tr2.dnaip.fi [62.78.107.124]
  6	20 ms	14 ms	15 ms  hel5-tr3.dnaip.fi [62.78.107.125]
  7	16 ms	16 ms	19 ms  rai1-tr1.dnaip.fi [62.78.107.13]
  8	15 ms	23 ms	21 ms  tuk2-sr1.dnaip.fi [62.78.107.174]
  9	18 ms	18 ms	18 ms  te0-7-0-2.ccr21.sto01.atlas.cogentco.com [149.6.
168.129]
10	16 ms	18 ms	14 ms  level3.sto01.atlas.cogentco.com [130.117.14.6]
11	 *		*		*	 Request timed out.
12	 *		*		*	 Request timed out.
13	 *		*		*	 Request timed out.
14	51 ms	49 ms	67 ms  sbg-g2-a9.fr.eu [91.121.128.125]
15	48 ms	49 ms	53 ms  37.187.36.155
16	 *		*		*	 Request timed out.
17   259 ms   261 ms   260 ms  mwomercs.com [192.99.109.192]
 
Trace complete.

This kind of ping for someone living in civilized eu country with high speed internet is unacceptable. You make me sad pgi.

Yeah, this one is weird.

I get 172 when pinging you - could you do me a favour and tracert the two following IPs:

192.99.40.103
209.15.227.106

[Coolant]

sometimes lose FPS when in Thermal....

Deleting the files in the Shader folders seems to fix the problem sometimes....

[MadPanda]

Jon Cunningham, on 13 November 2014 - 12:08 PM, said:

Yeah, this one is weird.

I get 172 when pinging you - could you do me a favour and tracert the two following IPs:

192.99.40.103
209.15.227.106

Sure.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

Tracing route to ns7000224.ip-192-99-40.net [192.99.40.103]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2	 7 ms	 7 ms	 7 ms  10.235.0.1
  3	 8 ms	 7 ms    35 ms  hel5-sr3.dnaip.fi [62.78.106.136]
  4	 6 ms	 7 ms	 7 ms  hel5-tr3.dnaip.fi [62.78.107.116]
  5	 6 ms    40 ms    33 ms  hel1-tr2.dnaip.fi [62.78.107.124]
  6    15 ms    15 ms    15 ms  hel5-tr3.dnaip.fi [62.78.107.125]
  7    15 ms    15 ms    15 ms  rai1-tr1.dnaip.fi [62.78.107.13]
  8    20 ms    14 ms    15 ms  tuk2-sr1.dnaip.fi [62.78.107.174]
  9    15 ms    17 ms    14 ms  te0-0-0-7.ccr21.sto01.atlas.cogentco.com [149.6.
168.13]
 10    15 ms    15 ms    15 ms  level3.sto01.atlas.cogentco.com [130.117.14.6]
 11	 *	    *	    *	 Request timed out.
 12	 *	    *	    *	 Request timed out.
 13	 *	    *	    *	 Request timed out.
 14    50 ms    51 ms    53 ms  rbx-g2-a9.fr.eu [178.33.100.250]
 15	 *	    *	    *	 Request timed out.
 16	 *	    *	    *	 Request timed out.
 17   259 ms   259 ms   259 ms  bhs-g2-6k.qc.ca [198.27.73.207]
 18   264 ms   270 ms   267 ms  bhs-s3-6k.qc.ca [198.27.73.142]
 19   256 ms   256 ms   261 ms  ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.

Tracing route to 209.15.227.106 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2	 6 ms	 6 ms	 5 ms  10.235.0.1
  3	 6 ms	 7 ms	 7 ms  hel5-sr3.dnaip.fi [62.78.106.136]
  4    25 ms    12 ms    12 ms  hel5-tr3.dnaip.fi [62.78.107.116]
  5	 9 ms	 7 ms	 7 ms  hel1-tr2.dnaip.fi [62.78.107.124]
  6    16 ms    15 ms    16 ms  hel5-tr3.dnaip.fi [62.78.107.125]
  7    16 ms    15 ms    15 ms  rai1-tr1.dnaip.fi [62.78.107.13]
  8    27 ms    17 ms    17 ms  tuk3-sr1.dnaip.fi [62.78.107.176]
  9    15 ms    15 ms    15 ms  ae1-107.stk10.ip4.gtt.net [77.67.72.177]
 10   132 ms   131 ms   138 ms  xe-8-2-0.tor10.ip4.gtt.net [141.136.107.98]
 11   140 ms   141 ms   143 ms  peer1-gw.ip4.gtt.net [77.67.68.10]
 12	 *	    *	    *	 Request timed out.
 13   145 ms   145 ms   145 ms  209.15.227.106

Trace complete.

[Captain Stiffy]

When the game was older I had a ping of an EIGHT in game. 8. It is generally now around 90-110. I'm moving soon but here's my trace from Southwest Ohio - this might help you to diagnose what changed between hosts?

This has some packet drops on it. I ran many traces and had those problems on and off with those hosts that are listed here as dropped. Not sure on who's end. I have very fast high quality fiber internet.

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.200.1
2 4 ms 4 ms 1 ms MH1-DSL-208-102-236-1.fuse.net [208.102.236.1]
3 2 ms 1 ms 1 ms 172.17.74.18
4 2 ms 2 ms 1 ms EV-ZT-1.EVE2.core.fuse.net [216.68.14.58]
5 40 ms 40 ms 40 ms EVE2.EVE1.core.fuse.net [216.68.14.44]
6 40 ms 39 ms 39 ms 216.68.14.91
7 46 ms 40 ms * eqx.dal.ovh.net [206.223.118.119]
8 * * * Request timed out.
9 76 ms 75 ms * 198.27.73.179
10 79 ms 78 ms 77 ms bhs-g2-6k.qc.ca [198.27.73.7]
11 78 ms 78 ms 78 ms 198.27.73.233
12 77 ms 77 ms 78 ms mwomercs.com [192.99.109.192]

[Jon Cunningham]

BigBucket, on 12 November 2014 - 05:24 PM, said:

198.27.73.231 14 40 ms 48 ms 40 ms mwomercs.com [192.99.109.192] Trace complete.

No network path issues here - 40 ms seems pretty good.

You may be having other issues if you're experiencing in game lag.

[Jon Cunningham]

Captain Stiffy, on 13 November 2014 - 01:44 PM, said:

When the game was older I had a ping of an EIGHT in game. 8. It is generally now around 90-110. I'm moving soon but here's my trace from Southwest Ohio - this might help you to diagnose what changed between hosts? This has some packet drops on it. I ran many traces and had those problems on and off with those hosts that are listed here as dropped. Not sure on who's end. I have very fast high quality fiber internet. Tracing route to mwomercs.com [192.99.109.192] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.200.1 2 4 ms 4 ms 1 ms MH1-DSL-208-102-236-1.fuse.net [208.102.236.1] 3 2 ms 1 ms 1 ms 172.17.74.18 4 2 ms 2 ms 1 ms EV-ZT-1.EVE2.core.fuse.net [216.68.14.58] 5 40 ms 40 ms 40 ms EVE2.EVE1.core.fuse.net [216.68.14.44] 6 40 ms 39 ms 39 ms 216.68.14.91 7 46 ms 40 ms * eqx.dal.ovh.net [206.223.118.119] 8 * * * Request timed out. 9 76 ms 75 ms * 198.27.73.179 10 79 ms 78 ms 77 ms bhs-g2-6k.qc.ca [198.27.73.7] 11 78 ms 78 ms 78 ms 198.27.73.233 12 77 ms 77 ms 78 ms mwomercs.com [192.99.109.192]

I should be able to get you fixed a bit. I don't think you'll see 8 again (the DC is no longer in Toronto) but there is no good reason for your traffic to go south to Texas before coming back north to Canada.

[Abivard]

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 8 ms 8 ms 8 ms d179-68-1-185.evv.wideopenwest.com [68.179.185.1
]
2 8 ms 8 ms 8 ms 172.31.55.129
3 11 ms 8 ms 8 ms user-75-76-127-176.knology.net [75.76.127.176]
4 20 ms 21 ms 21 ms 76-73-169-78.knology.net [76.73.169.78]
5 * * * Request timed out.
6 * * * Request timed out.
7 46 ms 48 ms 46 ms bhs-g1-6k.qc.ca [198.27.73.205]
8 46 ms 47 ms 47 ms 198.27.73.231
9 48 ms 46 ms 48 ms mwomercs.com [192.99.109.192]

Trace complete.