Author Topic: New ISP Adjustment (Read 3438 times)

Meatwad · « **Reply #15 on:** October 22, 2012, 10:29:57 PM »

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

BushLT1 · « **Reply #16 on:** October 22, 2012, 11:31:25 PM »

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.

JimmyC · « **Reply #17 on:** October 23, 2012, 05:27:01 AM »

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

Skuzzy · « **Reply #18 on:** October 23, 2012, 06:07:14 AM »

Quote from: Paladin3 on October 22, 2012, 06:00:34 PM

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

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.

Skuzzy · « **Reply #19 on:** October 23, 2012, 06:14:19 AM »

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.

Bruv119 · « **Reply #20 on:** October 23, 2012, 07:57:17 AM »

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.

Skuzzy · « **Reply #21 on:** October 23, 2012, 11:48:28 AM »

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.

JimmyC · « **Reply #22 on:** October 23, 2012, 12:54:58 PM »

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

Saw you wanted British info so offered up mine....
will report back after next time I play
Sorry for any confusion
<S> Jimmy

Skuzzy · « **Reply #23 on:** October 23, 2012, 01:00:13 PM »

Quote from: JimmyC on October 23, 2012, 12:54:58 PM

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

LCADolby · « **Reply #24 on:** October 23, 2012, 02:35:43 PM »

Old Server

NewServer

I did these around 20:30 during peak time.

Skuzzy · « **Reply #25 on:** October 23, 2012, 02:55:37 PM »

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.

LCADolby · « **Reply #26 on:** October 23, 2012, 02:58:03 PM »

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

Skuzzy · « **Reply #27 on:** October 23, 2012, 03:03:20 PM »

Quote from: LCADolby on October 23, 2012, 02:58:03 PM

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.

LCADolby · « **Reply #28 on:** October 23, 2012, 03:24:02 PM »

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.

RTHolmes · « **Reply #29 on:** October 23, 2012, 03:43:07 PM »

old - rock solid, very rarely saw warps:

new - mini warps in furballs, quite a few random big warps from some players:

Aces High Bulletin Board

Author Topic: New ISP Adjustment (Read 3438 times)

Meatwad

Re: New ISP Adjustment

BushLT1

Re: New ISP Adjustment

JimmyC

Re: New ISP Adjustment

Skuzzy

Re: New ISP Adjustment

Skuzzy

Re: New ISP Adjustment

Bruv119

Re: New ISP Adjustment

Skuzzy

Re: New ISP Adjustment

JimmyC

Re: New ISP Adjustment

Skuzzy

Re: New ISP Adjustment

LCADolby

Re: New ISP Adjustment

Skuzzy

Re: New ISP Adjustment

LCADolby

Re: New ISP Adjustment

Skuzzy

Re: New ISP Adjustment

LCADolby

Re: New ISP Adjustment

RTHolmes

Re: New ISP Adjustment