16 replies to this topic

[Jon Cunningham]

I thought I'd go directly to each of our international forums and ask. I apologize for this request being in English.

If you do find you have bad ping, please include this information:

click start or the windows icon,
type in CMD
hit enter
type these commands:
ping mwomercs.com
tracert mwomercs.com

copy and paste that info here. Or screenshot it and upload the image somewhere.

Don't forget to include the name of your ISP and your approximate location.

[Frost Lord]

ISP Engin Location Perth Weston Australia



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

C:\Users\aaron>ping mwomercs.com

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=303ms TTL=40
Reply from 192.99.109.192: bytes=32 time=303ms TTL=40
Reply from 192.99.109.192: bytes=32 time=303ms TTL=40
Reply from 192.99.109.192: bytes=32 time=303ms TTL=40

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 303ms, Maximum = 303ms, Average = 303ms

C:\Users\aaron>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 192.168.0.1
2 78 ms 79 ms 80 ms 202-68-96-2.users.engin.com.au [202.68.96.2]
3 81 ms 82 ms 80 ms 203.161.168.65
4 79 ms 79 ms 79 ms 203.161.169.2
5 78 ms 79 ms 80 ms 203.161.168.1
6 80 ms 81 ms 80 ms 77.0.148.122.network.m2core.net.au [122.148.0.77
]
7 79 ms 80 ms 79 ms 119.225.42.181
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 253 ms 252 ms 252 ms 59.154.142.226
12 * * * Request timed out.
13 * * * Request timed out.
14 274 ms 274 ms 275 ms 59.154.142.236
15 335 ms 280 ms 280 ms 203.208.190.69
16 274 ms 275 ms 274 ms 203.208.173.138
17 * * * Request timed out.
18 286 ms * * 198.27.73.186
19 * * * Request timed out.
20 304 ms 305 ms 304 ms bhs-g1-6k.qc.ca [198.27.73.5]
21 305 ms 304 ms 304 ms 198.27.73.231
22 303 ms 303 ms 304 ms mwomercs.com [192.99.109.192]

Trace complete.

[Taj]

Maybe it's not on Polish Forum but i post our ping too.
We (Polish Community) got "bad" ping too. ~140-250.

Spoiler

Microsoft Windows [Wersja 6.1.7601]


ping mwomercs.com

Badanie mwomercs.com [192.99.109.192] z 32 bajtami danych:
Odpowiedź z 192.99.109.192: bajtów=32 czas=223ms TTL=50
Odpowiedź z 192.99.109.192: bajtów=32 czas=155ms TTL=50
Odpowiedź z 192.99.109.192: bajtów=32 czas=194ms TTL=50
Odpowiedź z 192.99.109.192: bajtów=32 czas=154ms TTL=50

Statystyka badania ping dla 192.99.109.192:
Pakiety: Wysłane = 4, Odebrane = 4, Utracone = 0

Szacunkowy czas błądzenia pakietów w millisekundach:
Minimum = 154 ms, Maksimum = 223 ms, Czas średni = 181 ms

tracert mwomercs.com

Śledzenie trasy do mwomercs.com [192.99.109.192] z maksymalną liczbą 30 przeskoków:

1 12 ms 2 ms 14 ms epu89.internetdsl.tpnet.pl [83.12.128.89]
2 60 ms 137 ms 110 ms lodz-ru1.idsl.tpnet.pl [213.25.2.134]
3 551 ms 211 ms 186 ms lodz-r2.tpnet.pl [213.25.5.209]
4 167 ms 118 ms 134 ms kat-r2.tpnet.pl [194.204.175.174]
5 145 ms 103 ms 303 ms bundle-ether4.ffttr3.Frankfurt.opentransit.net [193.251.249.9]
6 * * * Upłynął limit czasu żądania.
7 172 ms 143 ms 111 ms sbg-g1-a9.fr.eu [91.121.128.80]
8 95 ms 270 ms 96 ms 37.187.36.153
9 * * * Upłynął limit czasu żądania.
10 235 ms 422 ms 226 ms mwomercs.com [192.99.109.192]

Śledzenie zakończone. (Trace complete.)

Edited by Taj, 13 January 2015 - 04:37 AM.

[Jeka Vorobyov]

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=165ms TTL=52
Reply from 192.99.109.192: bytes=32 time=166ms TTL=52
Reply from 192.99.109.192: bytes=32 time=165ms TTL=52
Reply from 192.99.109.192: bytes=32 time=166ms TTL=52

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 166ms, Average = 165ms


Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=165ms TTL=52
Reply from 192.99.109.192: bytes=32 time=166ms TTL=52
Reply from 192.99.109.192: bytes=32 time=165ms TTL=52
Reply from 192.99.109.192: bytes=32 time=166ms TTL=52

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 166ms, Average = 165ms

Location: Israel

[FlipOver]

Location: Portugal, Lisbon
Usual ping: 111-120

Most other Portuguese player have pings between 130 and 160.

------
>ping mwomercs.com

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=113ms TTL=53
Reply from 192.99.109.192: bytes=32 time=113ms TTL=53
Reply from 192.99.109.192: bytes=32 time=114ms TTL=53
Reply from 192.99.109.192: bytes=32 time=115ms TTL=53

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 115ms, Average = 113ms

>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 zonhub.home [192.168.1.2]
2 * * * Request timed out.
3 8 ms 11 ms 8 ms 10.137.208.129
4 9 ms 8 ms 8 ms 10.255.48.82
5 7 ms 7 ms 8 ms ix-0-3-1-0.tcore2.PV9-Lisbon.as6453.net [195.219
.214.49]
6 42 ms 45 ms 71 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.
5]
7 42 ms 40 ms 45 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.
158.30]
8 41 ms 42 ms 65 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.
139.1]
9 40 ms 41 ms 40 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139
.42]
10 41 ms 42 ms 42 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130
.130]
11 * * * Request timed out.
12 42 ms 41 ms 45 ms rbx-g2-a9.fr.eu [91.121.131.243]
13 44 ms 40 ms 40 ms 37.187.36.133
14 * * * Request timed out.
15 114 ms 114 ms 117 ms mwomercs.com [192.99.109.192]

Trace complete.

[Tarogato]

I'm in NA, but I've been getting ping spikes the past 2-3 days so I figured I'd contribute as well.

Ping 1 (70ms)

Spoiler

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=54ms TTL=51
Reply from 192.99.109.192: bytes=32 time=59ms TTL=51
Reply from 192.99.109.192: bytes=32 time=84ms TTL=51
Reply from 192.99.109.192: bytes=32 time=86ms TTL=51

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 86ms, Average = 70ms

Ping 2 (624ms... pinged mere moments after the first one)

Spoiler

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=593ms TTL=51
Reply from 192.99.109.192: bytes=32 time=630ms TTL=51
Reply from 192.99.109.192: bytes=32 time=559ms TTL=51
Reply from 192.99.109.192: bytes=32 time=716ms TTL=51

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 559ms, Maximum = 716ms, Average = 624ms

Tracert

Spoiler

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

1 87 ms 86 ms 129 ms CISCO01770 [192.168.1.1]
2 * * * Request timed out.
3 160 ms 61 ms 29 ms te-8-4-ur01.indiana.pa.pitt.comcast.net [68.85.7
2.49]
4 88 ms 27 ms 39 ms te-8-3-ur03.blairsville.pa.pitt.comcast.net [68.
86.100.177]
5 110 ms 80 ms 89 ms te-8-7-ur04.blairsville.pa.pitt.comcast.net [68.
87.173.98]
6 142 ms 80 ms 74 ms te-0-4-0-3-ar03.mckeesport.pa.pitt.comcast.net [
68.87.173.102]
7 52 ms 107 ms 63 ms be-7016-cr01.ashburn.va.ibone.comcast.net [68.86
.91.25]
8 69 ms 64 ms 61 ms pos-0-5-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.85.26]
9 68 ms 58 ms 85 ms he-0-11-0-1-pe03.111eighthave.ny.ibone.comcast.n
et [68.86.83.102]
10 * * 210 ms 198.27.73.61
11 * * * Request timed out.
12 119 ms 207 ms 420 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 259 ms 222 ms 509 ms 198.27.73.231
14 436 ms 471 ms 381 ms mwomercs.com [192.99.109.192]

Trace complete.

I literally know nothing about this kind of stuff, so it might be on my end, but I hope it helps anyways.

Actual location: Indiana, PA
ISP: Comcast
Usual avg in game ping: ~34ms

---

Here's a control ping and tracert to google:

Spoiler

Pinging google.com [173.194.123.3] with 32 bytes of data:
Reply from 173.194.123.3: bytes=32 time=139ms TTL=53
Reply from 173.194.123.3: bytes=32 time=237ms TTL=53
Reply from 173.194.123.3: bytes=32 time=86ms TTL=53
Reply from 173.194.123.3: bytes=32 time=130ms TTL=53

Ping statistics for 173.194.123.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 237ms, Average = 148ms

---

Tracing route to google.com [173.194.123.3]
over a maximum of 30 hops:

1 10 ms 11 ms 14 ms CISCO01770 [192.168.1.1]
2 * * * Request timed out.
3 69 ms 40 ms 17 ms te-8-4-ur01.indiana.pa.pitt.comcast.net [68.85.7
2.49]
4 124 ms 60 ms 53 ms te-9-3-ur01.punxy.pa.pitt.comcast.net [68.87.173
.81]
5 38 ms 72 ms 33 ms te-9-3-ur01.ruralvalley.pa.pitt.comcast.net [68.
87.173.77]
6 46 ms 59 ms 38 ms te-0-2-0-0-ar01.pittsburgh.pa.pitt.comcast.net [
68.86.100.182]
7 117 ms 102 ms 49 ms be-7016-cr01.newyork.ny.ibone.comcast.net [68.86
.91.29]
8 144 ms 90 ms 59 ms he-0-10-0-0-pe03.111eighthave.ny.ibone.comcast.n
et [68.86.83.90]
9 59 ms 42 ms 37 ms as15169-2-c.111eighthave.ny.ibone.comcast.net [2
3.30.206.126]
10 84 ms 123 ms 99 ms 209.85.248.178
11 76 ms 63 ms 88 ms 72.14.239.245
12 284 ms 335 ms 181 ms lga15s46-in-f3.1e100.net [173.194.123.3]

Trace complete.

Edited by Tarogato, 19 January 2015 - 06:59 PM.

[Phoenix Wolf]

Location: Pilisszentivan/Hungary
ISP: Magyar Telekom
My usual ping: 145-180 (it is the same for the majority of Hungarian players)

>ping mwomercs.com
Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=154ms TTL=49
Reply from 192.99.109.192: bytes=32 time=157ms TTL=49
Reply from 192.99.109.192: bytes=32 time=161ms TTL=49
Reply from 192.99.109.192: bytes=32 time=156ms TTL=49

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 154ms, Maximum = 161ms, Average = 157ms

>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 READYSHARE [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.2.254
3 18 ms 17 ms 17 ms rsr1-ferenc.net.telekom.hu [145.236.224.102]
4 19 ms 18 ms 17 ms fogl.er-osr-ferenc.net.telekom.hu.1.84.in-addr.a
rpa [84.1.85.18]
5 18 ms 18 ms 17 ms xe-2-3-1.ic0-ip2.net.telekom.hu [81.183.2.228]
6 17 ms 17 ms 17 ms 81.183.1.98
7 40 ms 39 ms 39 ms 193.159.166.253
8 35 ms 35 ms 35 ms 217.239.52.126
9 * 70 ms 47 ms fra-1-6k.de.eu [94.23.122.153]
10 39 ms 38 ms 39 ms sbg-g2-a9.fr.eu [91.121.128.82]
11 38 ms 38 ms 38 ms 37.187.36.155
12 * * * Request timed out.
13 157 ms 159 ms 162 ms mwomercs.com [192.99.109.192]

Trace complete.

[12Bravo]

The problems with Hop 7 started this morning...

[12Bravo]

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 3 ms 2 ms 2 ms 8.24.110.1
3 3 ms 3 ms 3 ms 192.168.2.1
4 5 ms 5 ms 5 ms te-4-3.car2.Minneapolis1.Level3.net [4.59.66.101]
5 * * * Request timed out.
6 * * * Request timed out.
7 421 ms 436 ms 422 ms bhs-g1-6k.qc.ca [198.27.73.1]
8 38 ms 38 ms 38 ms 198.27.73.231
9 37 ms 37 ms 37 ms mwomercs.com [192.99.109.192]

One more, it seems pretty consistent.

[Darkblood]

Hey, so nice to see you´re worrying with our "pilgrim packets"

I´m in São Paulo, Brazil, and I have two different ISP: Net Virtua (cable, labelled NET below) and VIVO (optic fiber, labelled vivo below). I tested both, it is a bit time-of-day dependent, so I´m sending the best results, only attained at night (time indicated below), during the day I have from 250 ms to 350 ms.


_____________________________________________________________________Vivo 22:12

ping mwomercs.com

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=161ms TTL=54
Reply from 192.99.109.192: bytes=32 time=196ms TTL=54
Reply from 192.99.109.192: bytes=32 time=161ms TTL=54
Reply from 192.99.109.192: bytes=32 time=161ms TTL=54

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 161ms, Maximum = 196ms, Average = 169ms

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 192.168.0.1
2 1 ms 1 ms 1 ms DMG-6661 [192.168.1.1]
3 * * * Request timed out.
4 3 ms 2 ms 2 ms 187-100-37-93.dsl.telesp.net.br [187.100.37.93]
5 3 ms 2 ms 2 ms 187-100-78-145.dsl.telesp.net.br [187.100.78.145]
6 3 ms 3 ms 2 ms 187-100-34-153.dsl.telesp.net.br [187.100.34.153]
7 59 ms 3 ms 4 ms 213.140.50.5
8 115 ms 110 ms 114 ms Te0-7-0-5-grtmiabr6.red.telefonica-wholesale.net [94.142.123.254]
9 * 142 ms 141 ms Xe3-1-7-grtwaseq6.red.telefonica-wholesale.net [5.53.6.212]
10 110 ms 110 ms 109 ms mia-1-6k.fl.us [178.32.135.52]
11 * * 139 ms nwk-2-6k.nj.us [198.27.73.201]
12 163 ms 163 ms * 192.99.146.86
13 148 ms 148 ms 196 ms 192.99.146.86
14 182 ms 182 ms 182 ms 198.27.73.233
15 161 ms 162 ms 196 ms mwomercs.com [192.99.109.192]

Trace complete.


_____________________________________________________________________Net 22:28


ping mwomercs.com

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=193ms TTL=51
Reply from 192.99.109.192: bytes=32 time=223ms TTL=51
Reply from 192.99.109.192: bytes=32 time=205ms TTL=51
Reply from 192.99.109.192: bytes=32 time=201ms TTL=51

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 193ms, Maximum = 223ms, Average = 205ms

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 192.168.0.1
2 33 ms 20 ms 19 ms bacc3801.virtua.com.br [186.204.56.1]
3 9 ms 10 ms 10 ms c906009e.virtua.com.br [201.6.0.158]
4 9 ms 11 ms 8 ms c9062851.virtua.com.br [201.6.40.81]
5 9 ms 12 ms 10 ms embratel-T0-0-0-2-uacc01.spo.embratel.net.br [201.56.239.9]
6 29 ms 11 ms * 200.244.212.3
7 127 ms 127 ms 128 ms ebt-P0-6-2-0-intl02.nyk.embratel.net.br [200.230.251.254]
8 169 ms 164 ms 163 ms nyk-b3-link.telia.net [62.115.33.1]
9 143 ms 140 ms 145 ms nyk-bb1-link.telia.net [80.91.247.18]
10 185 ms * 185 ms nyk-b2-link.telia.net [213.155.130.28]
11 149 ms * 165 ms nwk-1-6k.nj.us [178.32.135.212]
12 155 ms 159 ms 162 ms 192.99.146.84
13 190 ms 192 ms 188 ms 198.27.73.231
14 * 165 ms 160 ms mwomercs.com [192.99.109.192]

Trace complete.

[Shaix]

I am located in Taipei Taiwan and I used to have 200ms ping time. Now for past few days I have 270-300ms. Name of the ISP is FarEasTone or Seed.net.tw.

C:\Windows\system32>ping mwomercs.com

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=269ms TTL=52
Reply from 192.99.109.192: bytes=32 time=270ms TTL=52
Reply from 192.99.109.192: bytes=32 time=279ms TTL=52
Reply from 192.99.109.192: bytes=32 time=271ms TTL=52

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 269ms, Maximum = 279ms, Average = 272ms

C:\Windows\system32>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 router.asus.com [192.168.2.2]
2 5 ms 5 ms 4 ms tp240-20.dialup.seed.net.tw [139.175.240.20]
3 13 ms 4 ms 5 ms h129-192-72-46.seed.net.tw [192.72.46.129]
4 5 ms 5 ms 5 ms R58-145.seed.net.tw [139.175.58.145]
5 5 ms 5 ms 5 ms R59-194.seed.net.tw [139.175.59.194]
6 5 ms 5 ms 5 ms xe-4-0-0.r01.taiptw01.tw.bb.gin.ntt.net [61.58.33.213]
7 42 ms 27 ms 27 ms as-0.r22.tkokhk01.hk.bb.gin.ntt.net [129.250.4.140]
8 62 ms 62 ms 62 ms ae-7.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.6.46]
9 60 ms 58 ms 60 ms ae-2.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.3.147]
10 60 ms 61 ms 60 ms ae0.singapore2.sin.seabone.net [93.186.133.12]
11 284 ms 274 ms 276 ms xe-0-3-0.milano51.mil.seabone.net [195.22.196.133]
12 * * * Request timed out.
13 267 ms * 268 ms fra-1-6k.de.eu [213.251.128.66]
14 267 ms 269 ms 269 ms rbx-s11-6k.fr.eu [91.121.131.250]
15 332 ms 269 ms 271 ms 37.187.36.153
16 * * * Request timed out.
17 270 ms 270 ms 269 ms mwomercs.com [192.99.109.192]

Trace complete.

[Shaix]

Here is a ping and traceroute from a different ISP in Taipei Chunghwa Telecom (hinet.net), it gets ~200ms, while my ISP FarEasTone (Seed.net.tw) is even worse now...

traceroute to mwomercs.com (192.99.109.192), 64 hops max, 52 byte packets
1 zyxel.home (192.168.1.1) 1.327 ms 1.099 ms 1.907 ms
2 h254.s98.ts.hinet.net (168.95.98.254) 16.470 ms 11.134 ms 11.112 ms
3 tpdb-3316.hinet.net (168.95.25.26) 14.413 ms 12.284 ms 12.463 ms
4 tpdt-3011.hinet.net (220.128.3.134) 24.494 ms
tpdt-3012.hinet.net (220.128.2.10) 21.515 ms
tpdt-3012.hinet.net (220.128.4.114) 18.307 ms
5 r4101-s2.tp.hinet.net (220.128.7.117) 18.764 ms 11.087 ms 10.050 ms
6 r4001-s2.tp.hinet.net (220.128.11.133) 12.732 ms 12.000 ms 10.144 ms
7 r11-pa.us.hinet.net (211.72.108.153) 141.521 ms
r11-pa.us.hinet.net (211.72.108.21) 149.050 ms
r11-pa.us.hinet.net (211.72.108.197) 138.059 ms
8 r12-pa.us.hinet.net (202.39.83.46) 139.656 ms 139.377 ms 133.622 ms
9 pal-1-6k.ca.us (178.32.135.98) 143.444 ms * *
10 chi-2-6k.il.us (198.27.73.184) 188.330 ms * *
11 mtl-2-6k.qc.ca (198.27.73.173) 218.822 ms 217.429 ms 219.461 ms
12 bhs-g2-6k.qc.ca (198.27.73.7) 232.067 ms 209.311 ms 219.914 ms
13 198.27.73.233 (198.27.73.233) 248.733 ms 254.925 ms 257.680 ms
14 mwomercs.com (192.99.109.192) 200.980 ms !Z 209.309 ms !Z 204.997 ms !Z


ping mwomercs.com
PING mwomercs.com (192.99.109.192): 56 data bytes
64 bytes from 192.99.109.192: icmp_seq=0 ttl=52 time=204.836 ms
64 bytes from 192.99.109.192: icmp_seq=1 ttl=52 time=201.301 ms
64 bytes from 192.99.109.192: icmp_seq=2 ttl=52 time=206.137 ms
64 bytes from 192.99.109.192: icmp_seq=3 ttl=52 time=206.119 ms
64 bytes from 192.99.109.192: icmp_seq=4 ttl=52 time=207.196 ms
^C
--- mwomercs.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 201.301/205.118/207.196/2.050 ms


Here is from my ISP in Taipei:


Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=300ms TTL=46
Reply from 192.99.109.192: bytes=32 time=300ms TTL=46
Reply from 192.99.109.192: bytes=32 time=311ms TTL=46
Reply from 192.99.109.192: bytes=32 time=301ms TTL=46

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 300ms, Maximum = 311ms, Average = 303ms



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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.2.2]
2 5 ms 4 ms 5 ms tp240-20.dialup.seed.net.tw [139.175.240.20]
3 15 ms 5 ms 5 ms h1-192-72-46.seed.net.tw [192.72.46.1]
4 5 ms 5 ms 5 ms R58-145.seed.net.tw [139.175.58.145]
5 12 ms 33 ms 5 ms R59-194.seed.net.tw [139.175.59.194]
6 5 ms 5 ms 5 ms xe-4-0-0.r01.taiptw01.tw.bb.gin.ntt.net [61.58.33.213]
7 5 ms 5 ms 5 ms ae-1.r00.taiptw01.tw.bb.gin.ntt.net [129.250.3.206]
8 54 ms 44 ms 43 ms as-2.r22.tokyjp01.jp.bb.gin.ntt.net [129.250.8.129]
9 * 85 ms 85 ms ae-5.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.39]
10 91 ms 86 ms 87 ms ae-11.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.7.22]
11 86 ms * 85 ms ae-2.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.3.147]
12 84 ms 85 ms 84 ms ae0.singapore2.sin.seabone.net [93.186.133.12]
13 312 ms 310 ms 310 ms et-7-3-0.milano51.mil.seabone.net [195.22.196.191]
14 * * * Request timed out.
15 318 ms 323 ms 408 ms fra-1-6k.de.eu [213.251.128.66]
16 331 ms 332 ms 332 ms rbx-s11-6k.fr.eu [91.121.131.250]
17 310 ms 310 ms 310 ms 37.187.36.153
18 * * * Request timed out.
19 300 ms 301 ms 300 ms mwomercs.com [192.99.109.192]

Trace complete.

[GenBeco]

ISP Telstra Location Adelaide South australia

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

C:\Users\Geco>ping mwomercs.com

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=296ms TTL=43
Reply from 192.99.109.192: bytes=32 time=296ms TTL=43
Reply from 192.99.109.192: bytes=32 time=298ms TTL=43
Reply from 192.99.109.192: bytes=32 time=304ms TTL=43

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 296ms, Maximum = 304ms, Average = 298ms

C:\Users\Geco>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 BigPond.BigPond [10.0.0.138]
2 32 ms 31 ms 32 ms 172.18.214.100
3 34 ms 38 ms 31 ms 172.18.71.125
4 37 ms 32 ms 31 ms bundle-ether4.fli-edge901.adelaide.telstra.net [
203.50.116.100]
5 33 ms 35 ms 38 ms bundle-ether8.fli-core1.adelaide.telstra.net [20
3.50.11.154]
6 45 ms 51 ms 55 ms bundle-ether9.win-core10.melbourne.telstra.net [
203.50.11.91]
7 55 ms 58 ms 64 ms bundle-ether12.ken-core10.sydney.telstra.net [20
3.50.11.122]
8 57 ms 59 ms 65 ms Bundle-ether18.pad-gw2.sydney.telstra.net [203.5
0.13.82]
9 70 ms 58 ms 55 ms bundle-ether1.sydp-core01.sydney.reach.com [203.
50.13.46]
10 203 ms 192 ms 204 ms i-0-1-0-3.paix-core01.bx.telstraglobal.net [202.
84.140.218]
11 198 ms 208 ms 199 ms i-0-5-0-5.paix02.bi.telstraglobal.net [202.40.14
9.126]
12 190 ms 191 ms 192 ms xe-5-3-0.paloalto2.pao.seabone.net [195.22.206.1
29]
13 289 ms 291 ms 281 ms xe-1-0-1.miami15.mia.seabone.net [195.22.199.7]

14 281 ms 288 ms 288 ms xe-1-3-0.miami15.mia.seabone.net [195.22.199.111
]
15 285 ms 291 ms 331 ms mia-1-6k.fl.us [178.32.135.208]
16 308 ms 319 ms 305 ms nwk-1-6k.nj.us [198.27.73.199]
17 293 ms 308 ms 330 ms bhs-g1-6k.qc.ca [198.27.73.205]
18 293 ms 294 ms 298 ms 198.27.73.231
19 292 ms 293 ms 292 ms mwomercs.com [192.99.109.192]

Trace complete.

[Victus B]

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\---->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 192.168.--.--
2 * * * Request timed out.
3 21 ms 23 ms 23 ms 192.168.--.--
4 9 ms 10 ms 8 ms 10.224.252.50
5 25 ms 44 ms 24 ms 10.224.252.45
6 24 ms 24 ms 23 ms ae12.mpr3.atl6.us.zip.zayo.com [208.184.232.177]
7 24 ms 22 ms 23 ms ae4.mpr4.atl6.us.zip.zayo.com [64.125.31.198]
8 111 ms 122 ms 109 ms ae28.cs1.dca2.us.zip.zayo.com [64.125.31.168]
9 109 ms 153 ms 109 ms ae5.cs1.lhr15.uk.eth.zayo.com [64.125.29.130]
10 110 ms 109 ms 109 ms ae27.mpr3.lhr3.uk.zip.zayo.com [64.125.30.235]
11 111 ms 108 ms 109 ms ae6.mpr2.lhr3.uk.zip.zayo.com [64.125.21.22]
12 * * * Request timed out.
13 112 ms 113 ms 113 ms be10-1193.gra-g1-a9.fr.eu [91.121.128.90]
14 112 ms 111 ms 110 ms vl21.gra-g1-a75.fr.eu [213.251.128.43]
15 115 ms 115 ms 118 ms gra-g5-a9.fr.eu [37.187.36.182]
16 * * * Request timed out.
17 118 ms 119 ms 119 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\---->ping mwomercs.com

Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=119ms TTL=48
Reply from 192.99.109.192: bytes=32 time=118ms TTL=48
Reply from 192.99.109.192: bytes=32 time=119ms TTL=48
Reply from 192.99.109.192: bytes=32 time=118ms TTL=48

Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 119ms, Average = 118ms

C:\Users\---->
----------------------------------------------------------

This is a pretty consistent result over the past week from the southern USA, Cableone is the ISP. For reference avg ping to google.com is 23ms and ping in other games such as World of Tanks and Warthunder is between 25-60ms depending on time of day.

This crap ping is accompanied by a VERY unstable connection making games (esp CW games) very unstable with desync in nearly every drop and complete disconnects at least 2 times per hour. At this point I have written off MWO as a game to play as the satisfaction from playing does not equal or exceed the frustration.

UPDATE:I called my ISP and they traced it as well and thru alot of technomumblejumble said its basicaly the targeted IP (MWO) that is responsible for the roundabout. Something about their servers and prioritizing traffic. I am not a network admin guy so I can't call BS on anyone, however the ISP says the reason for the unusual path to Europe and back for a NA server is the fault of MWO.

I am inclined to believe them from a laypersons perspective as I play several online games and NONE of them do this. For shits and grins I did tracert to alot of high traffic servers like youtube and steam and whatnot, none of them do this.

TL;DR= MWO is not worth the headache. go play something else.

Edited by Victus B, 05 May 2016 - 11:56 AM.

[Dianesion]

Its been one week and all my friends from Brazil are having serious ping issues.

It seems to be a problem at the Backbone of Miami.

My ping was around 150 - 160 and now its 250 - 280 during matches. Its just impossible to face Cannadian teams with that sort of ping.

Microsoft Windows [versão 10.0.10586]
(c) 2015 Microsoft Corporation. Todos os direitos reservados.

C:\WINDOWS\System32>ping mwomercs.com

Disparando mwomercs.com [192.99.109.192] com 32 bytes de dados:
Resposta de 192.99.109.192: bytes=32 tempo=250ms TTL=46
Resposta de 192.99.109.192: bytes=32 tempo=250ms TTL=46
Resposta de 192.99.109.192: bytes=32 tempo=254ms TTL=46
Resposta de 192.99.109.192: bytes=32 tempo=260ms TTL=46

Estatísticas do Ping para 192.99.109.192:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 250ms, Máximo = 260ms, Média = 253ms

C:\WINDOWS\System32>tracert mwomercs.com

Rastreando a rota para mwomercs.com [192.99.109.192]
com no máximo 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.25.1
2 5 ms 5 ms 5 ms gvt-b-se01.gna.gvt.net.br [189.59.241.134]
3 6 ms 6 ms 5 ms 179.184.82.233.dynamic.adsl.gvt.net.br [179.184.82.233]
4 9 ms 6 ms 6 ms gvt-te-0-4-0-9.rc02.gna.gvt.net.br [179.184.121.215]
5 22 ms 22 ms 22 ms gvt-te-0-5-0-6.rc02.bhe.gvt.net.br [179.185.131.9]
6 32 ms 30 ms 30 ms gvt-te-0-5-0-9.rc02.spo.gvt.net.br [177.99.248.202]
7 30 ms 30 ms 30 ms gvt-te-0-0-0-10.rt01.spo.gvt.net.br [187.115.214.190]
8 30 ms 30 ms 31 ms ip-208.48.13.105.gblx.net [208.48.13.105]
9 71 ms 130 ms 62 ms telecomitalia-1.ar4.GRU1.gblx.net [64.208.27.86]
10 167 ms 161 ms 165 ms et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
11 157 ms 170 ms 170 ms et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
12 * * * Esgotado o tempo limite do pedido.
13 219 ms 219 ms 219 ms be100-1036.nwk-1-a9.nj.us [198.27.73.199]
14 241 ms 238 ms 234 ms be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
15 234 ms 233 ms 231 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
16 234 ms 239 ms 240 ms bhs-g5-a9.qc.ca [178.32.135.194]
17 250 ms 250 ms 253 ms mwomercs.com [192.99.109.192]

Rastreamento concluído.

C:\WINDOWS\System32>

[lkraider]

Country: Brazil
ISP: NET Virtua

ping mwomercs.com

Pinging mwomercs.com [192.99.109.143] with 32 bytes of data:
Reply from 192.99.109.143: bytes=32 time=177ms TTL=53
Reply from 192.99.109.143: bytes=32 time=178ms TTL=53
Reply from 192.99.109.143: bytes=32 time=176ms TTL=53
Reply from 192.99.109.143: bytes=32 time=175ms TTL=53

Ping statistics for 192.99.109.143:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 175ms, Maximum = 178ms, Average = 176ms

tracert mwomercs.com

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2	 *	    *	    *	 Request timed out.
  3	 7 ms	 9 ms	 8 ms  flnctrrtd01.fln.virtua.com.br [189.4.64.x]
  4    13 ms	 8 ms    10 ms  flndtcrtd04.fln.virtua.com.br [189.4.64.4]
  5    20 ms    21 ms    21 ms  embratel-G0-0-0-0-uacc01.spoph.embratel.net.br [200.245.154.41]
  6    22 ms    23 ms    23 ms  ebt-T0-4-0-5-tcore01.spo.embratel.net.br [200.230.252.26]
  7   135 ms   134 ms   131 ms  ebt-BP1114-intl04.mianap.embratel.net.br [200.230.220.66]
  8   134 ms	 *	  134 ms  po100-153.mia-5-6k.fl.us [192.99.146.104]
  9   168 ms   166 ms   166 ms  be100-1034.nwk-1-a9.nj.us [198.27.73.169]
 10   178 ms   181 ms   178 ms  be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
 11   172 ms   173 ms   173 ms  vl21.bhs-g1-a75.qc.ca [198.27.73.63]
 12   173 ms   172 ms   176 ms  bhs-g5-a9.qc.ca [178.32.135.194]
 13   176 ms   175 ms   175 ms  192.99.109.143

Trace complete.

[lobo gris]

Hello.
play form Santiago de Chile, ISP is VTR

Haciendo ping a mwomercs.com [192.99.109.143] con 32 bytes de datos:
Respuesta desde 192.99.109.143: bytes=32 tiempo=226ms TTL=50
Respuesta desde 192.99.109.143: bytes=32 tiempo=213ms TTL=49
Respuesta desde 192.99.109.143: bytes=32 tiempo=212ms TTL=49
Respuesta desde 192.99.109.143: bytes=32 tiempo=220ms TTL=49

Estadísticas de ping para 192.99.109.143:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 212ms, Máximo = 226ms, Media = 217ms


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

1 1 ms 4 ms 8 ms 192.168.0.1
2 * * * Tiempo de espera agotado para esta solicitud.
3 18 ms 27 ms 25 ms 10.68.231.62
4 24 ms 37 ms 29 ms 192.168.23.18
5 24 ms 26 ms 26 ms 192.168.15.18
6 26 ms 27 ms 26 ms te4-2.ar3.SCL1.gblx.net [208.48.250.61]
7 177 ms 176 ms 176 ms ae0-90G.ar7.LAX1.gblx.net [67.16.162.22]
8 177 ms 168 ms 166 ms ae10.edge1.LosAngeles9.Level3.net [4.68.111.21]
9 * * * Tiempo de espera agotado para esta solicitud.
10 208 ms 205 ms 208 ms be100-104.nwk-1-a9.nj.us [192.99.146.253]
11 213 ms 216 ms 217 ms be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
12 216 ms 214 ms 209 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
13 212 ms 218 ms 216 ms bhs-g5-a9.qc.ca [178.32.135.194]
14 279 ms 216 ms 216 ms 192.99.109.143

Traza completa.

thanks!

Edited by lobo gris, 19 September 2016 - 03:37 PM.