179 replies to this topic

[Votanin FleshRender]

Ping is usually fine, but will occasionally shoot to up over 5000.

Ping was 500ish when I did these traces.

1st trace

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

1 9 ms 4 ms 2 ms homeportal [192.168.1.254]
2 441 ms 454 ms 449 ms 76-236-0-3.lightspeed.gdrpmi.sbcglobal.net [76.2
36.0.3]
3 491 ms 499 ms 503 ms 75.29.192.90
4 641 ms 647 ms 561 ms 12.83.33.145
5 456 ms 458 ms 458 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 * * * Request timed out.
7 720 ms 332 ms 373 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
8 406 ms 416 ms 428 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
9 * * * Request timed out.
10 687 ms 507 ms 373 ms bhs-g1-6k.qc.ca [198.27.73.205]
11 365 ms 379 ms 398 ms 198.27.73.231
12 535 ms 553 ms 556 ms mwomercs.com [192.99.109.192]

Trace complete.


2nd trace

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

1 3 ms 1 ms 3 ms homeportal [192.168.1.254]
2 482 ms 490 ms 512 ms 76-236-0-3.lightspeed.gdrpmi.sbcglobal.net [76.2
36.0.3]
3 * * * Request timed out.
4 567 ms 574 ms 590 ms 12.83.33.145
5 * 622 ms 627 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 * * * Request timed out.
7 524 ms 530 ms 541 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
8 * 636 ms 642 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
9 * * 401 ms level3.as3356.nj.us [178.32.135.18]
10 446 ms 455 ms 474 ms bhs-g1-6k.qc.ca [198.27.73.205]
11 491 ms 508 ms 510 ms 198.27.73.231
12 338 ms 405 ms 534 ms mwomercs.com [192.99.109.192]

Trace complete.

Edited by Votanin FleshRender, 23 November 2014 - 10:37 PM.

[l33tworks]

I don't get it. The pings here seem fine, but the Game is next to unplayable atm. My ping can range from 500 to where game play is extremer jerky to 5000 where everyone is running on the spot for 10 seconds then the game catches up everyone runs fast things blow up and rinse and repeat every 10 seconds.

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

1 <1 ms <1 ms <1 ms 10.1.1.1
2 28 ms 27 ms 28 ms 160.1.233.220.static.exetel.com.au [220.233.1.16
0]
3 29 ms 28 ms 28 ms 10.1.21.45
4 28 ms 28 ms 28 ms 10.1.21.27
5 28 ms 27 ms 28 ms 161.43.102.1
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 29 ms 30 ms 30 ms 59.154.142.238
10 185 ms 185 ms 186 ms 203.208.190.17
11 186 ms 185 ms 186 ms 203.208.172.242
12 * * * Request timed out.
13 * * * Request timed out.
14 * 244 ms 246 ms 198.27.73.181
15 256 ms 251 ms 255 ms bhs-g2-6k.qc.ca [198.27.73.7]
16 247 ms 247 ms 246 ms 198.27.73.233
17 247 ms 248 ms 247 ms mwomercs.com [192.99.109.192]

Trace complete.

What exactly is the problem?

Somehow it seems to be related to peak traffic for my ISP timezone. For example the problem is worst between 3pm and 11pm and then gets better between 11pm to 1am and then 1am to say 2pm its very good back down to 250 ping then the cycle repeats. I think if there is any kind of congestion the game throws a fit?

Edited by l33tworks, 24 November 2014 - 05:38 AM.

[SoggyGorilla]

guys have you noticed that 90% of people that are complaining about lag are hitting the same 2 routers?

bhs-g1-6k.qc.ca and bhs-g2-6k.qc.ca doesnt that put a red flag up?

[SoggyGorilla]

hmm i almost thought my problems would be fixed last week.

but then i saw this today...


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

Comment by OVH - Monday, 24 November 2014, 17:09PM[color=#000000]
We are still awaiting the delivery of our lines from the supplier. The date is now for December 14, 2014.[/color]

[Colonel Jaime Wolf]

All the guys I play with from the Philippines have an average of 276 ping. Some days it shoots up to 350 average. it was much lower last year before that major server thing.

I'll wager we'll spend more cash if we had better ping. thanks


----------------------------------------------------------------------------


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

C:\Users\Oliver Buenaflor>ce..
'ce..' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Oliver Buenaflor>cd..

C:\Users>cd..

C:\>tracert 192.99.109.192

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

1 2 ms 2 ms 2 ms 192.168.1.1
2 26 ms 24 ms 23 ms 124.107.165.254.pldt.net [124.107.165.254]
3 25 ms 26 ms 25 ms 122.2.135.105.pldt.net [122.2.135.105]
4 25 ms 26 ms 25 ms 210.213.130.106.static.pldt.net [210.213.130.106
]
5 24 ms 24 ms 25 ms 210.213.130.158.static.pldt.net [210.213.130.158
]
6 209 ms * 224 ms so-4-0-0.edge5.Seattle1.Level3.net [4.30.140.1]

7 245 ms 246 ms 245 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
8 246 ms 245 ms 246 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
9 * * * Request timed out.
10 267 ms 266 ms 266 ms bhs-g1-6k.qc.ca [198.27.73.205]
11 268 ms 269 ms 267 ms 198.27.73.231
12 320 ms 272 ms 267 ms mwomercs.com [192.99.109.192]

Trace complete.

[ice trey]

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

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.

I just noticed the other IP address that should be checked with Tracert and all I have to say is... how can I force this IP to be my default connection?

[l33tworks]

Good news guys, now I'm getting disconnected from the game server when I launch match.

[Ataboy]

11/24/2014 7:40PM 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 181 ms 121 ms 71 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 35 ms 47 ms 60 ms 216.254.131.185
4 329 ms 46 ms 402 ms gw-nyiix.bb1.eastyork.primus.ca [198.32.160.89]
5 * 42 ms 30 ms nyiix.nyc.ny.us [198.32.160.77]
6 * * * Request timed out.
7 41 ms 39 ms 46 ms bhs-g2-6k.qc.ca [198.27.73.207]
8 42 ms 40 ms 46 ms 198.27.73.233
9 38 ms 38 ms 40 ms 192.99.109.129
Trace complete.


11/24/2014 8:40PM 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 775 ms 71 ms 20 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 19 ms 18 ms 17 ms 216.254.131.129
4 16 ms 16 ms 18 ms gw-nyiix.bb1.eastyork.primus.ca [198.32.160.89]
5 * * 2705 ms nyiix.nyc.ny.us [198.32.160.77]
6 191 ms * * nwk-2-6k.nj.us [178.32.135.59]
7 350 ms * * bhs-g2-6k.qc.ca [198.27.73.207]
8 92 ms 79 ms 43 ms 198.27.73.233
9 73 ms 253 ms 127 ms 192.99.109.129
Trace complete.

11/24/2014 8:50PM 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 * * * Request timed out.
3 34 ms 32 ms 28 ms 216.254.131.129
4 22 ms 10 ms 11 ms gw-nyiix.bb1.eastyork.primus.ca [198.32.160.89]
5 1716 ms 488 ms * nyiix.nyc.ny.us [198.32.160.77]
6 * * * Request timed out.
7 369 ms 173 ms 122 ms bhs-g2-6k.qc.ca [198.27.73.207]
8 * * 1046 ms 198.27.73.233
9 * 1262 ms 304 ms 192.99.109.129
Trace complete.


11/24/2014 9:20PM 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 253 ms 1186 ms 587 ms host-207-112-105-85.static.dsl.primus.ca [207.112.105.85]
3 14 ms 14 ms 13 ms 216.254.131.129
4 8 ms 7 ms 7 ms gw-nyiix.bb1.eastyork.primus.ca [198.32.160.89]
5 140 ms 2848 ms 501 ms nyiix.nyc.ny.us [198.32.160.77]
6 * * * Request timed out.
7 * * 105 ms bhs-g2-6k.qc.ca [198.27.73.207]
8 335 ms 1125 ms 1457 ms 198.27.73.233
9 * 744 ms 443 ms 192.99.109.129
Trace complete.

11/24/2014 9:25PM eastern
Pinging 192.99.109.129 with 32 bytes of data:
Reply from 192.99.109.129: bytes=32 time=44ms TTL=57
Reply from 192.99.109.129: bytes=32 time=54ms TTL=57
Reply from 192.99.109.129: bytes=32 time=123ms TTL=57
Reply from 192.99.109.129: bytes=32 time=67ms TTL=57
Reply from 192.99.109.129: bytes=32 time=39ms TTL=57
Reply from 192.99.109.129: bytes=32 time=3083ms TTL=57
Reply from 192.99.109.129: bytes=32 time=82ms TTL=57
Request timed out.
Reply from 192.99.109.129: bytes=32 time=1763ms TTL=57
Reply from 192.99.109.129: bytes=32 time=216ms TTL=57
Reply from 192.99.109.129: bytes=32 time=340ms TTL=57
Reply from 192.99.109.129: bytes=32 time=57ms TTL=57
Reply from 192.99.109.129: bytes=32 time=927ms TTL=57
Reply from 192.99.109.129: bytes=32 time=286ms TTL=57
Reply from 192.99.109.129: bytes=32 time=717ms TTL=57
Reply from 192.99.109.129: bytes=32 time=2174ms TTL=57
Reply from 192.99.109.129: bytes=32 time=444ms TTL=57
Reply from 192.99.109.129: bytes=32 time=1320ms TTL=57
Reply from 192.99.109.129: bytes=32 time=854ms TTL=57
Reply from 192.99.109.129: bytes=32 time=267ms TTL=57
Reply from 192.99.109.129: bytes=32 time=35ms TTL=57
Reply from 192.99.109.129: bytes=32 time=302ms TTL=57
Request timed out.
Request timed out.
Reply from 192.99.109.129: bytes=32 time=287ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.99.109.129: bytes=32 time=750ms TTL=57
Reply from 192.99.109.129: bytes=32 time=111ms TTL=57
Reply from 192.99.109.129: bytes=32 time=35ms TTL=57
Reply from 192.99.109.129: bytes=32 time=35ms TTL=57
Reply from 192.99.109.129: bytes=32 time=102ms TTL=57
Reply from 192.99.109.129: bytes=32 time=36ms TTL=57
Reply from 192.99.109.129: bytes=32 time=246ms TTL=57
Reply from 192.99.109.129: bytes=32 time=59ms TTL=57
Reply from 192.99.109.129: bytes=32 time=454ms TTL=57
Reply from 192.99.109.129: bytes=32 time=2134ms TTL=57
Reply from 192.99.109.129: bytes=32 time=1160ms TTL=57
Reply from 192.99.109.129: bytes=32 time=122ms TTL=57
Reply from 192.99.109.129: bytes=32 time=2006ms TTL=57
Reply from 192.99.109.129: bytes=32 time=1130ms TTL=57
Reply from 192.99.109.129: bytes=32 time=444ms TTL=57
Reply from 192.99.109.129: bytes=32 time=3174ms TTL=57
Reply from 192.99.109.129: bytes=32 time=214ms TTL=57
Reply from 192.99.109.129: bytes=32 time=1081ms TTL=57
Reply from 192.99.109.129: bytes=32 time=54ms TTL=57
Reply from 192.99.109.129: bytes=32 time=2196ms TTL=57
Reply from 192.99.109.129: bytes=32 time=386ms TTL=57

Ping statistics for 192.99.109.129:
Packets: Sent = 50, Received = 43, Lost = 7 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 3174ms, Average = 683ms

[Sgt Minuteman]

I used to get pings 30-40 in game now I am 125-780. Almost unplayable. Client also crashes and I have to rejoin the match. Disappointed as I was not able to really competetive in the win a Victor tournament and was able to only get 6 points after ~7 hours of playing. Did get the Premium Time though! I live in San Antonio, Texas.

[Skynet2000]

My ping got considerably worst after the Data Center move. Was 260ish before the move to 300 afterwards.

Now my ping jumps from 300 to over 400 sometimes. Has it got anything to do with people in North America waking up and congesting the server? Don't know why my lag is so bad now.

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

C:\Users\Mechwarrior Only.Tony-PC>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 16 ms 16 ms 16 ms pcd-lkt10-1-rx.netvigator.com [219.78.220.254]
3 * * * Request timed out.
4 16 ms 16 ms 16 ms wtsc3a014.netvigator.com [218.102.40.14]
5 17 ms 17 ms 16 ms tenge1-1.br01.hkg05.pccwbtn.net [63.218.255.9]
6 57 ms 59 ms 59 ms 63-218-144-253.static.pccwglobal.net [63.218.144
.253]
7 57 ms 56 ms 56 ms TenGE0-4-0-2.cr03.sin02.pccwbtn.net [63.218.228.
13]
8 349 ms * 352 ms xe-2-2-3.miami15.mia.seabone.net [195.22.199.65]

9 * 351 ms * xe-2-2-3.miami15.mia.seabone.net [195.22.199.65]

10 359 ms * 360 ms mia-1-6k.fl.us [178.32.135.208]
11 359 ms * 360 ms 198.27.73.197
12 370 ms 368 ms 369 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 370 ms 369 ms 368 ms 198.27.73.231
14 368 ms 368 ms 369 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\Mechwarrior Only.Tony-PC>

Edited by Skynet2000, 25 November 2014 - 11:42 AM.

[The Iron Chancellor]

My Ping is usually acceptable (120-170), but every now and again it spikes and when it does, mechs just gel/morph through each other. The tracert results at the time of occurence (will do more if need be)

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

1 1 ms <1 ms 1 ms 10.100.102.1
2 8 ms 8 ms 8 ms 93-172-0-1.bb.netvision.net.il [93.172.0.1]
3 8 ms 9 ms 8 ms coresw2-hfa-rb2-lns2.bb.netvision.net.il [212.14
3.62.250]
4 9 ms 9 ms 10 ms gw2-0-3-0-2-core2.hfa.nv.net.il [212.143.7.103]

5 63 ms 63 ms 63 ms gw2-fra-0-7-0-0-gw2.hfa.nv.net.il [212.143.12.54
]
6 64 ms 64 ms 63 ms 10.10.70.1
7 * * * Request timed out.
8 76 ms 77 ms 75 ms th2-g1-a9.fr.eu [213.186.32.202]
9 80 ms 80 ms 81 ms rbx-g1-a9.fr.eu [91.121.215.133]
10 82 ms 82 ms 82 ms 37.187.36.131
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 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[Mason2501]

Not to bad for me:


C:\Users\Administrator>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 10.10.10.1
2 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
3 24 ms 25 ms 27 ms 75-32-12-1.lightspeed.dllstx.sbcglobal.net [75.3
2.12.1]
4 28 ms 27 ms 25 ms 71.155.28.53
5 25 ms 23 ms 23 ms 70.143.193.130
6 23 ms 23 ms 23 ms 12.83.80.185
7 26 ms 26 ms 27 ms gar26.dlstx.ip.att.net [12.123.16.85]
8 * * * Request timed out.
9 66 ms * 68 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
10 67 ms 67 ms * ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 * * * Request timed out.
12 89 ms 90 ms 88 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 89 ms 88 ms 89 ms 198.27.73.231
14 87 ms 87 ms 87 ms mwomercs.com [192.99.109.192]

Trace complete.

[Syrkres]

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 [xxxxx]
2 7 ms 6 ms 7 ms xxxxx.verizon-gni.net [xxxxx]
3 10 ms 12 ms 9 ms G0-6-0-6.BSTNMA-LCR-21.verizon-gni.net [130.81.217.48]
4 15 ms 26 ms 114 ms ae1-0.BOS-BB-RTR1.verizon-gni.net [130.81.151.60]
5 20 ms 18 ms 17 ms 0.ae11.XL3.NYC1.ALTER.NET [152.63.20.69]
6 * * * Request timed out.
7 16 ms 13 ms 14 ms 3.ae1.XT1.NYC4.ALTER.NET [140.222.228.121]
8 27 ms 24 ms 17 ms TenGigE0-4-0-1.GW5.NYC4.ALTER.NET [152.63.30.86]
9 16 ms 14 ms 14 ms teliasonera-gw.customer.alter.net [152.179.163.178]
10 17 ms 17 ms 16 ms nyk-bb1-link.telia.net [213.155.135.18]
11 16 ms 17 ms 14 ms nyk-b2-link.telia.net [213.155.130.28]
12 * * * Request timed out.
13 46 ms 47 ms 49 ms bhs-g1-6k.qc.ca [198.27.73.205]
14 53 ms 52 ms 52 ms 198.27.73.231
15 48 ms 51 ms 52 ms mwomercs.com [192.99.109.192]

Trace complete.

Edited by Syrkres, 25 November 2014 - 06:51 PM.

[phatbhuda]

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 6 ms 6 ms 5 ms L100.NYCMNY-VFTTP-84.verizon-gni.net [98.113.8.1
]
3 7 ms 6 ms 7 ms G1-15-0-5.NYCMNY-LCR-21.verizon-gni.net [130.81.
223.32]
4 8 ms 8 ms 7 ms ae5-0.NY325-BB-RTR2.verizon-gni.net [130.81.163.
216]
5 17 ms 94 ms 8 ms 0.so-4-0-0.XT2.NYC4.ALTER.NET [152.63.9.249]
6 13 ms 9 ms 12 ms TenGigE0-7-0-2.GW5.NYC4.ALTER.NET [152.63.18.186
]
7 6 ms 7 ms 8 ms teliasonera-gw.customer.alter.net [152.179.163.1
78]
8 10 ms 9 ms 9 ms nyk-bb2-link.telia.net [213.155.131.138]
9 11 ms 10 ms 11 ms nyk-b2-link.telia.net [213.155.130.30]
10 * * * Request timed out.
11 39 ms 36 ms 36 ms bhs-g1-6k.qc.ca [198.27.73.205]
12 36 ms 36 ms 36 ms 198.27.73.231
13 40 ms 41 ms 40 ms mwomercs.com [192.99.109.192]

Trace complete.

[MongerMan]

Im in Tucson Az
And its looking pretty bad from here.


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

C:\Users\rig>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 * * * Request timed out.
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 79 ms 79 ms 79 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\rig>

[JSmith7784]

I'm in Buffalo NY and horrible here.

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.dlink.com [192.168.0.1]
2 9 ms 13 ms 9 ms cpe-98-0-4-245.buffalo.res.rr.com [98.0.4.245]
3 11 ms 9 ms 12 ms ae9-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.34]
4 29 ms 27 ms 31 ms bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0
.3.3]
5 30 ms 27 ms 32 ms be25.cr0.chi10.tbone.rr.com [107.14.19.28]
6 29 ms 31 ms 27 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
7 29 ms 26 ms 28 ms chi-b21-link.telia.net [213.248.76.97]
8 39 ms 38 ms 36 ms nyk-bb1-link.telia.net [80.91.246.163]
9 39 ms 66 ms 40 ms nyk-b2-link.telia.net [213.155.130.28]
10 * * 80 ms nwk-1-6k.nj.us [178.32.135.212]
11 50 ms 52 ms 50 ms bhs-g1-6k.qc.ca [198.27.73.205]
12 52 ms 50 ms 52 ms 198.27.73.231
13 50 ms 52 ms 50 ms mwomercs.com [192.99.109.192]
Trace complete.


Speedtest.net is showing my ping to Syracuse NY as 18ms with 34 down and 5 up over cable. So I know my connection isn't the problem here.

Edited by JSmith7784, 25 November 2014 - 07:07 PM.

[phatbhuda]

Looks like there's some sort of outage between American Internet providers and the first Canada jump.

[Jeffries]

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 5 ms 6 ms 7 ms L100.ALBYNY-VFTTP-07.verizon-gni.net [96.236.37.1]
3 10 ms 6 ms 8 ms G0-0-3-1.ALBYNY-LCR-22.verizon-gni.net [100.41.199.89]
4 22 ms 23 ms 21 ms 130.81.162.136
5 43 ms 81 ms 21 ms 0.so-6-0-0.XT2.NYC4.ALTER.NET [152.63.17.97]
6 25 ms 21 ms 24 ms TenGigE0-7-0-6.GW5.NYC4.ALTER.NET [152.63.22.118]
7 19 ms 16 ms 16 ms teliasonera-gw.customer.alter.net [152.179.163.178]
8 17 ms 16 ms 17 ms nyk-bb1-link.telia.net [213.155.131.136]
9 37 ms 16 ms 16 ms nyk-b2-link.telia.net [213.155.130.28]
10 * * * Request timed out.
11 44 ms 41 ms 48 ms bhs-g1-6k.qc.ca [198.27.73.205]
12 59 ms 47 ms 44 ms 198.27.73.231
13 41 ms 41 ms 41 ms mwomercs.com [192.99.109.192]

Trace complete.

[aniviron]

I generally ping 80-100, ping shot up to ~350. Ran a few traces:

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

1 3 ms 6 ms 2 ms 192.168.0.1
2 27 ms 26 ms 30 ms cpe-70-117-96-1.austin.res.rr.com [70.117.96.1]

3 30 ms 19 ms 22 ms tge7-7.ausgtxlg01h.texas.rr.com [66.68.4.57]
4 26 ms 19 ms 35 ms be1.ausgtxlg03h.texas.rr.com [24.175.41.62]
5 35 ms 18 ms 21 ms be22.ausutxla01r.texas.rr.com [24.175.43.211]
6 26 ms 25 ms 26 ms agg22.dllatxl301r.texas.rr.com [24.175.41.46]
7 21 ms 18 ms 26 ms 107.14.17.136
8 19 ms 16 ms 31 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
9 24 ms 33 ms 24 ms dls-bb1-link.telia.net [213.248.93.189]
10 66 ms 72 ms 75 ms nyk-bb1-link.telia.net [213.155.137.50]
11 97 ms 75 ms 73 ms nyk-b2-link.telia.net [213.155.130.28]
12 * * * Request timed out.
13 127 ms 126 ms 130 ms bhs-g1-6k.qc.ca [198.27.73.205]
14 130 ms 132 ms 126 ms 198.27.73.231
15 125 ms 124 ms 151 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 4 ms 11 ms 1 ms 192.168.0.1
2 * 23 ms 23 ms cpe-70-117-96-1.austin.res.rr.com [70.117.96.1]

3 16 ms 27 ms 9 ms tge7-7.ausgtxlg01h.texas.rr.com [66.68.4.57]
4 27 ms 32 ms 24 ms be1.ausgtxlg03h.texas.rr.com [24.175.41.62]
5 24 ms 20 ms 18 ms be22.ausutxla01r.texas.rr.com [24.175.43.211]
6 28 ms 22 ms 25 ms agg22.dllatxl301r.texas.rr.com [24.175.41.46]
7 36 ms 28 ms 34 ms 107.14.17.136
8 24 ms 18 ms 20 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
9 25 ms 24 ms 35 ms dls-bb1-link.telia.net [213.248.93.189]
10 75 ms 118 ms 70 ms nyk-bb1-link.telia.net [213.155.137.50]
11 69 ms 71 ms 75 ms nyk-b2-link.telia.net [213.155.130.28]
12 * * 120 ms nwk-1-6k.nj.us [178.32.135.212]
13 149 ms 129 ms 126 ms bhs-g1-6k.qc.ca [198.27.73.205]
14 127 ms * 126 ms 198.27.73.231
15 129 ms 128 ms 125 ms mwomercs.com [192.99.109.192]

Trace complete.


In every trace except the second I pasted, the results are like the first, where the Newark server at [178.32.135.212] either times out or is responsible for a large spike in latency every time.

[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.