Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Paladin3 on October 21, 2012, 05:08:38 PM
-
I was on a week ago when Skuzzy was talking about how they had changed something with their internet connection. I just wanted to say I am glad that we are working on new things, but ever since I have seen allot more warping throughout the arenas, as have a couple of my squaddies. I am not a fan since it has made it less smooth for me. Anyone else have any thoughts? Noticed anything different?
I looked for a thread on this topic and came up dry.
-
A lot more mini-warps since the change over.
-
I've noticed that too.
-C+
-
You guys should run ping plotter and post the runs for Skuzzy to look at. I know my run went from 16 hops to the old server to 10 with the new. My pings look about the same and I haven't noticed anything different in the game. The more info Skuzzy has the better the decision he can make when it comes time to decide which server to use.
-
You guys should run ping plotter and post the runs for Skuzzy to look at. I know my run went from 16 hops to the old server to 10 with the new. My pings look about the same and I haven't noticed anything different in the game. The more info Skuzzy has the better the decision he can make when it comes time to decide which server to use.
I notice a lot more enemies warping since the change also. Like 1 in 8 will warp.. It is noticeably worse.
-
Yes I notice it
-
I was on a week ago when Skuzzy was talking about how they had changed something with their internet connection. I just wanted to say I am glad that we are working on new things, but ever since I have seen allot more warping throughout the arenas, as have a couple of my squaddies. I am not a fan since it has made it less smooth for me. Anyone else have any thoughts? Noticed anything different?
I looked for a thread on this topic and came up dry.
:rofl :rofl P-P-P-P-P-Paladin, I heard you always come up d-d-d-d-dry! :rofl :rofl
and long live Richard Boone, Have Gun, Will Travel!
-
This topic is discussed in Technical Support under the subject of Connection woes.
-
Before I entered the arena friggin 180 pings when it was usually only 50.... :huh
-
Yes, lots more mini warps. :(
check through ping plotter if the causes is this ho; 207.88.14.34.ptr.us.xo.net
This hop I believe may be the very cause of any connection woes. The ping through it is unstable to say the least
-
I cannot do anything with the above comments. They do not provide anything really useful.
We know there have been ongoing problems with Comcast. Nothing we can do about that. We also know the new ISP location has had a poor route for the British players, but they have been working on it and for most it should better better now, or the same as before (they are using the same route as the old ISP).
The new ISP has direct connections with 11 Tier 1 backbone providers. Our current ISP has one connection.
Every analysis I have run to anyone in the U.S. shows the same levels of performance between both ISP's. They also show the same problems, as they are pretty much using the same routes.
However, the Internet is a dynamic beast. What is true today, may not be true tomorrow. Without data, there is little I can do. It is within your power to check your own connection. You do not have to listen to me or anyone else. Grab Ping Plotter, and run it to the following IP addresses (the longer the run, the better):
New: 66.151.248.2
Old: 206.16.60.38
I need both to be able to compare. I will then run a test to your location and see what it looks like as well.
This way we get real data which can help far more than general comments will ever do.
Thank you.
-
Ok, sure I can do that... However I was going off of stability before, and that you ran it that first weekend and said I was a little worse. I was just asking the community at large if others had noticed the same thing or if it was just me, not screaming fix it. Although yeah, if it wasn't broke for me before and is worse now, sure that is irritating. How long should I run it and how do I post it? I found a file, save image command and saved that.
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 22-Oct-12 18:55:29 to 22-Oct-12 18:57:29
1 6 ms 7 ms 7 ms 12 ms 8 ms 7 ms 7 ms 8 ms 7 ms [96.70.159.1]
2 8 ms 8 ms 7 ms 7 ms 8 ms 7 ms 8 ms 7 ms 7 ms te-9-3-ur02.sharpsridge.tn.knox.comcast.net [69.139.205.205]
3 7 ms 8 ms 7 ms 8 ms 8 ms 8 ms 8 ms 7 ms 8 ms te-6-3-ar01.bluelight.tn.knox.comcast.net [68.85.171.205]
4 13 ms 15 ms 15 ms 15 ms 19 ms 15 ms 15 ms 14 ms 16 ms xe-0-0-2-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.137]
5 25 ms 25 ms 23 ms 26 ms 26 ms 27 ms 23 ms 25 ms 24 ms pos-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101]
6 22 ms 25 ms 26 ms 23 ms 25 ms 22 ms 23 ms 23 ms 27 ms pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.86]
7 23 ms 23 ms 23 ms 23 ms 23 ms 22 ms 23 ms 23 ms 23 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
8 46 ms 44 ms 45 ms 44 ms 46 ms 46 ms 46 ms 44 ms 44 ms cr1.attga.ip.att.net [12.122.141.182]
9 43 ms 42 ms 43 ms 42 ms 43 ms 41 ms 43 ms 47 ms 45 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 41 ms 41 ms 43 ms 42 ms 43 ms 47 ms 41 ms 41 ms 58 ms ggr1.dlstx.ip.att.net [12.122.138.1]
11 42 ms 44 ms 42 ms N/A N/A 43 ms 42 ms N/A 42 ms [12.122.251.70]
12 43 ms 44 ms 42 ms 42 ms * 43 ms 42 ms 42 ms 43 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
13 42 ms 42 ms 42 ms 41 ms 40 ms 41 ms 43 ms 41 ms 42 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 9, Received = 9, Lost = 0 (0.0%)
Round Trip Times: Minimum = 40ms, Maximum = 43ms, Average = 41ms
Target Name: N/A
IP: 66.151.248.2
Date/Time: 22-Oct-12 18:58:07 to 22-Oct-12 19:00:22
1 8 ms 18 ms 7 ms 6 ms 8 ms 6 ms 6 ms 7 ms 6 ms 8 ms [96.70.159.1]
2 7 ms 8 ms 8 ms 7 ms 7 ms 6 ms 7 ms 12 ms 7 ms 9 ms te-9-3-ur01.sharpsridge.tn.knox.comcast.net [69.139.205.201]
3 7 ms 8 ms 9 ms 7 ms 7 ms 6 ms 7 ms 7 ms 7 ms 8 ms te-8-3-ur02.sharpsridge.tn.knox.comcast.net [68.86.136.77]
4 7 ms 8 ms 7 ms 8 ms 12 ms 7 ms 7 ms 7 ms 7 ms 8 ms te-6-3-ar01.bluelight.tn.knox.comcast.net [68.85.171.205]
5 17 ms 18 ms 15 ms 20 ms 14 ms 14 ms 14 ms 17 ms 14 ms 18 ms xe-0-0-1-0-ar01.goodslettvll.tn.nash.comcast.net [68.85.171.190]
6 26 ms 24 ms 24 ms 21 ms 26 ms 23 ms 22 ms 24 ms 25 ms 27 ms pos-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189]
7 23 ms 27 ms 23 ms 24 ms 24 ms 22 ms 37 ms 27 ms 26 ms 26 ms pos-0-2-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.166]
8 22 ms 22 ms 23 ms 22 ms 22 ms 22 ms * 22 ms 21 ms 27 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
9 45 ms 45 ms 43 ms 43 ms 42 ms 42 ms 45 ms 45 ms 44 ms 46 ms cr1.attga.ip.att.net [12.122.141.182]
10 42 ms 48 ms 45 ms 44 ms 49 ms 47 ms 45 ms 43 ms 44 ms 44 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 40 ms 41 ms 41 ms 40 ms 58 ms * 40 ms 41 ms 40 ms 42 ms ggr6.dlstx.ip.att.net [12.122.138.113]
12 41 ms 45 ms 43 ms 45 ms 47 ms 41 ms 41 ms 43 ms 41 ms 44 ms [12.90.228.14]
13 50 ms 52 ms 46 ms 51 ms 46 ms 48 ms 52 ms 54 ms 46 ms 52 ms border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
14 53 ms 56 ms 48 ms 49 ms 46 ms 48 ms 52 ms 56 ms 47 ms 52 ms [66.151.248.2]
Ping statistics for 66.151.248.2
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 46ms, Maximum = 56ms, Average = 50ms
Nevermind, I obviously figured it out :lol
-
New server:
Target Name: N/A
IP: 66.151.248.2
Date/Time: 23.10.2012 02:16:40 to 23.10.2012 02:19:50
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 20 0 0,0 1 3 1 [192.168.1.1]
2 20 0 0,0 8 17 10 esn1ibr2-xdsl.versatel.de [62.214.64.97]
3 20 0 0,0 8 123 24 ge-1-8-v511.esn001isp006.versatel.de [62.214.105.197]
4 20 0 0,0 9 60 15 fra20ip6.versatel.de [62.214.104.174]
5 20 0 0,0 14 220 38 10g-8-4.hhb002isp005.versatel.de [62.214.110.122]
6 20 0 0,0 14 16 14 hmb-s2-rou-1103.DE.eurorings.net [134.222.120.117]
7 20 0 0,0 106 123 109 dssd-s2-rou-1102.DE.eurorings.net [134.222.229.57]
8 20 0 0,0 106 152 109 asd2-rou-1022.NL.eurorings.net [134.222.228.73]
9 20 0 0,0 27 33 28 rt2-rou-1022.NL.eurorings.net [134.222.231.130]
10 20 0 0,0 106 132 110 nyk-s1-rou-1021.US.eurorings.net [134.222.226.174]
11 20 0 0,0 106 138 109 nyk-s1-rou-1001.US.eurorings.net [134.222.231.237]
12 20 0 0,0 99 193 104 [134.222.249.238]
13 20 20 100,0 0 0 0 [-]
14 20 0 0,0 146 148 146 [67.133.189.94]
15 20 7 35,0 146 179 149 border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
16 20 7 35,0 147 160 148 [66.151.248.2]
Old server:
Target Name: N/A
IP: 206.16.60.38
Date/Time: 23.10.2012 02:20:44 to 23.10.2012 02:23:54
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 20 0 0,0 1 2 1 [192.168.1.1]
2 20 0 0,0 8 20 9 esn1ibr2-xdsl.versatel.de [62.214.64.97]
3 20 0 0,0 8 134 16 ge-1-8-v511.esn001isp006.versatel.de [62.214.105.197]
4 20 0 0,0 8 137 23 [62.214.111.25]
5 20 0 0,0 9 194 34 10g-9-1.dus002isp005.versatel.de [62.214.110.233]
6 20 0 0,0 9 83 16 [212.162.17.5]
7 20 0 0,0 9 62 14 vl-3201-ve-128.ebr2.Dusseldorf1.Level3.net [4.69.161.133]
8 20 0 0,0 12 73 15 ae-45-45.ebr1.Amsterdam1.Level3.net [4.69.143.197]
9 20 0 0,0 12 55 14 ae-1-100.ebr2.Amsterdam1.Level3.net [4.69.141.170]
10 20 0 0,0 20 60 22 ae-47-47.ebr2.London1.Level3.net [4.69.143.78]
11 20 0 0,0 88 106 89 ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
12 20 0 0,0 88 105 91 ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
13 20 0 0,0 87 152 93 ae-1-60.edge3.NewYork1.Level3.net [4.69.155.17]
14 20 0 0,0 91 222 98 att-level3.newyork1.level3.net [4.68.63.142]
15 20 0 0,0 134 240 141 cr2.n54ny.ip.att.net [12.122.130.170]
16 20 0 0,0 134 248 141 cr2.wswdc.ip.att.net [12.122.3.38]
17 20 0 0,0 134 187 140 cr1.attga.ip.att.net [12.122.1.173]
18 20 0 0,0 133 205 138 cr2.dlstx.ip.att.net [12.122.28.174]
19 20 0 0,0 132 328 158 ggr1.dlstx.ip.att.net [12.122.138.1]
20 9 0 0,0 133 135 133 [12.122.251.66]
21 20 0 0,0 133 237 141 mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
22 20 0 0,0 132 197 136 [206.16.60.38]
Both plots are rather typical. Many troubles with the new location.
-
Old Server
Target Name: N/A
IP: 206.16.60.41
Date/Time: 10/22/2012 10:07:58 PM to 10/22/2012 10:08:17 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 20 0 0.0 1 37 3 WRT610N [192.168.1.1]
2 20 0 0.0 10 83 21 [10.241.112.1]
3 20 0 0.0 11 86 27 dtr01sbdgma-tge-4-3.sbdg.ma.charter.com [96.34.84.158]
4 20 0 0.0 11 70 23 crr03oxfrma-tge-0-1-0-0.oxfr.ma.charter.com [96.34.80.116]
5 20 0 0.0 12 54 21 bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
6 20 0 0.0 24 110 35 bst-edge-04.inet.qwest.net [72.164.154.201]
7 20 0 0.0 23 106 37 jfk-brdr-04.inet.qwest.net [67.14.5.26]
8 20 0 0.0 24 140 37 [63.146.26.2]
9 20 0 0.0 58 133 74 cr2.n54ny.ip.att.net [12.122.80.238]
10 20 0 0.0 59 166 77 cr2.wswdc.ip.att.net [12.122.3.38]
11 20 0 0.0 57 137 71 cr1.attga.ip.att.net [12.122.1.173]
12 20 0 0.0 58 125 74 cr2.dlstx.ip.att.net [12.122.28.174]
13 20 0 0.0 56 166 76 ggr1.dlstx.ip.att.net [12.122.138.1]
14 10 0 0.0 57 104 69 [12.122.251.66]
15 20 2 10.0 57 124 76 mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
16 20 0 0.0 57 146 86 [206.16.60.41]
New server
Target Name: N/A
IP: 66.151.248.2
Date/Time: 10/22/2012 10:09:16 PM to 10/22/2012 10:09:36 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 20 0 0.0 1 56 17 WRT610N [192.168.1.1]
2 20 0 0.0 10 83 35 [10.241.112.1]
3 20 0 0.0 11 90 30 dtr01sbdgma-tge-4-3.sbdg.ma.charter.com [96.34.84.158]
4 20 0 0.0 11 92 28 crr03oxfrma-tge-0-1-0-0.oxfr.ma.charter.com [96.34.80.116]
5 20 0 0.0 12 94 32 bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
6 20 0 0.0 24 104 44 bst-edge-04.inet.qwest.net [72.164.154.201]
7 20 0 0.0 57 206 86 dax-edge-03.inet.qwest.net [67.14.2.166]
8 20 1 5.0 58 177 76 [67.133.189.94]
9 20 0 0.0 58 218 73 border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
10 20 0 0.0 59 229 76 [66.151.248.2]
I don't normally see issue with the old server and haven't seen anything with the new either.
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 10/22/2012 10:28:01 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 8 ms 9 ms 10 ms 7 ms 9 ms [10.166.32.1]
3 8 ms 8 ms 8 ms 9 ms 7 ms acr01mtvril-gbe-3-40.mtvr.il.charter.com [96.34.56.88]
4 10 ms 16 ms 11 ms 12 ms 10 ms dtr01blvlil-tge-0-5-0-4.blvl.il.charter.com [96.34.49.22]
5 14 ms 12 ms 17 ms 20 ms 15 ms bbr01blvlil-tge-0-2-0-1.blvl.il.charter.com [96.34.1.114]
6 12 ms 10 ms 11 ms 10 ms 11 ms [216.55.35.77]
7 26 ms 23 ms 20 ms 27 ms 23 ms vb1720.rar3.chicago-il.us.xo.net [216.156.0.177]
8 41 ms 17 ms 43 ms * 41 ms 207.88.14.194.ptr.us.xo.net [207.88.14.194]
9 * 16 ms * 18 ms * 206.111.2.90.ptr.us.xo.net [206.111.2.90]
10 43 ms 44 ms 42 ms 49 ms 51 ms cr2.cgcil.ip.att.net [12.122.81.98]
11 46 ms 44 ms 47 ms 47 ms 46 ms cr2.sl9mo.ip.att.net [12.122.2.22]
12 48 ms 48 ms 49 ms 55 ms 47 ms cr1.sl9mo.ip.att.net [12.122.2.217]
13 48 ms 51 ms 49 ms 47 ms 44 ms cr2.dlstx.ip.att.net [12.122.3.221]
14 44 ms 44 ms 43 ms 44 ms 42 ms ggr1.dlstx.ip.att.net [12.122.138.1]
15 44 ms 46 ms 44 ms N/A 46 ms [12.122.251.70]
16 51 ms 45 ms 45 ms 45 ms 44 ms mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
17 46 ms 46 ms 45 ms 45 ms 45 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 45ms, Maximum = 46ms, Average = 45ms
Hops 9 and 14 I was getting anywhere from 25 to 40% packet loss
Target Name: N/A
IP: 66.151.248.2
Date/Time: 10/22/2012 10:29:51 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 8 ms 7 ms 8 ms 8 ms 10 ms [10.166.32.1]
3 10 ms 11 ms 9 ms 16 ms 12 ms acr01mtvril-gbe-3-42.mtvr.il.charter.com [96.34.56.22]
4 10 ms 11 ms 10 ms 19 ms 9 ms dtr01blvlil-tge-0-5-0-4.blvl.il.charter.com [96.34.49.22]
5 24 ms 17 ms 17 ms 27 ms 15 ms bbr01blvlil-tge-0-2-0-1.blvl.il.charter.com [96.34.1.114]
6 14 ms 20 ms 13 ms 12 ms 13 ms bbr01olvemo-tge-0-6-0-2.olve.mo.charter.com [96.34.0.110]
7 47 ms 37 ms 37 ms 35 ms 36 ms kcm-edge-13.inet.qwest.net [72.165.193.73]
8 36 ms 34 ms 40 ms 35 ms 36 ms dax-edge-03.inet.qwest.net [67.14.2.174]
9 36 ms 36 ms 36 ms 35 ms 35 ms [67.133.189.94]
10 38 ms 35 ms 45 ms 36 ms 36 ms border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
11 36 ms 36 ms 38 ms 38 ms 39 ms [66.151.248.2]
Ping statistics for 66.151.248.2
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 36ms, Maximum = 39ms, Average = 37ms
-
Well just going say I have never had problem before but I might as well be on dial up. For that reason alone ... maybe time for retirement from the game.
-
old
Target Name: N/A
IP: 206.16.60.38
Date/Time: 23/10/2012 11:17:42
1 0 ms [192.168.1.1]
2 * [-]
3 24 ms host-78-151-225-55.static.as13285.net [78.151.225.55]
4 54 ms host-78-151-225-54.static.as13285.net [78.151.225.54]
5 * [-]
6 31 ms xe-11-2-0-rt001.sov.as13285.net [62.24.240.5]
7 31 ms host-78-144-1-63.as13285.net [78.144.1.63]
8 31 ms ae52.edge5.London1.Level3.net [212.187.138.77]
9 32 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
10 32 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
11 98 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
12 * [-]
13 * [-]
14 26 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
15 15 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
16 13 ms att-level3.newyork1.level3.net [4.68.63.142]
17 57 ms cr2.n54ny.ip.att.net [12.122.130.170]
18 * [-]
19 15 ms cr2.wswdc.ip.att.net [12.122.3.38]
20 17 ms cr1.attga.ip.att.net [12.122.1.173]
21 13 ms cr2.dlstx.ip.att.net [12.122.28.174]
22 9 ms ggr1.dlstx.ip.att.net [12.122.138.1]
23 11 ms [12.122.251.66]
24 13 ms mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
25 139 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 139ms, Maximum = 139ms, Average = 139ms
2nd try
Target Name: N/A
IP: 206.16.60.38
Date/Time: 23/10/2012 11:21:05
1 0 ms 0 ms 0 ms [192.168.1.1]
2 * * * [-]
3 25 ms 25 ms 24 ms host-78-151-225-55.static.as13285.net [78.151.225.55]
4 24 ms 24 ms 25 ms host-78-151-225-54.static.as13285.net [78.151.225.54]
5 30 ms 30 ms 30 ms xe-10-1-0-rt002.bre.as13285.net [62.24.240.19]
6 31 ms 30 ms 31 ms xe-11-2-0-rt001.sov.as13285.net [62.24.240.5]
7 30 ms 30 ms 31 ms host-78-144-1-63.as13285.net [78.144.1.63]
8 31 ms 32 ms 31 ms ae52.edge5.London1.Level3.net [212.187.138.77]
9 32 ms 31 ms 31 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
10 31 ms N/A 32 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
11 99 ms 472 ms 99 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
12 * * * [-]
13 * * * [-]
14 19 ms 18 ms 19 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
15 19 ms 19 ms 19 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
16 19 ms 19 ms 20 ms att-level3.newyork1.level3.net [4.68.63.142]
17 63 ms 64 ms 63 ms cr2.n54ny.ip.att.net [12.122.130.170]
18 * * * [-]
19 21 ms 18 ms 21 ms cr2.wswdc.ip.att.net [12.122.3.38]
20 20 ms 19 ms 27 ms cr1.attga.ip.att.net [12.122.1.173]
21 21 ms 19 ms 23 ms cr2.dlstx.ip.att.net [12.122.28.174]
22 16 ms 17 ms 17 ms ggr1.dlstx.ip.att.net [12.122.138.1]
23 16 ms 18 ms 18 ms [12.122.251.70]
24 N/A 18 ms 17 ms mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
25 N/A N/A N/A []
26 N/A N/A N/A []
27 139 ms * * [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 3, Received = 1, Lost = 2 (66.7%)
Round Trip Times: Minimum = 139ms, Maximum = 139ms, Average = 139ms
new
Target Name: N/A
IP: 66.151.248.2
Date/Time: 23/10/2012 11:19:11
1 0 ms [192.168.1.1]
2 18 ms host-78-150-80-1.as13285.net [78.150.80.1]
3 24 ms host-78-151-225-55.static.as13285.net [78.151.225.55]
4 25 ms host-78-151-225-58.static.as13285.net [78.151.225.58]
5 33 ms xe-10-1-0-rt002.bre.as13285.net [62.24.240.19]
6 30 ms xe-11-2-0-rt001.sov.as13285.net [62.24.240.5]
7 30 ms host-78-144-1-65.as13285.net [78.144.1.65]
8 36 ms [62.157.251.189]
9 73 ms so-3-3-0-bcs1-lnx.savvis.net [206.24.169.5]
10 * [-]
11 15 ms [194.25.6.181]
12 101 ms cr2-pos-B-3.Dallas.savvis.net [204.70.194.74]
13 * [-]
14 * [-]
15 19 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]
16 18 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.145]
17 18 ms [208.175.175.54]
18 18 ms border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
19 141 ms [66.151.248.2]
Ping statistics for 66.151.248.2
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 141ms, Maximum = 141ms, Average = 141ms
2nd try
Target Name: N/A
IP: 66.151.248.2
Date/Time: 23/10/2012 11:22:51
1 0 ms [192.168.1.1]
2 * [-]
3 25 ms host-78-151-225-55.static.as13285.net [78.151.225.55]
4 25 ms host-78-151-225-58.static.as13285.net [78.151.225.58]
5 29 ms xe-10-1-0-rt002.bre.as13285.net [62.24.240.19]
6 31 ms xe-11-2-0-rt001.sov.as13285.net [62.24.240.5]
7 31 ms host-78-144-1-65.as13285.net [78.144.1.65]
8 35 ms [62.157.251.189]
9 30 ms [194.25.6.181]
10 33 ms so-3-3-0-bcs1-lnx.savvis.net [206.24.169.5]
11 142 ms cr2-pos-B-3.Dallas.savvis.net [204.70.194.74]
12 * [-]
13 * [-]
14 * [-]
15 19 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]
16 20 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.145]
17 18 ms [208.175.175.54]
18 18 ms border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
19 141 ms [66.151.248.2]
Ping statistics for 66.151.248.2
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 141ms, Maximum = 141ms, Average = 141ms
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 22-Oct-12 18:55:29 to 22-Oct-12 18:57:29
1 6 ms 7 ms 7 ms 12 ms 8 ms 7 ms 7 ms 8 ms 7 ms [96.70.159.1]
2 8 ms 8 ms 7 ms 7 ms 8 ms 7 ms 8 ms 7 ms 7 ms te-9-3-ur02.sharpsridge.tn.knox.comcast.net [69.139.205.205]
3 7 ms 8 ms 7 ms 8 ms 8 ms 8 ms 8 ms 7 ms 8 ms te-6-3-ar01.bluelight.tn.knox.comcast.net [68.85.171.205]
4 13 ms 15 ms 15 ms 15 ms 19 ms 15 ms 15 ms 14 ms 16 ms xe-0-0-2-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.137]
5 25 ms 25 ms 23 ms 26 ms 26 ms 27 ms 23 ms 25 ms 24 ms pos-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101]
6 22 ms 25 ms 26 ms 23 ms 25 ms 22 ms 23 ms 23 ms 27 ms pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.86]
7 23 ms 23 ms 23 ms 23 ms 23 ms 22 ms 23 ms 23 ms 23 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
8 46 ms 44 ms 45 ms 44 ms 46 ms 46 ms 46 ms 44 ms 44 ms cr1.attga.ip.att.net [12.122.141.182]
9 43 ms 42 ms 43 ms 42 ms 43 ms 41 ms 43 ms 47 ms 45 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 41 ms 41 ms 43 ms 42 ms 43 ms 47 ms 41 ms 41 ms 58 ms ggr1.dlstx.ip.att.net [12.122.138.1]
11 42 ms 44 ms 42 ms N/A N/A 43 ms 42 ms N/A 42 ms [12.122.251.70]
12 43 ms 44 ms 42 ms 42 ms * 43 ms 42 ms 42 ms 43 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
13 42 ms 42 ms 42 ms 41 ms 40 ms 41 ms 43 ms 41 ms 42 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 9, Received = 9, Lost = 0 (0.0%)
Round Trip Times: Minimum = 40ms, Maximum = 43ms, Average = 41ms
Target Name: N/A
IP: 66.151.248.2
Date/Time: 22-Oct-12 18:58:07 to 22-Oct-12 19:00:22
1 8 ms 18 ms 7 ms 6 ms 8 ms 6 ms 6 ms 7 ms 6 ms 8 ms [96.70.159.1]
2 7 ms 8 ms 8 ms 7 ms 7 ms 6 ms 7 ms 12 ms 7 ms 9 ms te-9-3-ur01.sharpsridge.tn.knox.comcast.net [69.139.205.201]
3 7 ms 8 ms 9 ms 7 ms 7 ms 6 ms 7 ms 7 ms 7 ms 8 ms te-8-3-ur02.sharpsridge.tn.knox.comcast.net [68.86.136.77]
4 7 ms 8 ms 7 ms 8 ms 12 ms 7 ms 7 ms 7 ms 7 ms 8 ms te-6-3-ar01.bluelight.tn.knox.comcast.net [68.85.171.205]
5 17 ms 18 ms 15 ms 20 ms 14 ms 14 ms 14 ms 17 ms 14 ms 18 ms xe-0-0-1-0-ar01.goodslettvll.tn.nash.comcast.net [68.85.171.190]
6 26 ms 24 ms 24 ms 21 ms 26 ms 23 ms 22 ms 24 ms 25 ms 27 ms pos-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189]
7 23 ms 27 ms 23 ms 24 ms 24 ms 22 ms 37 ms 27 ms 26 ms 26 ms pos-0-2-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.166]
8 22 ms 22 ms 23 ms 22 ms 22 ms 22 ms * 22 ms 21 ms 27 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
9 45 ms 45 ms 43 ms 43 ms 42 ms 42 ms 45 ms 45 ms 44 ms 46 ms cr1.attga.ip.att.net [12.122.141.182]
10 42 ms 48 ms 45 ms 44 ms 49 ms 47 ms 45 ms 43 ms 44 ms 44 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 40 ms 41 ms 41 ms 40 ms 58 ms * 40 ms 41 ms 40 ms 42 ms ggr6.dlstx.ip.att.net [12.122.138.113]
12 41 ms 45 ms 43 ms 45 ms 47 ms 41 ms 41 ms 43 ms 41 ms 44 ms [12.90.228.14]
13 50 ms 52 ms 46 ms 51 ms 46 ms 48 ms 52 ms 54 ms 46 ms 52 ms border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
14 53 ms 56 ms 48 ms 49 ms 46 ms 48 ms 52 ms 56 ms 47 ms 52 ms [66.151.248.2]
Ping statistics for 66.151.248.2
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 46ms, Maximum = 56ms, Average = 50ms
Nevermind, I obviously figured it out :lol
Notice the routes are virtually identical. The packet loss is occurring in AT&T's network, regardless of the destination. This is what I expect to see for most of North America. The problem is the Internet itself, not the end point.
-
So far where people are complaining about problems with the new ISP, I see the same problems with the old ISP, in North America. In general, the North American Internet is a mess and will probably stay that way until after our election is over, in the U.S.
Europe is another ball of wax. That is where I expect to see a lot of different routes. Some good, some bad.
Lusche, I will point the new ISP network folks at yours. Like I said. they have 11 different backbone connections to route through. Some will be worse, others will be better. They dynamically route based on traffic patterns, but if an ISP is not broadcasting that data correctly, it could cause bad route choices.
-
I've hardly logged any hours since the change but did see that things were worse. I'll get onto those ping plots skuzzy and get some more BT / British routes posted.
-
JimmyC, are you having issues with the new test ISP?
Folks, the test ISP will be looking at this thread, so please post up traces/ping plots to both IP addresses and state what you issue(s) are.
-
only played once in last couple of weeks..
not really sure if there was a problem, I think not but I had had a couple of sherberts.... :cheers:
Saw you wanted British info so offered up mine....
will report back after next time I play
Sorry for any confusion
<S> Jimmy
-
only played once in last couple of weeks..
not really sure if there was a problem, I think not but I had had a couple of sherberts.... :cheers:
Saw you wanted British info so offered up mine....
will report back after next time I play
Sorry for any confusion
<S> Jimmy
No confusion. Your trace to the new location looked better than the one to AT&T. Looks like it is going to be specific ISP in England that are at issue.
-
Old Server
(http://i724.photobucket.com/albums/ww247/Glendinho/206166038100SAMPLES_zps474b3b97.png)
NewServer
(http://i724.photobucket.com/albums/ww247/Glendinho/661512482100SAMPLES_zps5eb594b4.png)
I did these around 20:30 during peak time.
-
Dolby, the new one looks better than the old, but still has packet loss. Anytime you see Level3 in a trace, you will almost always see packet loss.
-
But look at the spikes in the new servers ping trace, it's probably the cause of alot of the mini warps.
EDIT: not to mention the ping average almost 30ms higher on average
-
but look at the spikes in the new servers ping trace, it's probably the cause of alot of the mini warps.
Packet loss is going to be the bigger problem. You have tons of packet loss and the pings from hop to hop are all over the place.
Easy way to test it is to log out of the Late War arena and try the Dueling arena. While the resource loads are less in the Dueling, it might give you an indication of how the old Late would play.
The ping average is irrelevant. It is well under the threshold of you being able to notice it in the game. Did you look at hop 21 in the AT&T trace? 203ms with an average of 187ms.
No need to create any monsters. Just grab a squaddie and go to the Dueling arena and see what it is like.
-
I duelled Pand a few days ago in the DA and had no problems, no mini warps what so ever through 6 duels. I have the AHFilm files if you need them.
The reason I have brought it to your attention is that I am noticing more warps with the new ISP.
While the new server has created less rubber bullets for me, it has made it more difficult with the mini warping. (Especially in high con density areas)
I will certainly grab someone in the upcoming hours to the DA as per your test instructions, I will also offer up the films should you need them to compare to the Pand fights.
:salute
-
old - rock solid, very rarely saw warps:
(http://i975.photobucket.com/albums/ae235/RTHolmes/AH%20stuff/206166039-1.png)
new - mini warps in furballs, quite a few random big warps from some players:
(http://i975.photobucket.com/albums/ae235/RTHolmes/AH%20stuff/661512482.png)
:(
-
Folks, just hang there. The new ISP is going to review this data and see what they can do. We are obliged to give them an opportunity to see what they can do to help here.
For the most part, most people are getting better or the same connections. For those who are not (mostyle England and Germany), please post information in here.
Thank you.
-
I've been seeing a more erratic connection in the MA the last couple of weeks. Most of the time it is as normal but occassionally it will get warpy for a minute or two before settling down again. My ISP is Talktalk, here are my traceroutes:
(http://www.gfg06.dial.pipex.com/screenshots3/Ping_plots.jpg)
-
Folks, just hang there. The new ISP is going to review this data and see what they can do. We are obliged to give them an opportunity to see what they can do to help here.
For the most part, most people are getting better or the same connections. For those who are not (mostyle England and Germany), please post information in here.
Thank you.
Skuzzy, thank you for staying on top of it in the community - it does help to know you guys are taking it seriously.
-
I`ve had a few micro stutters here and there...not loads but worse than before
I`m talktalk too if that helps..
<S>Jimmy
-
I'm getting micro freezes and warps as well, no clue what a trace route is though. Mine seems to happen when a new object or other player comes into visual range so I'm not sure if that's a graphical/sound issue or part of this connection thing, but it's definately worse than it was a couple months ago.
-
I'm getting micro freezes and warps as well, no clue what a trace route is though. Mine seems to happen when a new object or other player comes into visual range so I'm not sure if that's a graphical/sound issue or part of this connection thing, but it's definately worse than it was a couple months ago.
That does not sound like network related issues. More of a resource issue, possibly. The test started two weeks ago, today. We are going to run it over the weekend and see what we can get more data from more players and the ISP is going to try some route manipulations as well.
-
FWIW, new ISP has better connection to me than the old one.
I have PP plots of it............how do you post to the BBS?
:salute
-
I'd like to report that I am still getting many many more mini warps from everyone regardless of their connections and mine.
The new ISP is better for reducing packet loss but worse for keeping enemy planes in the right places. The connection is unstable still.
-
Everyday routes can change. I need to see data to both destinations, at the time of the issue. I am trying to get real time data to the ISP so they can analyze the traffic to see what is going on.
I want to stress, we are getting more positive remarks than negative remarks. As a matter of fact, the number of negative remarks are pretty small compared to the number of players making connections.
We want to help, but we need data, in real time, as often as you need to post it (once a day is good). The new ISP has eleven different routes available to it, but BGP is pretty stupid and it may need some coaxing. They have made a few changes and some players just seem to have it bad no matter what we do.
That said, I would like to see some films showing the problem. That might help.
-
Would you prefer to have the films emailed or will a youtube film just showing examples of the mini warps suffice?
-
new
(http://imageshack.us/a/img407/7528/661512482.png)
old
(http://imageshack.us/a/img827/7854/206166038.png)
-
Would you prefer to have the films emailed or will a youtube film just showing examples of the mini warps suffice?
I cannot view youtube. Please email the films.
Twinboom, the biggest issue I see in your traces is at your very first hop. If you are using a router, you might want to power cycle it. The jitter looks worse in the 206.16.60.38 traces.
-
No films yet. The decision will be made soon.
-
Give me time Skuzzy, I have had to look through many many sorties to note times at which warps happen so your not having to watch the whole film.
But I will definately expodite my work and have it sent unfinished so you can see for yourself in the next 15mins or so.
EDIT: I keep getting This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
support@hitechcreations.com
18.4MB zip file which is under the 20MB limit.
-
(http://s8.postimage.org/dqdxbld2d/66_151_248_2.png)
(http://s15.postimage.org/3umb0n1x7/206_16_60_38.png)
-
Give me time Skuzzy, I have had to look through many many sorties to note times at which warps happen so your not having to watch the whole film.
But I will definately expodite my work and have it sent unfinished so you can see for yourself in the next 15mins or so.
EDIT: I keep getting
18.4MB zip file which is under the 20MB limit.
We have a 15MB limit on email.
Pand, your traces look a lot better to the new ISP. Is that what you are saying?
-
Pand, your traces look a lot better to the new ISP. Is that what you are saying?
While the data indicates otherwise, I have been experiencing warps and issues *since* the migration to the new ISP. I wonder if last night the warps and items experienced were others' connection issues?
Here's another set ran around 9am Eastern Friday morning. I'll run another during prime time again tonight.
(http://s11.postimage.org/q071wfk77/66_151_248_2.png)
(http://s12.postimage.org/484j0ndp9/206_16_60_38.png)
-
Another round from this afternoon --- 66.151.248.2 continues to show packet loss on hops 9 and 10.
(http://s10.postimage.org/9x3yaf3qh/66_151_248_2.png)
(http://s12.postimage.org/opa006rdp/206_16_60_38.png)
-
Pand, here is the return trip from the test ISP.
===
traceroute 74.131.1.245
traceroute to 74.131.1.245 (74.131.1.245), 30 hops max, 40 byte packets
1 66.151.248.1 (66.151.248.1) 0.376 ms 0.431 ms 0.332 ms
2 core1.pc1-bbnet1.ext1a.dal.pnap.net (216.52.191.39) 2.480 ms 1.421 ms 1.327 ms
3 er1-ge-7-12.dallasequinix.savvis.net (208.175.175.53) 1.137 ms 1.105 ms 1.650 ms
4 144.232.25.89 (144.232.25.89) 1.653 ms 4.282 ms 17.728 ms
5 144.232.11.211 (144.232.11.211) 2.900 ms 2.734 ms 144.232.11.179 (144.232.11.179) 3.980 ms
6 144.232.1.160 (144.232.1.160) 2.611 ms 7.730 ms 8.342 ms
7 sl-crs2-nsh-0-5-2-0.sprintlink.net (144.232.24.251) 22.986 ms sl-crs2-nsh-0-11-5-0.sprintlink.net (144.232.9.31) 23.962 ms sl-crs1-nsh-0-11-1-0.sprintlink.net (144.232.20.19) 21.813 ms
8 sl-crs1-roa-0-12-2-0.sprintlink.net (144.232.6.111) 29.074 ms 29.635 ms 28.376 ms
9 sl-gw22-roa-14-0-0.sprintlink.net (144.232.5.106) 28.240 ms sl-gw22-roa-15-0-0.sprintlink.net (144.232.5.108) 28.779 ms sl-gw22-roa-14-0-0.sprintlink.net (144.232.5.106) 29.383 ms
10 sl-insig-265776-0.sprintlink.net (144.223.18.42) 36.943 ms 36.957 ms 36.509 ms
11 * * *
12 74-131-1-245.dhcp.insightbb.com (74.131.1.245) 38.859 ms * 39.335 ms
Here it is from the old server location.
====
traceroute 74.131.1.245
traceroute: Warning: Multiple interfaces found; using 206.16.60.41 @ e1000g0
traceroute to 74.131.1.245 (74.131.1.245), 30 hops max, 40 byte packets
1 206.16.60.46 (206.16.60.46) 0.846 ms 0.518 ms 0.384 ms
2 mdf001c7613r0002-gig-10-2.dal1.attens.net (63.241.193.17) 0.702 ms 0.320 ms 0.320 ms
3 12.122.251.57 (12.122.251.57) 1.032 ms 12.122.251.61 (12.122.251.61) 1.013 ms 12.122.251.57 (12.122.251.57) 1.016 ms
4 cr2.dlstx.ip.att.net (12.122.138.190) 5.709 ms cr1.dlstx.ip.att.net (12.122.85.70) 3.758 ms cr2.dlstx.ip.att.net (12.122.138.190) 4.417 ms
5 dlstx02jt.ip.att.net (12.122.214.245) 1.202 ms dlstx02jt.ip.att.net (12.122.214.249) 9.857 ms 1.271 ms
6 144.232.7.41 (144.232.7.41) 2.145 ms 1.869 ms 2.284 ms
7 144.232.11.207 (144.232.11.207) 3.327 ms sl-crs4-fw-0-4-0-0.sprintlink.net (144.232.25.191) 3.570 ms 144.232.11.181 (144.232.11.181) 5.396 ms
8 144.232.1.162 (144.232.1.162) 3.367 ms 2.851 ms 2.811 ms
9 sl-crs1-nsh-0-5-0-0.sprintlink.net (144.232.8.65) 24.889 ms sl-crs2-nsh-0-9-2-0.sprintlink.net (144.232.25.123) 23.881 ms sl-crs2-nsh-0-5-2-0.sprintlink.net (144.232.24.251) 23.225 ms
10 sl-crs2-roa-0-2-5-0.sprintlink.net (144.232.25.221) 28.791 ms 28.601 ms sl-crs2-roa-0-0-3-0.sprintlink.net (144.232.6.115) 31.182 ms
11 sl-gw22-roa-15-0-0.sprintlink.net (144.232.5.108) 27.931 ms 28.208 ms 27.845 ms
12 sl-insig-265776-1.sprintlink.net (144.223.18.42) 38.781 ms 39.087 ms 39.047 ms
13 * * *
14 74-131-1-245.dhcp.insightbb.com (74.131.1.245) 36.190 ms * 36.909 ms
I am seeing packet loss on both, but that could be the router giving ICMP ECHO messages a low priority.
Once both routes hit Sprint, they have the same route going back and the packet loss is on that side of the route.
-
I have been seeing more mini warps as well, usually in among a large group of AC. Not sure what it all means, but seems the average times have almost doubled... I'm not complaining just trying to provide some more data.
Target Name: N/A
IP: 66.151.248.2
Date/Time: 11/2/2012 5:58:58 PM to 11/2/2012 6:01:13 PM
1 9 ms 10 ms 12 ms 11 ms 9 ms 7 ms 6 ms 7 ms 8 ms 7 ms [10.81.64.1]
2 101 ms 110 ms 7 ms 8 ms 10 ms 8 ms 9 ms 11 ms 9 ms 8 ms 24-234-16-157.ptp.lvcm.net [24.234.16.157]
3 * * * * * * * * * * [-]
4 10 ms 17 ms 10 ms 8 ms 11 ms 8 ms 11 ms 57 ms 11 ms 9 ms 24-234-6-254.ptp.lvcm.net [24.234.6.254]
5 24 ms 26 ms 26 ms 24 ms 25 ms 24 ms 89 ms 57 ms 25 ms 23 ms paltbprj01-ae0.0.rd.pt.cox.net [68.1.0.234]
6 30 ms 29 ms 30 ms 30 ms 33 ms 28 ms 30 ms 28 ms 29 ms 28 ms dcr2-ge-7-0-0-292.sanfranciscosfo.savvis.net [208.173.170.1]
7 32 ms 43 ms 54 ms 32 ms 33 ms 43 ms 36 ms 35 ms 37 ms 34 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.70.200.198]
8 66 ms 68 ms 66 ms 66 ms 66 ms 68 ms 67 ms 68 ms 69 ms 65 ms dcr2-so-5-0-0.Chicago.savvis.net [204.70.192.46]
9 89 ms 88 ms 125 ms 64 ms 63 ms 61 ms 64 ms 61 ms 63 ms 61 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]
10 60 ms 64 ms 60 ms 64 ms 61 ms 61 ms 103 ms 64 ms 62 ms 61 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.145]
11 61 ms 62 ms 64 ms 62 ms 63 ms 62 ms 65 ms 61 ms 62 ms 62 ms [208.175.175.54]
12 87 ms 63 ms 63 ms 61 ms 62 ms 61 ms 62 ms 62 ms 65 ms 62 ms border1.te3-1-bbnet1.dal006.pnap.net [216.52.191.2]
13 64 ms 74 ms 83 ms 78 ms 65 ms 67 ms 65 ms 65 ms 67 ms 66 ms [66.151.248.2]
Ping statistics for 66.151.248.2
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 64ms, Maximum = 83ms, Average = 69ms
Target Name: N/A
IP: 206.16.60.38
Date/Time: 11/2/2012 6:06:39 PM to 11/2/2012 6:08:54 PM
1 9 ms 10 ms 9 ms 7 ms 8 ms 7 ms 8 ms 7 ms 8 ms 7 ms [10.81.64.1]
2 39 ms 8 ms 8 ms 38 ms 10 ms 8 ms 38 ms 18 ms 11 ms 39 ms 24-234-16-153.ptp.lvcm.net [24.234.16.153]
3 10 ms 10 ms 10 ms 24 ms 20 ms 11 ms 9 ms 9 ms 9 ms 19 ms 24-234-6-121.ptp.lvcm.net [24.234.6.121]
4 10 ms 9 ms 11 ms 10 ms 10 ms 33 ms 10 ms 9 ms 10 ms 9 ms 24-234-6-218.ptp.lvcm.net [24.234.6.218]
5 21 ms 20 ms 49 ms 22 ms 22 ms 21 ms 21 ms 21 ms 21 ms 21 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 16 ms 16 ms 16 ms 15 ms 14 ms 17 ms 14 ms 15 ms 17 ms 15 ms xe-7-3-1.edge2.LosAngeles9.Level3.net [4.53.230.41]
7 17 ms 15 ms 14 ms 15 ms 16 ms 26 ms 16 ms 17 ms 16 ms 15 ms [192.205.37.145]
8 63 ms 65 ms 66 ms 65 ms 60 ms 69 ms 62 ms 65 ms 63 ms 61 ms cr2.la2ca.ip.att.net [12.122.129.106]
9 58 ms 58 ms 50 ms 51 ms 52 ms 51 ms 51 ms 49 ms 51 ms 52 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 71 ms 76 ms 131 ms 170 ms 63 ms 63 ms 61 ms 61 ms 61 ms 59 ms ggr1.dlstx.ip.att.net [12.122.138.1]
11 64 ms 63 ms N/A 65 ms N/A 61 ms 61 ms 63 ms N/A 62 ms [12.122.251.70]
12 50 ms 49 ms 49 ms 51 ms 51 ms 51 ms 49 ms 51 ms 52 ms 63 ms mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
13 49 ms 50 ms 49 ms 50 ms 49 ms 51 ms 48 ms 50 ms 51 ms 48 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 48ms, Maximum = 51ms, Average = 49ms
-
Will do another plot later, but ingame the Host Qeue Time is extremely jittery all the time in LW, while perfectly flat in EW and MW. I see alot of mini warps and for the first time in my AH carre I seem to experience what they call "rubber bullets"
-
I'm getting the same as Lusche, very spiky host queue graph in the LW MA but flat in the other MAs and some mini warps.
-
A spiky host queue graph would normally indicate an issue with the server itself. I'll look into that. We are using a server we have never used for an arena before.
-
I read this
A spiky host queue graph would normally indicate an issue with the server itself.
I remembered this
But look at the spikes in the new servers ping trace, it's probably the cause of alot of the mini warps.
(http://www.dreamwidth.org/userpic/27224/52508)
http://www.youtube.com/watch?v=qMa0CxgCqiM
-
I'm getting the same as Lusche, very spiky host queue graph in the LW MA but flat in the other MAs and some mini warps.
Same for me too very spiky graph but i was smooth as glass in the Scenario arena
-
A spiky host queue graph would normally indicate an issue with the server itself. I'll look into that. We are using a server we have never used for an arena before.
That's the current situation for me:
MW:
(http://i1145.photobucket.com/albums/o507/Snaildude/mw.jpg)
LW:
(http://i1145.photobucket.com/albums/o507/Snaildude/lw.jpg)
Both taken in the past 30 mins, with some, but not too many planes around in both cases.
-----
New LW:
Target Name: N/A
IP: 66.151.248.2
Date/Time: 06.11.2012 03:02:17 to 06.11.2012 03:04:37
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 15 0 0,0 0 3 1 [192.168.1.1]
2 15 0 0,0 8 17 10 esn001ibr002-xdsl.versatel.de [62.214.64.97]
3 15 0 0,0 8 201 21 ge-1-10-v515.esn001isp006.versatel.de [62.214.105.213]
4 15 0 0,0 9 206 26 fra20ip6.versatel.de [62.214.104.174]
5 15 0 0,0 15 123 27 10g-8-4.hhb002isp005.versatel.de [62.214.110.122]
6 15 0 0,0 14 18 15 hmb-s2-rou-1103.DE.eurorings.net [134.222.120.117]
7 15 0 0,0 106 122 108 dssd-s2-rou-1102.DE.eurorings.net [134.222.229.57]
8 15 0 0,0 136 182 155 asd2-rou-1022.NL.eurorings.net [134.222.228.137]
9 15 0 0,0 36 74 39 mchr-s1-rou-1041.UK.eurorings.net [134.222.228.14]
10 15 0 0,0 108 110 109 nyk-s2-rou-1001.US.eurorings.net [134.222.226.157]
11 15 0 0,0 98 163 104 [12.250.255.9]
12 15 0 0,0 143 148 145 [12.122.105.90]
13 15 0 0,0 143 147 145 cr2.wswdc.ip.att.net [12.122.3.38]
14 15 0 0,0 144 149 146 cr1.attga.ip.att.net [12.122.1.173]
15 15 0 0,0 144 150 146 cr2.dlstx.ip.att.net [12.122.28.174]
16 15 0 0,0 142 255 163 ggr6.dlstx.ip.att.net [12.122.138.113]
17 15 0 0,0 144 200 148 [12.90.228.14]
18 15 0 0,0 145 148 146 border1.te4-1-bbnet2.dal006.pnap.net [216.52.191.66]
19 15 0 0,0 144 148 145 [66.151.248.2]
old LW
Target Name: N/A
IP: 206.16.60.38
Date/Time: 06.11.2012 03:05:27 to 06.11.2012 03:08:17
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 18 0 0,0 0 3 1 [192.168.1.1]
2 18 0 0,0 9 40 11 esn001ibr002-xdsl.versatel.de [62.214.64.97]
3 18 0 0,0 8 65 17 ge-1-10-v515.esn001isp006.versatel.de [62.214.105.213]
4 18 0 0,0 8 216 31 [62.214.111.25]
5 18 0 0,0 9 141 28 10g-9-1.dus002isp005.versatel.de [62.214.110.233]
6 18 0 0,0 9 50 14 [212.162.17.5]
7 18 0 0,0 9 41 13 vl-3201-ve-128.ebr2.Dusseldorf1.Level3.net [4.69.161.133]
8 18 0 0,0 12 26 13 ae-45-45.ebr1.Amsterdam1.Level3.net [4.69.143.197]
9 18 0 0,0 12 16 13 ae-1-100.ebr2.Amsterdam1.Level3.net [4.69.141.170]
10 18 0 0,0 19 26 20 ae-48-48.ebr2.London1.Level3.net [4.69.143.82]
11 18 0 0,0 88 177 94 ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
12 18 0 0,0 88 149 97 ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
13 18 0 0,0 88 119 90 ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
14 18 0 0,0 92 270 103 att-level3.newyork1.level3.net [4.68.63.142]
15 18 0 0,0 134 313 146 cr2.n54ny.ip.att.net [12.122.130.170]
16 18 0 0,0 134 282 144 cr2.wswdc.ip.att.net [12.122.3.38]
17 18 0 0,0 135 273 144 cr1.attga.ip.att.net [12.122.1.173]
18 18 0 0,0 136 244 144 cr2.dlstx.ip.att.net [12.122.28.174]
19 18 0 0,0 132 218 140 ggr1.dlstx.ip.att.net [12.122.138.1]
20 13 0 0,0 133 252 147 [12.122.251.70]
21 18 0 0,0 133 207 141 mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
22 18 0 0,0 133 140 135 [206.16.60.38]
-
Not sure if everyone else's issues have been resolved, but apparently the issue was on my side. My cable modem was porking out, and as long as only a few connections were actively using the internet, all was fine and full/normal speed; however, if anyone on my connection did anything else, it drastically affected my ping to the AH servers.
Cable modem replaced, connection and variance is perfect now.