180 replies to this topic

[KharnZor]

Verapamil, on 04 December 2014 - 08:08 PM, said:

I always have an ordinary connection, the lag spiking is annoying but the lack of hit registration for me since the server move is abysmal. Only front loaded damage weapons are useful at all, and even then they are a bit dodgy. Point blank shots with PPC or SRM never register

I have no idea what this tracert means.....

Optus customer?

[Elkarlo]

Lot of Rubberbanding
After 22GMT.

Ping is steady with 110-130ms.

Lot of Ping differences seems to trigger Rubberbanding and wrong Ghostsightings..

Edited by Elkarlo, 06 December 2014 - 12:37 PM.

[FatYak]

KharnZor, on 06 December 2014 - 08:11 AM, said:

Optus customer?

Yeah i am. Have always had a finicky connection, got worse after the server move

[Violent Nick]

Come on guys, the game is unplayable for people in Europe & UK tonight... this has to stop. Please...


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

C:\Users\*****>tracert 192.99.109.192

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

1 619 ms 7 ms 8 ms 10.10.144.1
2 7 ms 7 ms 7 ms brig-core-2b-xe-021-0.network.virginmedia.net [8
0.3.65.165]
3 17 ms 14 ms 11 ms popl-bb-1b-ae14-0.network.virginmedia.net [213.1
05.159.157]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 17 ms 17 ms 35 ms tcl5-ic-2-ae0-0.network.virginmedia.net [212.250
.15.210]
9 * * * Request timed out.
10 33 ms 26 ms 27 ms rbx-g2-a9.fr.eu [91.121.131.181]
11 24 ms 24 ms 24 ms 37.187.36.133
12 * * * Request timed out.
13 108 ms 108 ms 111 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\*****>

Edited by Nick86, 08 December 2014 - 10:33 AM.

[Superslicks]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\joshua>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 BTHOMEHUB [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 9 ms 10 ms 31.55.187.212
5 16 ms 15 ms 15 ms 195.99.127.62
6 11 ms 10 ms 11 ms peer2-xe9-0-0.telehouse.ukcore.bt.net [109.159.2
54.126]
7 * * * Request timed out.
8 81 ms 48 ms 146 ms rbx-g1-a9.fr.eu [91.121.131.191]
9 15 ms 15 ms 14 ms 37.187.36.131
10 * * * Request timed out.
11 95 ms 95 ms 95 ms mwomercs.com [192.99.109.192]
Trace complete.
C:\Users\joshua>

[D0hle]

Horrendous lag today. Normal ping around 160, now jumping between 200 and 270. Needless to say experiencing all kinds of lovely hit detection problems.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 5 ms 7 ms 5 ms 1252026 [0.0.0.0]
3 11 ms 6 ms 6 ms hel5-sr3.dnaip.fi [62.78.106.166]
4 8 ms 6 ms 6 ms hel5-tr3.dnaip.fi [62.78.107.116]
5 7 ms 9 ms 7 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 16 ms rai1-tr1.dnaip.fi [62.78.107.13]
8 15 ms 15 ms 14 ms tuk2-sr1.dnaip.fi [62.78.107.174]
9 17 ms 15 ms 23 ms te0-7-0-2.ccr21.sto01.atlas.cogentco.com [149.6.168.129]
10 14 ms 15 ms 15 ms level3.sto01.atlas.cogentco.com [130.117.14.6]
11 * * * Request timed out.
12 * * * Request timed out.
13 54 ms 54 ms * fra-5-6k.fr.eu [91.121.131.5]
14 57 ms 59 ms 55 ms sbg-g2-a9.fr.eu [91.121.128.82]
15 51 ms 51 ms 53 ms 37.187.36.155
16 * * * Request timed out.
17 224 ms 221 ms 223 ms mwomercs.com [192.99.109.192]

Presumably this is still due to the issue with the Finnish ISP 'DNA'. The lag is getting quite ridiculous I have to say...

[Ace Savant]

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

1 <1 ms <1 ms <1 ms 192.168.10.1
2 1 ms 6 ms 6 ms 10.50.8.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
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 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 115 ms 116 ms 117 ms mwomercs.com [192.99.109.192]

Trace complete.



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

1 <1 ms <1 ms <1 ms 192.168.10.1
2 3 ms 2 ms 3 ms 10.50.8.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
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 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 114 ms 114 ms 114 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\Ace>pathping 192.99.109.192

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
0 Ace-Zool.sanctionswithin.com [192.168.10.104]
1 192.168.10.1
2 10.50.8.1
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Ace-Zool.sanctionswithin.com [192.
168.10.104]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.10.1
0/ 100 = 0% |
2 3ms 0/ 100 = 0% 0/ 100 = 0% 10.50.8.1


Tried it twice to be sure, and even tried a pathping. I'm sure this tells you a whole lot of nothing, seeing as no part of the path is reachable other than the first and last hops.


I'm having a very strange issue where the game will intermittently put me on servers with between 400ms-900ms. This leads to the game being nearly unplayable, and I'm sure is none too happy for those shooting at me. Then I will try again and get a regular ping (around 120ms). Let me know if I can provide any more information. Sorry I don't have more.

[Dauntless Blint]

How to improve packet loss?

Also since the "To the Victors" challenge weekend and the one before it my ping has gone up from 235-255ish.
I don't know how to muck around with script or files so can you optimise heat vision please,My frames start at 100fps then drop to 60 pugging and in group drops it goes down to like 40 and with heat vision it goes down to about 25 and it becomes unplayable.

[Violent Nick]

So, is there any info on why this is happening or and ideas on how this may even begin to be fixed?? EU server? Anything?

It seems like a lot of people are having issues. Mine has been since the server was moved months ago now.
I love MWO, but I really cannot justify spending money on a game I can hardly play properly. I'm already gonna be useless to my Unit in CW because of this. I don't mean to whine and I don't expect a magic wand but.... any info???

[Mellowseven]

Quote

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

C:\Users\Eric>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 dsldevice.attlocal.net [192.168.1.254]
2 26 ms 21 ms 23 ms 162-198-20-3.lightspeed.mtryca.sbcglobal.net [16
2.198.20.3]
3 * * * Request timed out.
4 20 ms 24 ms 23 ms 99.134.39.27
5 24 ms 29 ms 25 ms 12.83.47.133
6 32 ms 36 ms 34 ms ggr2.la2ca.ip.att.net [12.122.128.97]
7 37 ms 29 ms 33 ms ix-15-0.tcore1.LVW-Los-Angeles.as6453.net [66.11
0.59.41]
8 * * * Request timed out.
9 * * 119 ms if-1-2.tcore1.NYY-New-York.as6453.net [66.198.12
7.6]
10 126 ms 120 ms 122 ms if-3-2.thar1.NJY-Newark.as6453.net [66.198.70.21
]
11 * * * Request timed out.
12 133 ms 133 ms 137 ms bhs-g2-6k.qc.ca [198.27.73.207]
13 134 ms 131 ms 129 ms 198.27.73.233
14 135 ms 134 ms 132 ms mwomercs.com [192.99.109.192]

Trace complete.

[Bhael Fire]

Ever since the new map went in I've been getting high pings intermittently every other match or so. Usually shutting down the mech, disconnecting from the match and reconnecting immediately fixes the problem.

I will post a tracert tonight when it happens next.

[D0hle]

And it's happening again, ping is up to 250 when my normal is 160. Getting really tired of this.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 5 ms 7 ms 1252026 [0.0.0.0]
3 7 ms 7 ms 5 ms hel5-sr3.dnaip.fi [62.78.106.166]
4 8 ms 6 ms 6 ms hel5-tr3.dnaip.fi [62.78.107.116]
5 6 ms 7 ms 8 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 16 ms 15 ms 17 ms rai1-tr1.dnaip.fi [62.78.107.13]
8 16 ms 16 ms 14 ms tuk2-sr1.dnaip.fi [62.78.107.174]
9 16 ms 15 ms 14 ms te0-7-0-2.ccr21.sto01.atlas.cogentco.com [149.6.168.129]
10 15 ms 15 ms 14 ms level3.sto01.atlas.cogentco.com [130.117.14.6]
11 * * 93 ms ae-2-70.edge5.Frankfurt1.Level3.net [4.69.154.73]
12 91 ms * 96 ms ae-2-70.edge5.Frankfurt1.Level3.net [4.69.154.73]
13 51 ms * 53 ms fra-5-6k.fr.eu [91.121.131.5]
14 54 ms 55 ms 55 ms sbg-g2-a9.fr.eu [91.121.128.82]
15 52 ms 51 ms 51 ms 37.187.36.155
16 * * * Request timed out.
17 240 ms 242 ms 242 ms mwomercs.com [192.99.109.192]

[Lyrik]

My Ping for tonight. 109 is pretty standart for me. Could be better ;-)

Microsoft Windows [Version 6.3.9600]
(c) 2013 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 3 ms fritz.box [192.168.178.1]
2 20 ms 18 ms 18 ms 10.222.0.1
3 22 ms 20 ms 23 ms 10.220.2.13
4 20 ms 21 ms 18 ms 78.141.179.81
5 * 23 ms 24 ms PTLUX-Teralink-Brussels.pt.lu [213.166.61.193]
6 * * * Request timed out.
7 30 ms 33 ms 30 ms rbx-g2-a9.fr.eu [94.23.122.137]
8 29 ms 30 ms 28 ms 37.187.36.133
9 * * * Request timed out.
10 112 ms 109 ms 109 ms mwomercs.com [192.99.109.192]

Trace complete.

[MayoRe]

I'm getting some bad latency lately. My usual 240ms-ish is good enough but it spikes up to 1.3kish..


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 4 ms 3 ms 3 ms cgw-211-24-64-1.bbrtl.time.net.my [211.24.64.1]
3 3 ms 3 ms 3 ms xe-5-3-0-0.er-01-majjw.ni.time.net.my [223.28.2.41]
4 14 ms 14 ms 14 ms xe-5-3-0-0.er-01-glsfb.ni.time.net.my [223.28.2.37]
5 13 ms 15 ms 15 ms xe-0-1-0-1.cr-02-glsfb.ni.time.net.my [223.28.2.9]
6 10 ms 10 ms 10 ms ae-0-0.br-01-mciwg.ni.time.net.my [223.28.2.122]
7 10 ms 9 ms 9 ms 124.158.226.149
8 170 ms 170 ms 170 ms xe-0-1-0-0.cr-gw-2-sin-pip.sg.globaltransit.net[124.158.224.229]
9 170 ms 170 ms 170 ms ae-2.br-gw-1-lax-pip.us.globaltransit.net [124.158.224.18]
10 170 ms 177 ms 170 ms ge-0-1-0-0.pp-gw-1-lax-pip.us.globaltransit.net[124.158.250.9]
11 * * 170 ms any2ix.coresite.com [206.72.210.214]
12 * * * Request timed out.
13 240 ms 241 ms 241 ms bhs-g2-6k.qc.ca [198.27.73.207]
14 952 ms 1082 ms 1190 ms 198.27.73.233
15 241 ms 243 ms 242 ms mwomercs.com [192.99.109.192]

Trace complete.

[Ataboy]

Jon, can we get an update on steps if any PGI are taking with OVH on this. The problem for me is during peak times (8-11pm ET). I have worked with my ISP as far as I can go with them.

Looks like there are 3 devices we need to get responses from once we get to beauharnois. 198.27.73.231 is the problem for the tests below, but all 3 during peak time are simply not handling the load.



tracert mwomercs.com
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.2.1]
2 14 ms 15 ms 13 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 20 ms 21 ms 20 ms 216.254.131.129
4 18 ms * 16 ms gw-ovh.torontointernetxchange.net [206.108.34.189]
5 21 ms * 21 ms mtl-2-6k.qc.ca [178.32.135.71]
6 28 ms 23 ms 25 ms bhs-g1-6k.qc.ca [198.27.73.5]
7 1184 ms 567 ms 2851 ms 198.27.73.231
8 22 ms 23 ms 35 ms mwomercs.com [192.99.109.192]
Trace complete.

tracert mwomercs.com
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.2.1]
2 14 ms 14 ms 15 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 34 ms 35 ms 35 ms 216.254.131.129
4 14 ms * 16 ms gw-ovh.torontointernetxchange.net [206.108.34.189]
5 21 ms * 20 ms mtl-2-6k.qc.ca [178.32.135.71]
6 24 ms 29 ms 27 ms bhs-g1-6k.qc.ca [198.27.73.5]
7 * * 1492 ms 198.27.73.231
8 37 ms 58 ms 27 ms mwomercs.com [192.99.109.192]
Trace complete.



tracert mwomercs.com
Tracing route to mwomercs.com [192.99.109.192]over a maximum of 30 hops:
1 2 ms 1 ms 1 ms homeportal [192.168.2.1]
2 14 ms 15 ms 13 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 29 ms 27 ms 29 ms 216.254.131.129
4 14 ms * 19 ms gw-ovh.torontointernetxchange.net [206.108.34.189]
5 32 ms * * mtl-2-6k.qc.ca [178.32.135.71]
6 23 ms 23 ms 23 ms bhs-g1-6k.qc.ca [198.27.73.5]
7 * * * Request timed out.
8 23 ms 23 ms 23 ms mwomercs.com [192.99.109.192]
Trace complete.

tracert mwomercs.com
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.2.1]
2 15 ms 13 ms 13 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 30 ms 33 ms 33 ms 216.254.131.129
4 19 ms * 15 ms gw-ovh.torontointernetxchange.net [206.108.34.189]
5 26 ms * 23 ms mtl-2-6k.qc.ca [178.32.135.71]
6 33 ms 37 ms 23 ms bhs-g1-6k.qc.ca [198.27.73.5]
7 1517 ms 1395 ms 1373 ms 198.27.73.231
8 23 ms 27 ms 51 ms mwomercs.com [192.99.109.192]
Trace complete.

Thanks

[Jon Cunningham]

Hey folks, we're back in the office again. Give me a bit to get caught up on your postings.

We have been working behind the scenes over the holidays with some of our providers. Hopefully we will have some new news for folks with lag problems that we can resolve by optimizing the pathing soon.

[mogs01gt]

Jon Cunningham, on 05 January 2015 - 08:20 AM, said:

Hey folks, we're back in the office again. Give me a bit to get caught up on your postings.

We have been working behind the scenes over the holidays with some of our providers. Hopefully we will have some new news for folks with lag problems that we can resolve by optimizing the pathing soon.

My money is on the whole issue with the United States ****** internet speeds.

[Bracchus]

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

1 1 ms 9 ms 1 ms 192.168.1.1
2 23 ms 22 ms 24 ms gw3-no27.tbcn.telia.com [81.232.154.1]
3 36 ms 38 ms 38 ms s-b6-link.telia.net [80.91.250.43]
4 36 ms 37 ms 36 ms s-bb4-link.telia.net [62.115.141.204]
5 112 ms 59 ms 57 ms ffm-bb2-link.telia.net [62.115.143.105]
6 59 ms 62 ms 57 ms ffm-b11-link.telia.net [62.115.138.13]
7 * * * Request timed out.
8 72 ms 67 ms 69 ms sbg-g1-a9.fr.eu [91.121.128.127]
9 75 ms 66 ms 66 ms 37.187.36.153
10 * * * Request timed out.
11 146 ms 143 ms 143 ms mwomercs.com [192.99.109.192]

Trace complete.

Been having some really bad spikes with my ping lately, its jumping from 150ish up to 600-800ish, unplayable

[nehebkau]

Been getting very bad performance the past 3 days... usually around 60 ms in-game ping but now ~250 with rubber banding and DCs

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 * * * Request timed out.
3 9 ms 11 ms 8 ms rc2so-tge0-13-0-2-1.cg.shawcable.net [64.59.132.161]
4 34 ms 32 ms 34 ms rc5wt-tge0-11-0-11.wa.shawcable.net [66.163.70.254]
5 * * * Request timed out.
6 * * 206 ms snj-2-6k.ca.us [178.32.135.162]
7 203 ms 201 ms 284 ms pal-1-6k.ca.us [178.32.135.169]
8 * * 108 ms chi-2-6k.il.us [198.27.73.184]
9 * * * Request timed out.
10 * 577 ms * bhs-g2-6k.qc.ca [198.27.73.7]
11 229 ms * 227 ms 198.27.73.233
12 87 ms 89 ms 85 ms mwomercs.com [192.99.109.192]

Trace complete.

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 * * * Request timed out.
3 10 ms 10 ms 20 ms rc2so-tge0-13-0-2-1.cg.shawcable.net [64.59.132.161]
4 34 ms 32 ms 31 ms rc5wt-tge0-11-0-4.wa.shawcable.net [66.163.70.238]
5 * * * Request timed out.
6 * 70 ms * snj-2-6k.ca.us [178.32.135.162]
7 * 343 ms 223 ms pal-1-6k.ca.us [178.32.135.169]
8 * * * Request timed out.
9 234 ms * 229 ms mtl-2-6k.qc.ca [198.27.73.173]
10 583 ms * 449 ms bhs-g2-6k.qc.ca [198.27.73.7]
11 88 ms 89 ms 87 ms 198.27.73.233
12 101 ms 104 ms 109 ms mwomercs.com [192.99.109.192]

Trace complete.
Pinging 192.99.109.192 with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=214ms TTL=55
Reply from 192.99.109.192: bytes=32 time=211ms TTL=55
Reply from 192.99.109.192: bytes=32 time=215ms TTL=55
Reply from 192.99.109.192: bytes=32 time=216ms TTL=55
Request timed out.
Reply from 192.99.109.192: bytes=32 time=215ms TTL=55
Request timed out.
Reply from 192.99.109.192: bytes=32 time=213ms TTL=55
Reply from 192.99.109.192: bytes=32 time=213ms TTL=55
Reply from 192.99.109.192: bytes=32 time=209ms TTL=55
Reply from 192.99.109.192: bytes=32 time=208ms TTL=55
Reply from 192.99.109.192: bytes=32 time=202ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=95ms TTL=55
Reply from 192.99.109.192: bytes=32 time=186ms TTL=55
Reply from 192.99.109.192: bytes=32 time=214ms TTL=55
Reply from 192.99.109.192: bytes=32 time=196ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=85ms TTL=55
Reply from 192.99.109.192: bytes=32 time=133ms TTL=55
Reply from 192.99.109.192: bytes=32 time=174ms TTL=55
Reply from 192.99.109.192: bytes=32 time=201ms TTL=55
Reply from 192.99.109.192: bytes=32 time=164ms TTL=55
Reply from 192.99.109.192: bytes=32 time=185ms TTL=55
Reply from 192.99.109.192: bytes=32 time=205ms TTL=55
Reply from 192.99.109.192: bytes=32 time=218ms TTL=55
Reply from 192.99.109.192: bytes=32 time=215ms TTL=55
Reply from 192.99.109.192: bytes=32 time=220ms TTL=55
Reply from 192.99.109.192: bytes=32 time=216ms TTL=55
Reply from 192.99.109.192: bytes=32 time=215ms TTL=55
Reply from 192.99.109.192: bytes=32 time=218ms TTL=55
Request timed out.
Reply from 192.99.109.192: bytes=32 time=214ms TTL=55
Request timed out.
Reply from 192.99.109.192: bytes=32 time=213ms TTL=55
Request timed out.
Reply from 192.99.109.192: bytes=32 time=213ms TTL=55
Reply from 192.99.109.192: bytes=32 time=175ms TTL=55
Reply from 192.99.109.192: bytes=32 time=152ms TTL=55
Reply from 192.99.109.192: bytes=32 time=120ms TTL=55
Reply from 192.99.109.192: bytes=32 time=101ms TTL=55
Reply from 192.99.109.192: bytes=32 time=123ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=137ms TTL=55
Reply from 192.99.109.192: bytes=32 time=186ms TTL=55
Reply from 192.99.109.192: bytes=32 time=206ms TTL=55
Reply from 192.99.109.192: bytes=32 time=192ms TTL=55
Reply from 192.99.109.192: bytes=32 time=212ms TTL=55
Request timed out.
Reply from 192.99.109.192: bytes=32 time=212ms TTL=55
Reply from 192.99.109.192: bytes=32 time=213ms TTL=55
Reply from 192.99.109.192: bytes=32 time=218ms TTL=55
Reply from 192.99.109.192: bytes=32 time=219ms TTL=55
Reply from 192.99.109.192: bytes=32 time=213ms TTL=55
Reply from 192.99.109.192: bytes=32 time=212ms TTL=55
Reply from 192.99.109.192: bytes=32 time=215ms TTL=55
Reply from 192.99.109.192: bytes=32 time=215ms TTL=55
Reply from 192.99.109.192: bytes=32 time=219ms TTL=55
Reply from 192.99.109.192: bytes=32 time=191ms TTL=55
Reply from 192.99.109.192: bytes=32 time=139ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=87ms TTL=55
Reply from 192.99.109.192: bytes=32 time=168ms TTL=55
Reply from 192.99.109.192: bytes=32 time=216ms TTL=55
Reply from 192.99.109.192: bytes=32 time=215ms TTL=55
Request timed out.
Reply from 192.99.109.192: bytes=32 time=213ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=93ms TTL=55
Reply from 192.99.109.192: bytes=32 time=86ms TTL=55
Reply from 192.99.109.192: bytes=32 time=88ms TTL=55
Reply from 192.99.109.192: bytes=32 time=89ms TTL=55
Reply from 192.99.109.192: bytes=32 time=125ms TTL=55
Reply from 192.99.109.192: bytes=32 time=105ms TTL=55
Reply from 192.99.109.192: bytes=32 time=173ms TTL=55
Reply from 192.99.109.192: bytes=32 time=205ms TTL=55
Request timed out.

Ping statistics for 192.99.109.192:
Packets: Sent = 100, Received = 92, Lost = 8 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 220ms, Average = 152ms

C:\>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 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 9 ms 17 ms rc3no-tge0-0-0-17-1.cg.shawcable.net [64.59.132.165]
4 10 ms 10 ms 9 ms rd1so-ge1-0-0.cg.shawcable.net [66.163.71.118]
5 33 ms 31 ms 31 ms rc5wt-tge0-4-0-6.wa.shawcable.net [66.163.70.210]
6 * * * Request timed out.
7 207 ms 197 ms * snj-2-6k.ca.us [178.32.135.162]
8 198 ms 195 ms 196 ms 198.27.73.249
9 * * * Request timed out.
10 * 210 ms 215 ms mtl-2-6k.qc.ca [198.27.73.179]
11 557 ms * 436 ms bhs-g2-6k.qc.ca [198.27.73.7]
12 88 ms 88 ms 89 ms bhs-s3-6k.qc.ca [198.27.73.142]
13 88 ms 86 ms 96 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.

Ping statistics for 192.99.109.192:
Packets: Sent = 10000, Received = 9034, Lost = 966 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 1273ms, Average = 169ms

Edited by nehebkau, 21 February 2015 - 04:52 PM.

[R4wdigga]

Horrible lags and rubbing here in germany, yesterday evening / night @ around 10 pm local time to 1 am, and this morning @ around 9 am.





"Zeitüberschreitung der Anforderung" means - Timeout.

I'm seing this alot lately, and the game is unplayable during this times.
Laggy mech movement, laggy hitreg, even delayed droptime and loadscreen.

Is there any solution / workaround yet?

Edited by R4wdigga, 25 April 2015 - 10:49 PM.