70 replies to this topic

[FREDtheDEAD]

Some more stats for ya. From Australia. The San Jose router is droping packets! What is relay-1.mwtactics.com and why does it accept 1 in 3 packets?


Target Name: N/A
IP: 70.42.29.74
Date/Time: 30/06/2013 1:51:56 AM to 30/06/2013 1:53:49 AM

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 77 0 0.0 0 12 1 home.gateway [192.168.0.254]
2 77 0 0.0 23 44 24 {snip}
3 77 0 0.0 23 76 26 202-7-162-138.tpgi.com.au [202.7.162.138]
4 77 0 0.0 23 78 25 adl-sot-way-crt2-ge-4-0-0.tpgi.com.au [203.29.135.29]
5 77 0 0.0 43 176 46 syd-sot-way-crt4-te-11-4-2028.tpgi.com.au [220.244.137.93]
6 77 0 0.0 43 63 45 203-26-22-030.static.tpgi.com.au [203.26.22.30]
7 77 18 23.4 245 261 250 Vlan541.icore1.SQN-SanJose.as6453.net [209.58.116.93]
8 77 0 0.0 245 340 249 if-3-2146.tcore2.SQN-SanJose.as6453.net [209.58.116.138]
9 77 0 0.0 306 399 314 if-5-2.tcore2.PDI-PaloAlto.as6453.net [64.86.21.2]
10 77 0 0.0 310 365 315 if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
11 77 0 0.0 297 344 302 if-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.2]
12 77 0 0.0 306 315 307 if-1-1-0.core4.TNK-Toronto.as6453.net [63.243.172.41]
13 77 0 0.0 310 480 318 ix-4-0-3.core4.TNK-Toronto.as6453.net [216.6.49.2]
14 77 0 0.0 310 364 314 border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
15 62 61 98.4 311 311 311 relay-1.mwtactics.com [70.42.29.65]

Edited by Xajorkith, 29 June 2013 - 08:27 AM.

[Paikanx]

Some stats from France (ISP: Free). You can clearly see which node is failing.

Unfortunately quite sure PGI can't do anything about that :-/ .

tracert 70.42.29.65

Détermination de l'itinéraire vers relay-1.mwtactics.com [70.42.29.65]
avec un maximum de 30 sauts :

1 <1 ms <1 ms <1 ms FREEBOX [192.168.1.1]
2 24 ms 23 ms 22 ms X.X.X.X
3 * 23 ms 23 ms stmaurice-6k-1-a5.routers.proxad.net [213.228.14.254]
4 68 ms 61 ms 73 ms th2-crs16-1-be1008.intf.routers.proxad.net [212.27.50.29]
5 24 ms 28 ms 27 ms p11-crs16-1-be1004.intf.routers.proxad.net [78.254.249.129]
6 24 ms 24 ms 28 ms th2-9k-1-be1001.intf.routers.proxad.net [78.254.249.6]
7 49 ms 57 ms 72 ms ix-15-547.tcore1.PVU-Paris.as6453.net [195.219.241.173]
8 * 152 ms 155 ms if-2-2.tcore1.PYE-Paris.as6453.net [80.231.154.18]
9 154 ms 153 ms 152 ms if-5-2.tcore1.L78-London.as6453.net [80.231.130.1]
10 153 ms 153 ms 176 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
11 172 ms 156 ms 156 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
12 150 ms 147 ms 149 ms if-12-6.tcore1.CT8-Chicago.as6453.net [216.6.99.46]
13 155 ms * 156 ms if-1-1-0.core4.TNK-Toronto.as6453.net [63.243.172.41]
14 405 ms 402 ms 405 ms ix-4-0-3.core4.TNK-Toronto.as6453.net [216.6.49.2]
15 406 ms 408 ms 408 ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.132]
16 402 ms 400 ms 406 ms relay-1.mwtactics.com [70.42.29.65]

[Sarsaparilla Kid]

I've been seeing the same two routers in Toronto acting up from my direction here in California, as does the OP. For me, it means I last about a minute after launching before I get DC'd completely from the game to mechlab and I can't get back into that particular match. Using pingplotter.com, I've seen an occasional 10% packet loss from those two nodes. I filed a ticket on it, and the tech handling it basically said the packet loss in my connection is causing my crashes, and the best I can do is see if my ISP can re-route my signal path. Of course, my ISP doesn't have that kind of control, so no dice there. The one thing that has kept me connected is using CyberGhost, which gives me a VPN address, usually out of New York, and that seems to work well enough to bypass those two jittery routers in Toronto, though it does bump my ping up to usually 200-300ms. Generally playable, but not ideal.

[aniviron]

http://mwomercs.com/...-getting-worse/

Immediately after this problem:

Tracing route to relay-1.mwtactic.com [208.73.211.175]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 6 ms 7 ms 10.239.66.1
3 17 ms 7 ms 12 ms tge7-2.ausgtxlg01h.texas.rr.com [66.68.5.92]
4 7 ms 22 ms 7 ms tge8-1.ausgtxlg02h.texas.rr.com [66.68.5.77]
5 14 ms 15 ms 8 ms te-0-8-0-3.austtxrdcsc-cr02.texas.rr.com [24.27.12.196]
6 15 ms 15 ms 16 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
7 18 ms 15 ms 15 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
8 23 ms 23 ms 23 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
9 * 17 ms 17 ms ae1.pr1.dfw10.tbone.rr.com [107.14.17.234]
10 63 ms 61 ms 56 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
11 59 ms 59 ms 59 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
12 64 ms 62 ms 66 ms te0-0-0-3.mpd22.iah01.atlas.cogentco.com [154.54.0.201]
13 56 ms 57 ms 57 ms te0-3-0-6.mpd22.lax01.atlas.cogentco.com [154.54.0.253]
14 58 ms 57 ms 59 ms te7-1.mag02.lax01.atlas.cogentco.com [154.54.47.166]
15 57 ms 56 ms 63 ms 38.104.77.122
16 56 ms 57 ms 57 ms border1.te4-1-bbnet2.lax015.pnap.net [216.52.255.120]
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.

Edited by aniviron, 29 June 2013 - 02:50 PM.

[DragonsFire]

Xajorkith, on 29 June 2013 - 07:51 AM, said:

Some more stats for ya. From Australia. The San Jose router is droping packets! What is relay-1.mwtactics.com and why does it accept 1 in 3 packets?
<snip>

I am not positive on this as I do not have direct access but your last hop that you asked about is either a router owned by PGI or port(s) on a router at the hosting solution where the servers appear to be located. The packet loss is not necessarily indicative of an issue outright either. While I realize that one is indeed happening, and there does appear to be some latency jitter, routers can be set to bump ICMP responses very far down their priority list in terms of handling causing latency increase or outright loss.

Again, that's not to say that this isn't a problem, because it certainly does seem that an issue is happening at the Internap edge router. However, without direct access the best that we can do is continue to provide feedback that will arm PGI with the information they need to get their host to resolve the issues.

Edited by DragonsFire, 29 June 2013 - 03:00 PM.

[FREDtheDEAD]

It does look like ix-4-0-3.core4.TNK-Toronto.as6453.net [216.6.49.2] has a large ICMP latency. Also Vlan541.icore1.SQN-SanJose.as6453.net seems to be dropping packets. You can email Tata Communications, owners of these routers, at trouble@as6453.net - their web site is http://www.tatacommunications.com/


MWO players: fixing the internet one router at a time... (pfft!)

Edited by Xajorkith, 29 June 2013 - 06:05 PM.

[Sarsaparilla Kid]

Here are some typical pingplotter results I've been getting:

[Wildstreak]

Well for what they are worth, I did a Traceroute over 3 days, Friday, Saturday and Sunday. Also did Pingplotter Saturday and Sunday.

Traceroute from 6-28, Friday.

Spoiler

Traceroute from 6-29, Saturday.

Spoiler

Pingplotter from 6-29, Saturday.

Spoiler

Traceroute from 6-30, Sunday.

Spoiler

Pingplotter from 6-30, Sunday.

Spoiler

[Sarsaparilla Kid]

That might explain why CyberGhost setting up a VPN in New York hasn't been working well for me the last few days...something fishy going on in the NY area now. I tell ya, seems like the whole interwebs is hanging on by the barest of threads...

[Arcturious]

This is why I'm hoping a local Canadian can run some tests from their home.

PGI obviously can't do anything about the Internet other than perhaps 2-3 hops out - their servers, host, ISP. Once it gets outside there it is impossible for them to effect.

A Canadian will eliminate most of the net and be only a few hops out. If they see similar fluctuations in the last few hops we might be on to something, until then though its mostly circumstantial.

[SmokinDave73]

I have a canadian member in my unit next time he comes on TS I will ask him to do a traceroute, just have to wait for him to come back from his fly in fly out work.