180 replies to this topic

[SoggyGorilla]

Well i find this extremely aggravating.



notice the above graphic. The ip is hosted with peer 1. this ip is located in Toronto, and until im corrected i believe this to be the old data center for the previous mechwarrior server host. That being said, i get a great ping to it. and not only that, MY TRAFFIC GOES THROUGH MONTREAL! so really you can see the problem here.




Oh i see so 1 less hop because i need to go to Montreal, but wait 5x the latency? the problem is the hosting providers reception from the national providers. Yes i understand that the routers delay pings when they are overloaded, but that is the same ping i get in game, over 300.

[affman67]

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.

[Texugo87]

Usually my ping is quite good, but lately I've been experiencing periodic rubber-banding, at a time I experienced some rubber banding I got the following tracert

1 2ms <1ms <1ms 192.168.11.1
2 1ms <1ms <1ms 192.168.0.1
3 8ms 9ms 9ms blk-11-16-1.eastlink.ca [76.11.16.1]
4 8ms 9 ms 14ms blk-212-126-149.easlinc.ca [173.212.126.149]
5 10ms 9ms 10ms 24.215.101.101
6 14ms 9ms 9ms ns-hlfx-br001.ns.easlink.ca [24.215.101.221]
7 43ms * 132ms gw.ovh.torontointernetxchange.net [206.108.34.189]
8 43ms 43ms * mtl-2-6k.qc.ca [178.32.135.71]
9 366ms 363ms 340ms bhs-g2-6k.qc.ca [198.27.73.7]
10 53ms 52ms 51ms 198.27.73.233
11 43ms 48ms 44ms mwomercs.com [192.99.109.192]

I just re-ran the tracert and for hop 9 got:
9 63ms 71ms 78ms bhs-g2-6k.qc.ca
all other results were more or less the same.

It also seems a little strange that I would go from Halifax to Toronto then back to Montreal.

[Creovex]

Reserving spot for my posts... Been seeing a TON of lag spiking for the past week+ that never used to happen... Costs me a ton of airstrikes.... Of to post when I get out of work.

ie. ping = 48 then ping = 836 (tons of this lately)

Edited by Creovex, 21 November 2014 - 10:04 AM.

[Thunder Lips Express]

is lag the same as bad fps? my ping never goes above 50 but my fps changes from being able to run 40+ fps on high settings for days on end to dropping below 10 fps on medium settings

[Texugo87]

Ecliptor, on 21 November 2014 - 08:58 AM, said:

is lag the same as bad fps? my ping never goes above 50 but my fps changes from being able to run 40+ fps on high settings for days on end to dropping below 10 fps on medium settings

No, FPS is going to be completely local to your computer. Look for another program running in the background (via task manager) when you experience a dip in FPS like that, and download a hardware monitoring program to watch for a cooling problem (HWmonitor is easy to use).

Lag refers to internet connection problems, and will manifest as rubberbanding, teleporting, and ping spikes in game, not a change in FPS.

[Thunder Lips Express]

cjmurphy87, on 21 November 2014 - 09:02 AM, said:

No, FPS is going to be completely local to your computer. Look for another program running in the background (via task manager) when you experience a dip in FPS like that, and download a hardware monitoring program to watch for a cooling problem (HWmonitor is easy to use).

Lag refers to internet connection problems, and will manifest as rubberbanding, teleporting, and ping spikes in game, not a change in FPS.

ok, thank you

[Chimperator]

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

1 <1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 12 ms 14 ms 19 ms 83-169-183-72-isp.superkabel.de [83.169.183.72

3 18 ms 19 ms 13 ms ip5886c9a9.dynamic.kabel-deutschland.de [88.13
201.169]
4 26 ms 23 ms 31 ms ip5886ca3a.dynamic.kabel-deutschland.de [88.13
202.58]
5 25 ms 27 ms 29 ms ip5886ca29.dynamic.kabel-deutschland.de [88.13
202.41]
6 22 ms 20 ms * decix.routers.ovh.net [80.81.192.209]
7 28 ms 29 ms 24 ms sbg-g2-a9.fr.eu [91.121.128.82]
8 27 ms 23 ms 24 ms 37.187.36.155
9 * * * Request timed out.
10 113 ms 113 ms 116 ms mwomercs.com [192.99.109.192]

Trace complete.


Specialy on weekends i have nearly no hitreg, and sometimes my mech turns instant a few deegrees back against the direction where I twisted to.

And sometimes a few desynchs.

Under the week its all fine, absolut no problems.

I'm sure there is an issue on the mwo servers or smth like.
Many people of my unit got same problems on weekends and we all from Germany with modern stable internet performance!

Edited by Chimperator, 21 November 2014 - 04:28 PM.

[Budor]

My tracerts look fine again, ingame ping still fluctuates inbetween 117-300ms.


C:\Windows\System32>tracert 192.99.40.103

Routenverfolgung zu ns7000224.ip-192-99-40.net [192.99.40.103]
über maximal 30 Hops:

1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 18 ms 17 ms 17 ms 217.0.119.68
3 21 ms 18 ms 19 ms 217.0.77.62
4 25 ms 60 ms 25 ms 217.239.39.26
5 25 ms * 45 ms fra-1-6k.de.eu [94.23.122.153]
6 34 ms 34 ms 34 ms rbx-g2-a9.fr.eu [91.121.131.130]
7 110 ms * * ldn-5-6k.uk.eu [91.121.131.242]
8 * * * Zeitüberschreitung der Anforderung.
9 115 ms 114 ms 115 ms bhs-g2-6k.qc.ca [198.27.73.207]
10 115 ms 115 ms 115 ms bhs-s3-6k.qc.ca [198.27.73.142]
11 118 ms 120 ms 118 ms ns7000224.ip-192-99-40.net [192.99.40.103]

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 17 ms 18 ms 17 ms 217.0.119.68
3 27 ms 19 ms 19 ms 217.0.77.58
4 44 ms 19 ms 30 ms 80.156.161.122
5 118 ms 118 ms 119 ms ae-2-23.edge1.Toronto2.Level3.net [4.69.200.238]

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

Ablaufverfolgung beendet.

Edited by Budor, 21 November 2014 - 11:49 PM.

[Ataboy]

Lag and spikes most of the time, but 9pm-11pm eastern it is unplayable. Had to miss comp play because of it.

Thanks for taking a look at these.

C:\Users\Office3_User>tracert 192.99.109.129
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 6 ms 6 ms 6 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 7 ms 6 ms 6 ms 216.254.131.133
4 7 ms 400 ms 47 ms gw-nyiix.bb1.eastyork.primus.ca [198.32.160.89]
5 27 ms * 27 ms nyiix.nyc.ny.us [198.32.160.77]
6 649 ms * * nwk-2-6k.nj.us [178.32.135.59]
7 36 ms 35 ms 36 ms bhs-g2-6k.qc.ca [198.27.73.207]
8 36 ms 36 ms 35 ms 198.27.73.233
9 36 ms 35 ms 35 ms 192.99.109.129
Trace complete.

[ice trey]

I've already started a support e-mail about this months ago. I already contacted both my ISP (NTT East, Japan), as well as PGI. Staff are supposedly "Looking at it".

But recently, my ping has taken an even BIGGER dip this past weekend, as ridiculous BS is happening with my connection.

When I first got to Japan, the connection was working properly, going through the Pacific. This gave me a ping of below 200. Usually 170-180.

After the server move, my ping jumped by 100 points, as the connection started going the wrong way around the world. Now I was sitting at 270-320 ping.



This past weekend, Not only is my connection going the wrong way, but it's now going through undersea cables, junctioning from Singapore, ALL THE WAY to Florida. My ping has jumped by another 100 points.



I don't know just what in the hell is going on.

[Lynx7725]

ice trey, on 22 November 2014 - 08:18 AM, said:

When I first got to Japan, the connection was working properly, going through the Pacific. This gave me a ping of below 200. Usually 170-180.

After the server move, my ping jumped by 100 points, as the connection started going the wrong way around the world. Now I was sitting at 270-320 ping.

This past weekend, Not only is my connection going the wrong way, but it's now going through undersea cables, junctioning from Singapore, ALL THE WAY to Florida. My ping has jumped by another 100 points.

I don't know just what in the hell is going on.

It looks like your connection is routing through Europe, which by extension is logical for it to cross the Atlantic to the Eastern US seaboard (to Florida, it seems).

I'm in SG myself and suffering from a similar issue it seems. It might actually be faster to go through Europe if there are some issues with the submarine cables in the Pacific.

[Uthael]

The following is after I lagged out of a game. When I reconnected, I was dead with good ping:
Tracing route to mwomercs.com [192.99.109.192] over a maximum of 30 hops:
1 1 ms 1 ms 2 ms ~censored~
2 * * * Request timed out.
3 10 ms 10 ms 10 ms 172.29.49.73
4 8 ms 8 ms 8 ms gdr09-hdr01.ip.t-com.hr [195.29.3.210]
5 * * * Request timed out.
6 30 ms 33 ms 27 ms sbg-g1-a9.fr.eu [91.121.128.127]
7 40 ms 28 ms 27 ms 37.187.36.153
8 * * * Request timed out.
9 116 ms 117 ms 118 ms mwomercs.com [192.99.109.192]
Trace complete.

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 ~censored~
2 * * * Request timed out.
3 10 ms 6 ms 7 ms 172.29.49.65
4 8 ms 9 ms 8 ms gdr09-hdr01.ip.t-com.hr [195.29.3.210]
5 55 ms * * decix2.routers.ovh.net [80.81.193.209]
6 36 ms 34 ms 35 ms rbx-g1-a9.fr.eu [91.121.131.205]
7 * * * Request timed out.
8 * * * Request timed out.
9 114 ms 112 ms 113 ms bhs-g1-6k.qc.ca [198.27.73.205]
10 114 ms 113 ms 113 ms bhs-s3-6k.qc.ca [198.27.73.140]
11 123 ms 116 ms 116 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 ~censored~
2 * * * Request timed out.
3 9 ms 10 ms 6 ms 172.29.49.73
4 8 ms 8 ms 14 ms gdr09-hdr01.ip.t-com.hr [195.29.3.210]
5 32 ms 31 ms 36 ms frk-eqx-cor-1.peer1.net [80.81.193.151]
6 32 ms 33 ms 43 ms 10ge.xe-3-0-0.ams-sara-cor-1.peer1.net [216.187.88.199]
7 122 ms 122 ms 123 ms 10ge.xe-0-1-0.wdc-eqx-dis-1.peer1.net [216.187.115.121]
8 122 ms 123 ms 124 ms 10ge.xe-1-1-0.wdc-sp225-sbcor-1.peer1.net [216.187.115.126]
9 134 ms 160 ms 138 ms 10ge.xe-0-3-0.tor-fr709-cor-1.peer1.net [216.187.120.128]
10 135 ms 135 ms 135 ms 10ge.xe-4-1-0.tor-20p1ops-dis-2.peer1.net [216.187.114.150]
11 134 ms 140 ms 133 ms 209.15.227.106
Trace complete.

5 good games in a row since this while trying to jinx it. Lucky xD

Edited by Uthael, 22 November 2014 - 03:07 PM.

[Hipsu]

Jon Cunningham, on 20 November 2014 - 10:28 AM, said:

In the mean time, please tracert these addresses:

192.99.40.103
209.15.227.106

Not sure if you meant only Blackie, but here's mine. Still from Lahti, Finland

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.0.1
2 10 ms 9 ms 12 ms 62-113-160-1.bb.dnainternet.fi [62.113.160.1]
3 9 ms 8 ms 11 ms lah1-sr8.dnaip.fi [62.78.106.84]
4 16 ms 12 ms 12 ms hol1-tr2.dnaip.fi [62.78.107.49]
5 15 ms 11 ms 12 ms esp2-tr2.dnaip.fi [62.78.107.128]
6 12 ms 12 ms 11 ms hel1-tr2.dnaip.fi [62.78.107.98]
7 23 ms 19 ms 20 ms hel5-tr3.dnaip.fi [62.78.107.125]
8 18 ms 20 ms 21 ms rai1-tr1.dnaip.fi [62.78.107.13]
9 19 ms 20 ms 20 ms tuk2-sr1.dnaip.fi [62.78.107.174]
10 20 ms 40 ms 21 ms te0-0-0-7.ccr21.sto01.atlas.cogentco.com [149.6.
168.13]
11 20 ms 19 ms 22 ms level3.sto01.atlas.cogentco.com [130.117.14.6]
12 * * * Request timed out.
13 * * * Request timed out.
14 59 ms * * fra-5-6k.fr.eu [91.121.131.5]
15 60 ms 58 ms 59 ms rbx-g2-a9.fr.eu [178.33.100.244]
16 * * 68 ms ldn-5-6k.uk.eu [91.121.131.242]
17 * * * Request timed out.
18 233 ms 220 ms 221 ms bhs-g2-6k.qc.ca [198.27.73.207]
19 199 ms 172 ms 172 ms bhs-s4-6k.qc.ca [198.27.73.146]
20 232 ms 234 ms 231 ms ns7000224.ip-192-99-40.net [192.99.40.103]

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.0.1
2 14 ms 9 ms 12 ms 62-113-160-1.bb.dnainternet.fi [62.113.160.1]
3 14 ms 8 ms 8 ms 62-113-160-1.bb.dnainternet.fi [62.113.160.1]
4 16 ms 9 ms 8 ms lah1-sr7.dnaip.fi [62.78.106.78]
5 12 ms 11 ms 11 ms lah1-tr1.dnaip.fi [62.78.107.44]
6 10 ms 11 ms 10 ms hel5-tr3.dnaip.fi [62.78.107.126]
7 11 ms 10 ms 10 ms hel1-tr2.dnaip.fi [62.78.107.124]
8 18 ms 20 ms 19 ms hel5-tr3.dnaip.fi [62.78.107.125]
9 19 ms 19 ms 19 ms rai1-tr1.dnaip.fi [62.78.107.13]
10 35 ms 20 ms 18 ms tuk3-sr1.dnaip.fi [62.78.107.176]
11 19 ms 19 ms 19 ms ae1-107.stk10.ip4.gtt.net [77.67.72.177]
12 126 ms 126 ms 127 ms xe-8-1-0.tor10.ip4.gtt.net [141.136.107.94]
13 144 ms 143 ms 142 ms peer1-gw.ip4.gtt.net [77.67.68.10]
14 * * * Request timed out.
15 143 ms 142 ms 143 ms 209.15.227.106

Trace complete.

[Blackie Flawless]

Sorry for the late reply, been out of home for the weekend.


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 6 ms 7 ms 17 ms 10.247.0.1
2 29 ms 7 ms 7 ms lah1-sr8.dnaip.fi [62.78.106.42]
3 9 ms 11 ms 10 ms hol1-tr2.dnaip.fi [62.78.107.49]
4 11 ms 9 ms 13 ms esp2-tr2.dnaip.fi [62.78.107.128]
5 8 ms 41 ms 32 ms hel1-tr2.dnaip.fi [62.78.107.98]
6 21 ms 21 ms 18 ms hel5-tr3.dnaip.fi [62.78.107.125]
7 18 ms 20 ms 22 ms rai1-tr1.dnaip.fi [62.78.107.13]
8 18 ms 35 ms 16 ms tuk2-sr1.dnaip.fi [62.78.107.174]
9 19 ms 17 ms 19 ms te0-0-0-7.ccr21.sto01.atlas.cogentco.com [149.6.
168.13]
10 18 ms 17 ms 17 ms level3.sto01.atlas.cogentco.com [130.117.14.6]
11 * * * Request timed out.
12 * * * Request timed out.
13 99 ms * 59 ms fra-5-6k.fr.eu [91.121.131.5]
14 56 ms 55 ms 59 ms rbx-g2-a9.fr.eu [178.33.100.250]
15 * 61 ms 68 ms ldn-5-6k.uk.eu [91.121.131.182]
16 * * * Request timed out.
17 272 ms 271 ms 271 ms bhs-g2-6k.qc.ca [198.27.73.207]
18 276 ms 271 ms 271 ms bhs-s4-6k.qc.ca [198.27.73.146]
19 164 ms 165 ms 169 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.

C:\>tracert 209.15.227.106

Tracing route to 209.15.227.106 over a maximum of 30 hops

1 8 ms 7 ms 7 ms 10.247.0.1
2 7 ms 8 ms 8 ms lah1-sr8.dnaip.fi [62.78.106.42]
3 9 ms 8 ms 9 ms hol1-tr2.dnaip.fi [62.78.107.49]
4 9 ms 9 ms 11 ms esp2-tr2.dnaip.fi [62.78.107.128]
5 11 ms 8 ms 10 ms hel1-tr2.dnaip.fi [62.78.107.98]
6 20 ms 21 ms 20 ms hel5-tr3.dnaip.fi [62.78.107.125]
7 17 ms 17 ms 20 ms rai1-tr1.dnaip.fi [62.78.107.13]
8 22 ms 17 ms 21 ms tuk3-sr1.dnaip.fi [62.78.107.176]
9 18 ms 19 ms 19 ms ae1-107.stk10.ip4.gtt.net [77.67.72.177]
10 127 ms 128 ms 126 ms xe-8-2-0.tor10.ip4.gtt.net [141.136.107.98]
11 139 ms 140 ms 146 ms peer1-gw.ip4.gtt.net [77.67.68.10]
12 * * * Request timed out.
13 142 ms 144 ms 141 ms 209.15.227.106

Trace complete.

[ZelloStorm]

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

1 1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 16 ms 16 ms 17 ms 217.0.119.22
3 20 ms 17 ms 19 ms 87.190.163.38
4 21 ms 20 ms 20 ms 217.239.40.242
5 21 ms * * fra-1-6k.de.eu [94.23.122.153]
6 24 ms 24 ms 24 ms sbg-g2-a9.fr.eu [91.121.128.125]
7 23 ms 24 ms 24 ms 37.187.36.155
8 * * * Zeitüberschreitung der Anforderung.
9 113 ms 113 ms 112 ms mwomercs.com [192.99.109.192]

[Oberost]

Heavy lag (400+) this afternoon. Usually I just have around 125-150, very stable.


Traza a la dirección mwomercs.com [192.99.109.192]
sobre un máximo de 30 saltos:

1 1 ms 1 ms 1 ms 192.168.0.1
2 <1 ms 1 ms <1 ms 192.168.69.1
3 * * * Tiempo de espera agotado para esta solicitud.
4 4 ms 79 ms 4 ms 10.50.2.254
5 23 ms 19 ms 20 ms 10.50.51.161
6 377 ms 381 ms 380 ms 193.149.1.81
7 371 ms 384 ms 373 ms th2-g1-a9.fr.eu [213.251.128.41]
8 409 ms 418 ms 409 ms rbx-g1-a9.fr.eu [91.121.131.209]
9 406 ms 409 ms 407 ms 37.187.36.131
10 507 ms 495 ms 472 ms 10.21.49.7
11 461 ms 452 ms 470 ms mwomercs.com [192.99.109.192]

Traza completa.

Traza a la dirección ns7000224.ip-192-99-40.net [192.99.40.103]
sobre un máximo de 30 saltos:

1 1 ms 1 ms 1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 192.168.69.1
3 * * * Tiempo de espera agotado para esta solicitud.
4 51 ms 54 ms 70 ms 10.50.2.254
5 139 ms 125 ms * 10.50.51.161
6 409 ms 409 ms * 193.149.1.81
7 * * 411 ms mad-5-6k.es.eu [94.23.122.245]
8 457 ms 450 ms 456 ms gsw-g1-a9.fr.eu [91.121.128.33]
9 461 ms 436 ms 446 ms rbx-g2-a9.fr.eu [91.121.131.213]
10 * * * Tiempo de espera agotado para esta solicitud.
11 * * * Tiempo de espera agotado para esta solicitud.
12 513 ms 534 ms 546 ms bhs-g2-6k.qc.ca [198.27.73.207]
13 543 ms 541 ms 526 ms bhs-s3-6k.qc.ca [198.27.73.142]
14 538 ms 527 ms 534 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Traza completa.


Traza a 209.15.227.106 sobre caminos de 30 saltos como máximo.

1 1 ms 2 ms 1 ms 192.168.0.1
2 1 ms <1 ms <1 ms 192.168.69.1
3 * * * Tiempo de espera agotado para esta solicitud.
4 9 ms 15 ms 5 ms 10.50.2.254
5 22 ms 23 ms 22 ms 10.50.51.161
6 62 ms 57 ms 57 ms 10.50.60.1
7 56 ms 57 ms 56 ms ams-sara-cor-1.peer1.net [80.249.209.209]
8 174 ms 211 ms 175 ms 10ge.xe-0-1-0.wdc-eqx-dis-1.peer1.net [216.187.115.121]
9 200 ms 209 ms 212 ms 10ge.xe-1-1-0.wdc-sp225-sbcor-1.peer1.net [216.187.115.126]
10 290 ms 223 ms 239 ms 10ge.xe-0-3-0.tor-fr709-cor-1.peer1.net [216.187.120.128]
11 232 ms 221 ms 221 ms 10ge.xe-4-1-0.tor-20p1ops-dis-2.peer1.net [216.187.114.150]
12 212 ms 218 ms 216 ms 209.15.227.106

Traza completa.

Edited by Oberost, 23 November 2014 - 11:29 AM.

[Chubulantk]

From Eastern WA

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

1 11 ms <1 ms <1 ms PK5001Z.PK5001Z [192.168.0.1]
2 24 ms 26 ms 21 ms 67.5.64.194
3 23 ms 23 ms 21 ms spok-agw1.inet.qwest.net [67.5.65.9]
4 55 ms 30 ms 29 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 35 ms 41 ms 30 ms ae14.edge2.Seattle1.Level3.net [4.68.62.189]
6 96 ms 178 ms 166 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
7 98 ms 173 ms 97 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
8 * * 134 ms level3.as3356.nj.us [178.32.135.18]
9 131 ms 136 ms 135 ms bhs-g1-6k.qc.ca [198.27.73.205]
10 134 ms 129 ms 132 ms 198.27.73.231
11 136 ms 133 ms 131 ms mwomercs.com [192.99.109.192]

Trace complete.

[Grey Ghost]

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?

[SogekiDan]

I never had problems before, but now I am always sitting around 400+ ping.

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

C:\Users\Sogekidan>tracert 192.99.109.192

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

1 6 ms 10 ms 7 ms 192.168.0.1
2 30 ms 26 ms cpe-72-177-0-1.austin.res.rr.com [72.177.0.1]
3 116 ms 29 ms 29 ms cpe-72-177-0-1.austin.res.rr.com [72.177.0.1]
4 19 ms 29 ms 19 ms tge3-1.ausutxla01h.texas.rr.com [66.68.5.53]
5 29 ms 35 ms 34 ms be1.ausutxla03h.texas.rr.com [24.175.41.3]
6 24 ms 28 ms 30 ms be50.ausutxla01r.texas.rr.com [24.175.43.181]
7 32 ms 37 ms 35 ms agg22.dllatxl301r.texas.rr.com [24.175.41.46]
8 34 ms 28 ms 40 ms 107.14.19.92
9 29 ms 29 ms 29 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
10 20 ms 26 ms 30 ms dls-bb1-link.telia.net [213.248.93.189]
11 79 ms 69 ms 80 ms nyk-bb2-link.telia.net [213.155.137.28]
12 79 ms 79 ms 76 ms nyk-b2-link.telia.net [213.155.130.30]
13 125 ms 123 ms nwk-1-6k.nj.us [178.32.135.212]
14 472 ms 458 ms 470 ms bhs-g1-6k.qc.ca [198.27.73.205]
15 128 ms 128 ms 129 ms 198.27.73.231
16 140 ms 119 ms 129 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\Sogekidan>

Edited by SogekiDan, 23 November 2014 - 06:24 PM.