New ISP Adjustment

[Skuzzy]

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]

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.

[Pand]

Another round from this afternoon --- 66.151.248.2 continues to show packet loss on hops 9 and 10.

[Skuzzy]

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.

[Halo46]

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

[Lusche]

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"

[Greebo]

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.

[Skuzzy]

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.

[LCADolby]

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.youtube.com/watch?v=qMa0CxgCqiM

[TwinBoom]

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

[Lusche]

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:



LW:


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]

[Pand]

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.