180 replies to this topic

[Jeffries]

It looks like the hops after 213.155.130.28 are consistently the problem, possibly to Newark based on some reports. I've checked again this morning, and I still have the same problems:

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

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 6 ms L100.ALBYNY-VFTTP-07.verizon-gni.net [96.236.37.1]
3 7 ms 6 ms 9 ms G0-0-3-1.ALBYNY-LCR-22.verizon-gni.net [100.41.199.89]
4 22 ms 22 ms 21 ms 130.81.162.136
5 23 ms 21 ms 21 ms 0.so-6-0-0.XT2.NYC4.ALTER.NET [152.63.17.97]
6 20 ms 29 ms 34 ms TenGigE0-7-0-0.GW5.NYC4.ALTER.NET [152.63.17.62]
7 17 ms 17 ms 16 ms teliasonera-gw.customer.alter.net [152.179.163.178]
8 17 ms 16 ms 16 ms nyk-bb1-link.telia.net [213.155.131.136]
9 16 ms 17 ms 16 ms nyk-b2-link.telia.net [213.155.130.28]
10 * * * Request timed out.
11 41 ms 41 ms 42 ms bhs-g1-6k.qc.ca [198.27.73.205]
12 47 ms 53 ms 47 ms 198.27.73.231
13 43 ms 41 ms 41 ms mwomercs.com [192.99.109.192]

Trace complete.

[Horace83]

Quote

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.



Routenverfolgung zu nyk-b2-link.telia.net [213.155.130.28] über maximal 30 Absch
nitte:

1 1 ms 1 ms 1 ms 192.168.178.1
2 29 ms 29 ms 37 ms rdsl-stgt-de81.nw.mediaways.net [213.20.56.140]

3 24 ms 23 ms 25 ms xmwc-stgt-de04-chan-23.nw.mediaways.net [195.71.
229.205]
4 23 ms 25 ms 23 ms ae1-0.02.rmwc.99.str.de.net.telefonica.de [62.53
.2.82]
5 26 ms 26 ms 26 ms so-3-3-0-0.01.rmwc.99.fra.de.net.telefonica.de [
62.53.1.71]
6 26 ms 24 ms 25 ms 213.140.50.124
7 * * * Zeitüberschreitung der Anforderung.
8 97 ms 88 ms 142 ms ffm-bb1-link.telia.net [62.115.142.194]
9 189 ms 140 ms 177 ms nyk-bb1-link.telia.net [213.155.131.145]
10 171 ms 170 ms 165 ms nyk-bb1-link.telia.net [213.155.135.5]
11 147 ms 162 ms 155 ms nyk-b2-link.telia.net [213.155.130.28]

Ablaufverfolgung beendet.



Routenverfolgung zu mwomercs.com [192.99.109.192] über maximal 30 Abschnitte:

1 1 ms 4 ms 2 ms 192.168.178.1
2 26 ms 49 ms 28 ms rdsl-stgt-de81.nw.mediaways.net [213.20.56.140]

3 24 ms 26 ms 26 ms xmwc-stgt-de04-chan-23.nw.mediaways.net [195.71.
229.205]
4 91 ms 25 ms 23 ms ae1-0.02.rmwc.99.str.de.net.telefonica.de [62.53
.2.82]
5 28 ms 27 ms 29 ms xe-6-1-0-0.01.rmwc.99.fra.de.net.telefonica.de [
62.53.1.75]
6 34 ms 34 ms 35 ms xmwc-amsd-nl01-chan-1.nw.mediaways.net [195.71.2
12.238]
7 * * * Zeitüberschreitung der Anforderung.
8 53 ms 55 ms 68 ms rbx-g1-a9.fr.eu [178.33.100.238]
9 55 ms 83 ms 52 ms 37.187.36.131
10 * * * Zeitüberschreitung der Anforderung.
11 188 ms 165 ms 160 ms mwomercs.com [192.99.109.192]

Ablaufverfolgung beendet.

nothing new here from me

Country: Germany
DSL16.000

edit1: now i cannot even login no more - "unknown failure". Running repair tool now. This is the state right before the server migration. All other MMOs run smoothly...

Edited by Horace83, 26 November 2014 - 12:02 PM.

[Jon Cunningham]

Aphoticus, on 18 November 2014 - 11:01 AM, said:

Tracing route to mwomercs.com [192.99.109.192] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Pennsylvania, USA 2 28 ms 28 ms 28 ms 10.29.39.1 3 30 ms 29 ms 29 ms G3-0-5-2213.SCTNPA-LCR-02.verizon-gni.net [130.8 1.198.26] 4 42 ms 43 ms 41 ms G13-0-0.SCTNPA-LCR-01.verizon-gni.net [130.81.15 1.34] 5 73 ms 34 ms 34 ms xe-4-1-8-0.NWRK-BB-RTR1.verizon-gni.net [130.81. 209.194] 6 * * * Request timed out. 7 72 ms 59 ms 59 ms 2.ae1.XT1.NYC4.ALTER.NET [140.222.228.119] 8 43 ms 52 ms 42 ms TenGigE0-6-0-5.GW5.NYC4.ALTER.NET [152.63.17.118 ] 9 42 ms 44 ms 42 ms teliasonera-gw.customer.alter.net [152.179.163.1 78] 10 42 ms 42 ms 42 ms nyk-bb2-link.telia.net [80.91.254.15] 11 42 ms 41 ms 42 ms nyk-b2-link.telia.net [213.155.130.30] 12 * * * Request timed out. 13 63 ms 63 ms 64 ms bhs-g1-6k.qc.ca [198.27.73.205] 14 63 ms 63 ms 64 ms 198.27.73.231 15 62 ms 63 ms 63 ms mwomercs.com [192.99.109.192] Trace complete. Just curious, am I hopping the Atlantic then coming back (Teliasonera)? Wait, is 'bhs-g1-6k.qc.ca [198.27.73.205]' in France? I am in PA, USA, FYI, and I still experience lag spikes, HSR issues, and very, very low frame rates (15-25 most of the time; can spike high on fresh boot of machines, but after a game or two, I am back to high teens, low twenties). I know the machine is not ideal, but on low, and all settings on the graphics card (updated drivers) and what-not, I would expect at least high twenties, low 30's like almost every other game I play on this machine. But, been doing the same thing since open beta started, so good luck...still playing.

No, you're not going to France. 198.27.73.205 is one of our core routers in Montreal.

If you look at your traceroute, it would appear that the first 30 ms of delay come from the first hop from your systems to your ISP. From your ISP, it only takes ~31ms to reach our datacenter, which is what I would expect for PA to Montreal, Canada.

Lynx7725, on 20 November 2014 - 10:41 AM, said:

In case this is useful:

>tracert 192.99.40.103

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

1 13 ms 15 ms 20 ms 182.55.225.3
2 40 ms 56 ms 14 ms an-tl-br05.starhub.net.sg [183.90.44.58]
3 12 ms 7 ms 33 ms six2-ultl-int01.starhub.net.sg [183.90.44.1]
4 168 ms 280 ms 163 ms any2ix.coresite.com [206.72.210.214]
5 * * * Request timed out.
6 * * * Request timed out.
7 251 ms 246 ms 259 ms bhs-s3-6k.qc.ca [198.27.73.142]
8 276 ms 271 ms 275 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.

>tracert 209.15.227.106

Tracing route to 209.15.227.106 over a maximum of 30 hops

1 13 ms 5 ms 5 ms 182.55.225.3
2 12 ms 5 ms 5 ms an-tl-br05.starhub.net.sg [183.90.44.58]
3 20 ms 6 ms 6 ms 183.90.44.5
4 6 ms 9 ms 7 ms 203.117.36.29
5 8 ms 6 ms 8 ms six2-ultl-int01.starhub.net.sg [203.117.34.58]
6 185 ms 212 ms 172 ms any2ix.coresite.com [206.72.210.79]
7 179 ms 240 ms 193 ms 10ge.xe-2-3-0.lax-600w-sbcor-2.peer1.net [216.187.124.121]
8 221 ms 243 ms 211 ms 10ge-xe-0-0-1.dal-eqx-cor-1.peer1.net [216.187.88.131]
9 242 ms 245 ms 247 ms 10ge-ten4-0-0.chi-eqx-dis-1.peer1.net [216.187.124.74]
10 331 ms 453 ms * 10ge.xe-1-0-0.tor-1yg-cor-1.peer1.net [216.187.114.142]
11 245 ms 255 ms 253 ms 10ge.xe-0-1-1.tor-20p1ops-dis-2.peer1.net [216.187.114.190]
12 255 ms 257 ms 277 ms 209.15.227.106

Trace complete.

About what we would expect for Singapore, currently. Good to see that the ping is under 300ms though.

Crotch RockIt, on 20 November 2014 - 04:18 PM, said:

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 1 ms 1 ms 1 ms 192.168.43.1 2 * * * Request timed out. 3 66 ms 33 ms 76 ms 50.sub-69-83-102.myvzw.com [69.83.102.50] 4 * 79 ms 78 ms 241.sub-69-83-102.myvzw.com [69.83.102.241] 5 72 ms 79 ms 77 ms 17.sub-69-83-102.myvzw.com [69.83.102.17] 6 72 ms 82 ms 76 ms 194.sub-69-83-102.myvzw.com [69.83.102.194] 7 75 ms 78 ms 81 ms 64.sub-69-83-97.myvzw.com [69.83.97.64] 8 * * * Request timed out. 9 49 ms 29 ms 39 ms 103.sub-69-83-98.myvzw.com [69.83.98.103] 10 * 51 ms 55 ms TenGigE0-0-0-0.GW9.HOU7.ALTER.NET [152.179.94.253] 11 62 ms 57 ms 59 ms 0.xe-4-1-6.XL4.DFW7.ALTER.NET [152.63.97.70] 12 56 ms 54 ms 53 ms TenGigE0-5-2-0.GW4.DFW13.ALTER.NET [152.63.101.66] 13 71 ms 70 ms 64 ms teliasonera-gw.customer.alter.net [63.65.123.46] 14 103 ms 99 ms 99 ms nyk-bb2-link.telia.net [213.155.137.28] 15 92 ms 98 ms 100 ms nyk-b2-link.telia.net [213.155.130.30] 16 * * * Request timed out. 17 116 ms 98 ms 100 ms bhs-g1-6k.qc.ca [198.27.73.205] 18 104 ms 94 ms 95 ms 198.27.73.231 19 112 ms 91 ms 107 ms mwomercs.com [192.99.109.192] Trace complete. I periodically get severe lagging where my ping jumps up anywhere from several hundred to several thousand ms. When my ping is stable and the game is working properly, my ping is in the 90-120 range. Sometimes I have multiple games in a row that are almost unplayable, with moonwalking mechs and rubberbanding.

It appears that you have 50 ping before you even get off the Verizon network. Might want to check in with your ISP on that one.

Grey Ghost, on 23 November 2014 - 05:07 PM, said:

Pretty sure I must be experiencing some packet loss. I miss the old server location... My connection was always very stable back then, and about 20ms lower.

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
 
  1	 1 ms	 1 ms	<1 ms  homeportal [192.168.1.254]
  2	 *		*		*	 Request timed out.
  3	22 ms	20 ms	21 ms  71.144.129.22
  4	24 ms	24 ms	22 ms  12.83.86.133
  5	27 ms	27 ms	27 ms  gar26.dlstx.ip.att.net [12.123.16.85]
  6	 *		*		*	 Request timed out.
  7   157 ms   157 ms	 *	 ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
  8   155 ms   156 ms	 *	 ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
  9	 *		*		*	 Request timed out.
10	89 ms	89 ms	88 ms  bhs-g1-6k.qc.ca [198.27.73.205]
11	89 ms	89 ms	89 ms  198.27.73.231
12	89 ms	89 ms	89 ms  mwomercs.com [192.99.109.192]

What's up with Newark?

Packet loss is perfectly normal - remember, traceroute pings each router in succession. Sometimes the router says "why the hell are you pinging me? I'm not a webserver and I have important shit to do," and starts dropping ping packets directed to itself.

Newark is one of our major points of contact with much of the US. Also Chicago.

affman67, on 20 November 2014 - 09:05 PM, said:

Tracing route to mwomercs.com [192.99.109.192] over a maximum of 30 hops: 1 7 ms 7 ms 6 ms 10.3.128.1 2 6 ms 7 ms 8 ms ip68-1-11-89.at.at.cox.net [68.1.11.89] 3 8 ms 7 ms 8 ms ip68-1-11-212.at.at.cox.net [68.1.11.212] 4 48 ms 64 ms 65 ms 68.1.2.121 5 24 ms 25 ms * dal-1-6k.tx.us [198.27.73.214] 6 221 ms 217 ms * dal-2-6k.tx.us [178.32.135.175] 7 * * * Request timed out. 8 61 ms 61 ms * 198.27.73.181 9 77 ms 76 ms 83 ms bhs-g2-6k.qc.ca [198.27.73.7] 10 76 ms 76 ms 76 ms 198.27.73.233 11 63 ms 62 ms 62 ms mwomercs.com [192.99.109.192]


Trace complete. Just for fun,NW Florida 62 to 70 ping most the time,game runs ok need better comp only a 4Ghz 4core phenom2 amd.

Glad to hear it's running smoothly.

[Jon Cunningham]

Soggy, I'll reply to you soon. Thanks for the information and troubleshooting you've done so far.

[Bluemaxx]

Here is my tracert result, location is Sydney Australia. Hit reg and lag have been getting worse then normal (for someone with 250ms ping), had a game yesterday where I was unable to hit a mech that we standing still while i was moving slowly (64kph) towards the target.
Hope this helps you guys out.

Tracing route to mediacollege.com [69.72.153.253]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BoB.iiNet [10.1.1.1]
2 19 ms 19 ms 18 ms nexthop.nsw.iinet.net.au [203.215.17.248]
3 20 ms 19 ms 19 ms te1-1.syd-ult-bdr1.iinet.net.au [203.215.16.22]

4 18 ms 35 ms 19 ms ae6.cr1.syd7.on.ii.net [150.101.33.114]
5 30 ms 19 ms 19 ms ae5.br1.syd7.on.ii.net [150.101.33.50]
6 171 ms 171 ms 171 ms te0-1-1-2.br1.sjc2.on.ii.net [150.101.33.193]
7 173 ms 174 ms 175 ms sl-st31-sj-.sprintlink.net [144.232.191.193]
8 172 ms 171 ms 171 ms 144.232.8.194
9 167 ms 167 ms 167 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.105]
10 172 ms 172 ms 173 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28.33]
11 210 ms 212 ms 210 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
12 246 ms 246 ms 246 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
13 242 ms 258 ms 257 ms be2114.ccr41.jfk02.atlas.cogentco.com [66.28.4.201]
14 242 ms 243 ms 242 ms be2056.ccr21.jfk10.atlas.cogentco.com [154.54.44.218]
15 246 ms 246 ms 246 ms 38.122.228.202
16 270 ms 269 ms 270 ms 50.60.1.251
17 251 ms 250 ms 251 ms spock.mediacollege.com [69.72.153.253]

Trace complete.

Edited by Bluemaxx, 26 November 2014 - 01:47 PM.

[Zordicron]

Jon Cunningham, on 26 November 2014 - 01:12 PM, said:

Soggy, I'll reply to you soon. Thanks for the information and troubleshooting you've done so far.

Any word on my Frontiernet woes Jon?

Although if you don't want to touch it with a ten foot pole I wouldn't blame you.

[SoggyGorilla]

Jon Cunningham, on 26 November 2014 - 01:12 PM, said:

Soggy, I'll reply to you soon. Thanks for the information and troubleshooting you've done so far.

[That Dawg]

Quote

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

C:\Users\>tracert 192.99.109.192.

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

1 1 ms 1 ms <1 ms 192.168.1.1
2 221 ms * 135 ms dynamic-acs-24-112-183-1.zoominternet.net [24.11
2.183.1]
3 263 ms 191 ms 123 ms dynamic-acs-72-23-10-245.zoominternet.net [72.23
.10.245]
4 74 ms 125 ms 191 ms te-8-2.car2.Pittsburgh3.Level3.net [4.49.110.69]

5 354 ms * * ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
6 * * * Request timed out.
7 229 ms 345 ms 393 ms bhs-g1-6k.qc.ca [198.27.73.205]
8 349 ms 427 ms 395 ms 198.27.73.231
9 332 ms 367 ms 373 ms mwomercs.com [192.99.109.192]

Trace complete.

lots of lag tonight
mechs lurching from point to point

I'm in North Ohio

[Ataboy]

You will see in my previous posts in this thread that I had a routing that was putting me through nyc and newark where there were problems. I have had my ISP change that so that I now go from Toronto to Montreal. But the following tracert and ping shows a problem at your end into the DC and on the game server.

11/27/2014 8:28pm eastern
Tracing route to 192.99.109.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 10 ms 8 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 8 ms 8 ms 8 ms 216.254.131.129
4 37 ms * * gw-ovh.torontointernetxchange.net [206.108.34.189]
5 15 ms * 71 ms mtl-2-6k.qc.ca [178.32.135.71]
6 44 ms 20 ms 16 ms bhs-g1-6k.qc.ca [198.27.73.5]
7 149 ms 32 ms 24 ms 198.27.73.231
8 521 ms 66 ms 17 ms 192.99.109.129
Trace complete.

ping -n 25 192.99.109.129
Pinging 192.99.109.129 with 32 bytes of data:
Reply from 192.99.109.129: bytes=32 time=233ms TTL=57
Reply from 192.99.109.129: bytes=32 time=167ms TTL=57
Reply from 192.99.109.129: bytes=32 time=167ms TTL=57
Reply from 192.99.109.129: bytes=32 time=31ms TTL=57
Reply from 192.99.109.129: bytes=32 time=133ms TTL=57
Reply from 192.99.109.129: bytes=32 time=789ms TTL=57
Reply from 192.99.109.129: bytes=32 time=281ms TTL=57
Reply from 192.99.109.129: bytes=32 time=455ms TTL=57
Reply from 192.99.109.129: bytes=32 time=213ms TTL=57
Reply from 192.99.109.129: bytes=32 time=454ms TTL=57
Reply from 192.99.109.129: bytes=32 time=16ms TTL=57
Reply from 192.99.109.129: bytes=32 time=1376ms TTL=57
Reply from 192.99.109.129: bytes=32 time=295ms TTL=57
Reply from 192.99.109.129: bytes=32 time=16ms TTL=57
Reply from 192.99.109.129: bytes=32 time=22ms TTL=57
Reply from 192.99.109.129: bytes=32 time=486ms TTL=57
Reply from 192.99.109.129: bytes=32 time=474ms TTL=57
Reply from 192.99.109.129: bytes=32 time=112ms TTL=57
Reply from 192.99.109.129: bytes=32 time=762ms TTL=57
Reply from 192.99.109.129: bytes=32 time=731ms TTL=57
Reply from 192.99.109.129: bytes=32 time=95ms TTL=57
Reply from 192.99.109.129: bytes=32 time=309ms TTL=57
Reply from 192.99.109.129: bytes=32 time=1102ms TTL=57
Reply from 192.99.109.129: bytes=32 time=527ms TTL=57
Reply from 192.99.109.129: bytes=32 time=124ms TTL=57

Ping statistics for 192.99.109.129:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 1376ms, Average = 374ms

[Captain Stiffy]

Having switched to wireless (no option and I have a powerful expansion card with a strong signal) I constantly get desyncs when playing and EVERY. SINGLE. TIME. two mechs collide I get a desync.

[Boozer]

It appears this trace has hops in Europe from the US? Huge increase in ping time from when SprinLlink hands off at a shared tenant site in Chicago...

Tracing route to mwomercs.com [192.99.109.192]
 
over a maximum of 30 hops:
 
  1	 1 ms	<1 ms	<1 ms  192.168.2.1
  2	28 ms	27 ms	27 ms  services-router-a.st-tel.net [208.84.76.2]
  3	28 ms	27 ms	27 ms gateway-router.st-tel.net 208.84.76.1]
  4	36 ms	35 ms	35 ms sl-gw16-kc-14-0-1.sprintlink.net [160.81.245.133]
 
  5	37 ms	37 ms	37 ms  sl-crs1-kc-0-5-0-0.sprintlink.net [144.232.11.152]
  6	48 ms	50 ms	47 ms  144.232.11.233
  7	46 ms	45 ms	46 ms  sl-st21-chi-12-0-0.sprintlink.net [144.232.19.142]
  8   327 ms   326 ms   311 ms  62.156.128.145
  9   386 ms   406 ms   414 ms  217.239.40.234
10	 *	  428 ms   415 ms  fra-1-6k.de.euf [94.23.122.153]
11   398 ms   420 ms   420 ms  fsbg-g2-a9.fr.euf [91.121.128.82]
12   404 ms   419 ms   416 ms  37.187.36.155
13	 *		*		*	 Request timed out.
14   414 ms   395 ms   392 ms  mwomercs.com [192.99.109.192]
 
 
Trace complete.

192.99.109.192 is in a /25 network and Sprintlink hands off to Deutsche Telekom AG (AS 3320) following the 192.99.0.0/16 route in Chicago and a huge spike begins. Maybe just a high circuit utilization between the two ISP's there?

 
Sprint Source Region: Kansas City, MO (sl-gw16-kc)
Performing: Show Route
BGP routing table entry for 192.99.0.0/16, version 386597122
Bestpath Modifiers: deterministic-med
Paths: (2 available, best #1)
  Advertised to update-groups:
	 3		  7		  10		 11		
  3320 16276
	144.228.241.248 (metric 118) from 144.228.241.70 (144.228.241.70)
	  Origin IGP, metric 4294967294, localpref 90, valid, internal, best
	  Community: 1239:666 1239:667 1239:1000 1239:1004
	  Originator: 144.228.241.248, Cluster list: 144.228.241.70, 144.228.243.241
  3320 16276
	144.228.241.248 (metric 118) from 144.228.241.71 (144.228.241.71)
	  Origin IGP, metric 4294967294, localpref 90, valid, internal
	  Community: 1239:666 1239:667 1239:1000 1239:1004
	  Originator: 144.228.241.248, Cluster list: 144.228.241.71, 144.228.243.241

Edited by Boozer, 27 November 2014 - 07:19 PM.

[AztecD]

C:\>tracert 192.99.109.192

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

1 2 ms 1 ms 2 ms 192.168.1.254
2 18 ms 18 ms 18 ms 200.76.252.33.ded.telnor.net [200.76.252.33]
3 29 ms 18 ms 19 ms 200.76.250.34.ded.telnor.net [200.76.250.34]
4 23 ms 22 ms * bup-bcn-piopico-23-tge0-0-0-6.uninet.net.mx [201
.125.22.114]
5 27 ms 22 ms 23 ms bb-la-grand-5-tge0-13-0-8.uninet.net.mx [201.125
.22.34]
6 79 ms 63 ms 60 ms xe-9-1-0.edge2.LosAngeles9.Level3.net [4.53.230.
197]
7 * * 90 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * 114 ms bhs-g1-6k.qc.ca [198.27.73.205]
11 97 ms 96 ms 96 ms 198.27.73.231
12 109 ms 108 ms 108 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\>

[KodiakGW]

C:\Users\Brian>tracert 192.99.109.192

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

1 * * * Request timed out.
2 9 ms 7 ms 8 ms 68.85.142.53
3 13 ms 15 ms 15 ms be-27-ar01.chartford.ct.hartford.comcast.net [68
.86.231.157]
4 19 ms 19 ms 20 ms 162.151.53.161
5 24 ms 23 ms 23 ms te-0-0-0-11-cr01.losangeles.ca.ibone.comcast.net
[68.86.90.217]
6 22 ms 23 ms 23 ms he-0-13-0-1-pe03.111eighthave.ny.ibone.comcast.n
et [68.86.85.190]
7 46 ms * 46 ms 198.27.73.61
8 44 ms * 45 ms nwk-1-6k.nj.us [178.32.135.57]
9 48 ms 47 ms 48 ms bhs-g1-6k.qc.ca [198.27.73.205]
10 49 ms 48 ms 49 ms 198.27.73.231
11 46 ms 47 ms 48 ms mwomercs.com [192.99.109.192]

Trace complete.

48ms not bad. But, losangeles.ca.ibone.comcast.net to ny.ibone.comcast.net
??
Comcast Business - hit registration issues. Just had a round nailing a legged spider in the back with 2CLPL and CUAC10 (2 taps) = barely any noticeable damage.

[Obiken]

Here's my tracert from Norway, it looks about what I'd expect and not that much different than before patch. But it was taken during a game where I was down to 3-5 fps, and I had no issues playing before.

Sporer rute til mwomercs.com [192.99.109.192]
over maksimalt 30 hopp:

1 1 ms 1 ms 1 ms FJELLGEITENE [192.168.1.1]
2 8 ms 8 ms 7 ms 10.195.64.1
3 11 ms 8 ms 9 ms 193.212.177.233
4 52 ms 48 ms 49 ms ti0300c360-ae45-0.ti.telenor.net [146.172.101.12
1]
5 57 ms 51 ms 49 ms ti3003c400-ae6-0.ti.telenor.net [146.172.99.245]

6 48 ms 52 ms 48 ms ti9002b400-ae0-0.ti.telenor.net [146.172.105.14]

7 * * * Forespørsel avbrutt.
8 56 ms 56 ms 54 ms rbx-g1-a9.fr.eu [91.121.215.145]
9 54 ms 57 ms 53 ms 37.187.36.131
10 * * * Forespørsel avbrutt.
11 134 ms 138 ms 134 ms mwomercs.com [192.99.109.192]

[Kahoumono]

I find myself getting delay damage constantly, I don't actually know when I've been hit. I go from yellow armor to cored without seeing myself take hits. And I never know whether I am actually dealing any damage. Sad to say the gameplay was better from Hong Kong 6 months ago when I was being disconnected from 1/3 of the games.

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 6 ms 6 ms 7 ms 217-168-61-169.static.cablecom.ch [217.168.61.169]
4 9 ms 7 ms 7 ms 84.116.202.225
5 9 ms 8 ms 10 ms ch-zrh01b-ra1-ae-9-0.aorta.net [84.116.134.22]
6 8 ms * 8 ms zur-1-6k.ch.eu [91.121.131.61]
7 * 16 ms * fra-5-6k.fr.eu [94.23.122.145]
8 17 ms 18 ms 18 ms sbg-g2-a9.fr.eu [91.121.128.82]
9 20 ms 19 ms 18 ms 37.187.36.155
10 * * * Request timed out.
11 109 ms 111 ms 111 ms mwomercs.com [192.99.109.192]

Trace complete.

[Kelvin Casing]

Some matches my ping is 80-90, some matches it is 500+. Seems not to be dependent on the map! Sometimes just rejoining will take the ping back to 80-90.

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

1 1 ms <1 ms 2 ms DD-WRT [192.168.1.1]
2 17 ms 13 ms 14 ms 213.1.112.25
3 15 ms 13 ms 14 ms 213.1.114.110
4 15 ms 14 ms 13 ms 213.1.67.134
5 15 ms 15 ms 19 ms 87.237.20.138
6 * * * Request timed out.
7 19 ms 19 ms 18 ms rbx-g2-a9.fr.eu [91.121.131.177]
8 20 ms 20 ms 23 ms 37.187.36.133
9 * * * Request timed out.
10 148 ms 142 ms 100 ms mwomercs.com [192.99.109.192]

Trace complete.

Edited by Kelvin Casing, 28 November 2014 - 03:59 PM.

[Tritarian]

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.2.1
2 40 ms 25 ms 38 ms 71.57.96.1
3 10 ms 9 ms 9 ms te-0-0-0-4-sur01.speedway.in.indiana.comcast.net[68.87.209.177]
4 * 10 ms 11 ms te-0-5-0-2-ar01.indianapolis.in.indiana.comcast.net [68.87.231.25]
5 25 ms * 23 ms he-1-15-0-0-ar01.area4.il.chicago.comcast.net [68.87.230.9]
6 22 ms * * be-33491-cr01.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 22 ms 28 ms 20 ms 68.86.85.230
8 * * * Request timed out.
9 * * * Request timed out.
10 * 38 ms 50 ms bhs-g1-6k.qc.ca [198.27.73.5]
11 40 ms * 49 ms 198.27.73.231
12 39 ms 38 ms 38 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\>tracert 192.99.40.130

Tracing route to splunk10.500px.net [192.99.40.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 11 ms 21 ms 21 ms 71.57.96.1
3 9 ms * 11 ms te-0-0-0-4-sur01.speedway.in.indiana.comcast.net[68.87.209.177]
4 13 ms 14 ms 23 ms te-0-12-0-3-ar01.indianapolis.in.indiana.comcast.net [69.139.185.65]
5 * 23 ms 23 ms he-1-14-0-0-ar01.area4.il.chicago.comcast.net [68.87.231.17]
6 22 ms 23 ms 23 ms be-33491-cr01.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 20 ms 21 ms 21 ms pos-1-6-0-0-pe01.350ecermak.il.ibone.comcast.net[68.86.87.130]
8 * * 21 ms 198.27.73.65
9 37 ms * 37 ms 198.27.73.179
10 41 ms 38 ms 40 ms bhs-g1-6k.qc.ca [198.27.73.5]
11 * 39 ms * bhs-s3-6k.qc.ca [198.27.73.140]
12 57 ms * 41 ms splunk10.500px.net [192.99.40.130]

Trace complete.

C:\>tracert 209.15.227.106

Tracing route to 209.15.227.106 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1
2 22 ms 25 ms 29 ms 71.57.96.1
3 11 ms 11 ms 11 ms te-0-0-0-4-sur01.speedway.in.indiana.comcast.net[68.87.209.177]
4 13 ms 15 ms 16 ms te-0-5-0-2-ar01.kokomo.in.indiana.comcast.net [68.87.231.61]
5 23 ms 23 ms 24 ms he-1-14-0-0-ar01.elmhurst.il.chicago.comcast.net[68.87.230.241]
6 28 ms 27 ms 28 ms he-1-6-0-0-11-cr01.seattle.wa.ibone.comcast.net[68.86.92.33]
7 24 ms 27 ms 24 ms be-10406-cr01.350ecermak.il.ibone.comcast.net [68.86.84.210]
8 24 ms 23 ms 23 ms he-0-3-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.88.142]
9 23 ms 23 ms 24 ms as13768-1-c.350ecermak.il.ibone.comcast.net [173.167.58.10]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 35 ms 42 ms 33 ms 209.15.227.106

Trace complete.

Mostly I seem to have the issue with rubberbanding, hit detection seems to be ok as long as I am not rubberbanding.
To me it seems like it mostly happens when I "should" get the "incomming missle" warning. The rubberbanding seems to happen just before I get hit with missiles and continues until all the missile attacks are finished. Basically my client gets paused while I get pelted with missiles, and releases me after I have felt their wrath.
(included the other two address given eariler in thread for completness.

Comcast ISP in central Indiana U.S.A.

[SoggyGorilla]

So....i have already posted about this issue. YES the problem is NEWARK! No they can't fix it. Your going to have to wait till they bring more fiber connections online to the data-center in Montreal. Here is the open ticket @ OVH.


http://status.ovh.co...details&id=8038

[Budor]

Came back after a week long break, unfortunately nothing changed here. Tracerts look fine, ping in game fluctuates between 115-200 constantly.

C:\Windows\System32>tracert 192.99.109.192

Routenverfolgung zu mwomercs.com [192.99.109.192]
über maximal 30 Hops:

1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 17 ms 18 ms 18 ms 217.0.119.68
3 21 ms 19 ms 20 ms 217.0.77.62
4 27 ms 29 ms 26 ms 217.239.52.70
5 * 63 ms * fra-1-6k.de.eu [94.23.122.153]
6 28 ms 28 ms 28 ms sbg-g2-a9.fr.eu [91.121.128.125]
7 28 ms 29 ms 30 ms 37.187.36.155
8 * * * Zeitüberschreitung der Anforderung.
9 118 ms 117 ms 117 ms mwomercs.com [192.99.109.192]

Ablaufverfolgung beendet.


C:\Windows\System32>tracert 192.99.40.130

Routenverfolgung zu splunk10.500px.net [192.99.40.130]
über maximal 30 Hops:

1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 19 ms 18 ms 18 ms 217.0.119.68
3 21 ms 19 ms 19 ms 217.0.77.58
4 24 ms 24 ms 24 ms 217.239.39.30
5 * * * Zeitüberschreitung der Anforderung.
6 34 ms 33 ms 33 ms rbx-g2-a9.fr.eu [91.121.131.130]
7 * * * Zeitüberschreitung der Anforderung.
8 * * * Zeitüberschreitung der Anforderung.
9 114 ms 114 ms 117 ms bhs-g2-6k.qc.ca [198.27.73.207]
10 112 ms 112 ms 112 ms bhs-s4-6k.qc.ca [198.27.73.146]
11 117 ms 113 ms 135 ms splunk10.500px.net [192.99.40.130]

Ablaufverfolgung beendet.

C:\Windows\System32>tracert 209.15.227.106

Routenverfolgung zu 209.15.227.106 über maximal 30 Hops

1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 19 ms 18 ms 17 ms 217.0.119.68
3 19 ms 19 ms 19 ms 217.0.77.58
4 18 ms 19 ms 19 ms 62.157.251.238
5 119 ms 119 ms 119 ms ae-2-23.edge1.Toronto2.Level3.net [4.69.200.238]

6 129 ms 126 ms 127 ms PEER-1-NETW.edge1.Toronto2.Level3.net [4.59.183.
162]
7 * * * Zeitüberschreitung der Anforderung.
8 131 ms 131 ms 130 ms 209.15.227.106

Ablaufverfolgung beendet.

[Pixelpilot]

This is what i got and i am lagging and rubberbandibg a lot.

Edited by Pixelpilot, 29 November 2014 - 06:06 AM.