UDP loss and IPs between me and HTC

[fuzeman]

OK, didnt fly yesterday but loaded the new patch today and when online I noticed a unusual amount of UDP to TCP switching. When I ran a pingplot I noticed something I never have before. The listing of IPs between me and HTC are changing. I never noticed this before, they used to all stay the same and I'd use one rounte to communicate. Now I'm changing my route to HTC about every 2nd or 3rd ping.
Not being an expert on netstuff I was wondering if I just didn't notice this before or is something wacky going on. My assumption was we needed one consistant route to HTC using the same IPs allowing us to use UDP, is this correct?
Do the IPs in route to HTC change like that or is it the usualy wacky nature of the net?

[fuzeman]

OK, ran a few pingplots and here are the results. IPs on hops 2,4,5,7 & 8 change every second or third ping wether I ping the 39 or 38 server, all these are on 39. I'm also still getting a loopback on hop #6 but I think that's a minor detail.


Many thanks for the help and assistance. I run Win98se and use a dialup connection to Earthlink. If you need anything else let me know and I'll post or call you.
If needed the case # when I talked to the tech is 87537319.

[Skuzzy]

wrag, I need some traces posted in this thread.  I am pointing Savvis at it to see if we can do some joint work on this issue.

Fuze, here is a trace back to you from 216.91.187.39 (actually, to the second hop, as it is a router).
traceroute to 63.212.200.3 (63.212.200.3), 30 hops max, 40 byte packets
 1  216.91.187.34 (216.91.187.34)  0.431 ms  0.349 ms  0.980 ms
 2  208.172.1.221 (208.172.1.221)  6.368 ms  6.324 ms  6.334 ms
 3  dcr2-so-2-2-0.Chicago.savvis.net (208.172.3.81)  6.519 ms  6.368 ms  6.408 ms
 4  bpr1-so-0-0-0.ChicagoEquinix.savvis.net (208.175.10.238)  6.495 ms  6.540 ms  6.581 ms
 5  ge-2-0-1.edge1.Chicago1.Level3.net (208.174.226.62)  6.531 ms ge-2-0-0.edge1.Chicago1.Level3.net (208.174.226.58)  6.830 ms  6.548 ms
 6  * * *
 7  64.159.4.177 (64.159.4.177)  29.807 ms so-0-1-0.mp2.Boston1.Level3.net (209.247.9.126)  29.811 ms 64.159.4.177 (64.159.4.177)  29.658 ms
 8  ge-11-0.hsa1.Boston1.Level3.net (4.68.100.36)  29.608 ms ge-10-2.hsa1.Boston1.Level3.net (4.68.100.132)  29.673 ms ge-11-0.hsa1.Boston1.Level3.net (4.68.100.36)  30.094 ms
 9  ge-7-0-1.hsa2.Boston1.Level3.net (63.212.200.3)  30.346 ms * ge-11-2.hsa2.Boston1.Level3.net (4.68.100.165)  29.948 ms

Pretty ugly.

[Skuzzy]

This is from Pannzzer.  Another client.
====
Here's my ping stats, there's packet loss at Savvis.net:


Oh, and normal ping times (MA) are at around 150 ms.

[Skuzzy]

Here is a trace back from 216.91.187.39 to Pannzzer's second hop.
===
traceroute to 80.223.224.1 (80.223.224.1), 30 hops max, 40 byte packets
 1  216.91.187.34 (216.91.187.34)  0.541 ms  0.406 ms  0.322 ms
 2  at-0-2-901.usstls1-01.j20c.savvis.net (206.129.9.89)  0.680 ms  0.910 ms  0.721 ms
 3  208.172.163.133 (208.172.163.133)  20.385 ms  20.324 ms  20.224 ms
 4  dcr1-loopback.LosAngeles.savvis.net (208.172.34.107)  51.229 ms  51.200 ms  51.352 ms
 5  bpr1-so-0-0-0.LosAngelesEquinix.savvis.net (208.172.44.106)  51.145 ms  51.460 ms  101.340 ms
 6  las-bb1-so2-3-3.telia.net (208.174.196.2)  51.252 ms  51.299 ms  51.214 ms
 7  dls-bb1-pos0-0-0.telia.net (213.248.80.22)  85.606 ms  85.575 ms  85.602 ms
 8  213.248.80.150 (213.248.80.150)  77.550 ms  78.413 ms  78.154 ms
 9  nyk-bb2-pos7-1-0.telia.net (213.248.80.74)  77.446 ms  78.200 ms  77.907 ms
10  kbn-bb2-pos1-3-0.telia.net (213.248.64.33)  167.962 ms  167.854 ms  167.927 ms
11  s-bb2-pos7-0-0.telia.net (213.248.65.30)  175.861 ms  175.970 ms  175.857 ms
12  hls-b4-pos3-0-0.telia.net (213.248.64.138)  201.338 ms  181.834 ms  181.640 ms
13  soneracarrier-105059-hls-b4.c.telia.net (213.248.99.158)  186.361 ms  186.297 ms  186.325 ms
14  trecore1-so1-0-0.datanet.tele.fi (193.227.224.6)  192.972 ms  183.789 ms  183.881 ms
15  193.227.224.146 (193.227.224.146)  184.043 ms  183.848 ms  183.749 ms
16  141.208.206.106 (141.208.206.106)  184.648 ms  184.624 ms *

[straffo]

I can't say for sure when it started as I changed ISP 1 week ago

It's either pretty stable or completly porked ...


Btw Skuzzy did you got my email concerning my bill ?

[Skuzzy]

This is a trace back to the third hop of the above PingPlot (attempting to trace to the second hop caused an immediate failure).
===
traceroute to 195.115.106.1 (195.115.106.1), 30 hops max, 40 byte packets
 1  216.91.187.34 (216.91.187.34)  0.422 ms  0.591 ms  0.462 ms
 2  208.172.1.221 (208.172.1.221)  6.324 ms  6.627 ms  6.486 ms
 3  dcr2-so-2-2-0.Chicago.savvis.net (208.172.3.81)  6.477 ms  6.454 ms  6.394 ms
 4  bpr1-so-0-0-0.ChicagoEquinix.savvis.net (208.175.10.238)  6.515 ms  6.617 ms  6.497 ms
 5  ge-2-0-0.edge1.Chicago1.Level3.net (208.174.226.58)  6.630 ms ge-2-0-1.edge1.Chicago1.Level3.net (208.174.226.62)  106.939 ms  6.511 ms
 6  so-2-1-0.bbr2.Chicago1.Level3.net (209.244.8.13)  6.760 ms  6.567 ms  6.577 ms
 7  so-2-0-0.bbr2.Washington1.Level3.net (209.247.10.130)  23.666 ms  23.869 ms  23.675 ms
 8  as-0-0.bbr1.London2.Level3.net (4.68.128.101)  97.580 ms  97.312 ms  114.287 ms
 9  so-3-0-0.mp2.Paris1.Level3.net (212.187.128.37)  102.682 ms so-1-0-0.mp1.Paris1.Level3.net (212.187.128.41)  102.695 ms  143.711 ms
10  ge-11-1.ipcolo2.Paris1.Level3.net (212.73.240.84)  102.448 ms ge-10-0.ipcolo2.Paris1.Level3.net (212.73.240.8)  102.469 ms ge-11-2.ipcolo2.Paris1.Level3.net (212.73.240.118)  102.379 ms
11  212.73.204.134 (212.73.204.134)  103.584 ms  103.379 ms  103.263 ms
12  80.124.170.19 (80.124.170.19)  103.548 ms  103.698 ms  104.674 ms
13  195.115.104.206 (195.115.104.206)  105.490 ms  105.751 ms  105.311 ms
14  195.115.106.1 (195.115.106.1)  105.260 ms *  105.042 ms

[Flyboy]

what software do you use to generate those graphs?

[eta32]

Target Name: N/A
         IP: 216.91.187.39
  Date/Time: 12/9/2004 1:32:10 PM

 1    8 ms   13 ms   11 ms   10 ms   10 ms  [10.129.32.1]
 2    9 ms   *        9 ms   12 ms   11 ms  [68.11.12.89]
 3   11 ms   10 ms    9 ms   11 ms   13 ms  mctydsrc02-gew0304.rd.no.cox.net [68.11.14.17]
 4   10 ms   11 ms   10 ms    9 ms   12 ms  mctybbrc02-pos0101.rd.no.cox.net [68.1.0.68]
 5   22 ms   21 ms   24 ms   29 ms   21 ms  lkhnbbrc02-pos0102.rd.at.cox.net [68.1.0.10]
 6   26 ms   25 ms   24 ms   20 ms   23 ms  [12.124.65.61]
 7   22 ms   21 ms   35 ms   21 ms   23 ms  gbr5-p90.attga.ip.att.net [12.123.21.82]
 8   22 ms   24 ms   26 ms   24 ms   21 ms  tbr1-p013501.attga.ip.att.net [12.122.12.21]
 9   34 ms   25 ms   25 ms   21 ms   28 ms  ggr1-p340.attga.ip.att.net [12.122.12.30]
10   24 ms   22 ms   26 ms   29 ms   22 ms  dcr1-so-4-0-0.atlanta.savvis.net [192.205.32.118]
11  N/A     N/A     N/A     N/A      48 ms  dcr1-loopback.Chicago.savvis.net [208.172.2.99]
12   49 ms   49 ms  N/A     N/A      50 ms  acr2-so-0-0-0.Chicago.savvis.net [208.172.3.82]
13   64 ms   55 ms   59 ms   56 ms   59 ms  [208.172.1.202]
14   60 ms   59 ms   57 ms   57 ms   57 ms  [216.91.187.39]

Ping statistics for 216.91.187.39
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 57ms, Maximum = 60ms, Average = 58ms

[eta32]

Target Name: N/A
         IP: 216.91.187.39
  Date/Time: 12/9/2004 1:37:37 PM

 1   10 ms  [10.129.32.1]
 2   23 ms  [68.11.12.89]
 3   54 ms  mctydsrc01-gew0304.rd.no.cox.net [68.11.14.9]
 4  129 ms  mctybbrc01-pos0101.rd.no.cox.net [68.1.0.64]
 5   11 ms  mctybbrc02-pos0100.rd.no.cox.net [68.1.0.63]
 6  136 ms  lkhnbbrc02-pos0102.rd.at.cox.net [68.1.0.10]
 7   22 ms  [12.124.65.61]
 8   24 ms  gbr5-p90.attga.ip.att.net [12.123.21.82]
 9   22 ms  tbr1-p013501.attga.ip.att.net [12.122.12.21]
10   21 ms  ggr1-p340.attga.ip.att.net [12.122.12.30]
11   23 ms  dcr1-so-4-0-0.atlanta.savvis.net [192.205.32.118]
12   51 ms  dcr2-loopback.Chicago.savvis.net [208.172.2.100]
13   49 ms  acr2-so-1-0-0.Chicago.savvis.net [208.172.3.86]
14   59 ms  [208.172.1.202]
15   56 ms  [216.91.187.39]

Ping statistics for 216.91.187.39
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 56ms, Maximum = 56ms, Average = 56ms

[Skuzzy]

This is a traceroute back to your second hop eta, from 216.91.187.39.
====
traceroute to 68.11.12.89 (68.11.12.89), 30 hops max, 40 byte packets
 1  216.91.187.34 (216.91.187.34)  0.436 ms  0.537 ms  0.437 ms
 2  208.172.1.221 (208.172.1.221)  6.446 ms  30.134 ms  6.371 ms
 3  dcr1-so-2-3-0.Chicago.savvis.net (208.172.3.85)  6.327 ms  6.423 ms  6.386 ms
 4  savvis-gw.cgcil02ck4.ip.att.net (208.175.10.94)  6.693 ms  6.538 ms  6.667 ms
 5  tbr2-p012201.cgcil.ip.att.net (12.123.6.38)  7.094 ms  7.469 ms  7.265 ms
 6  tbr2-cl7.sl9mo.ip.att.net (12.122.10.46)  13.445 ms  13.349 ms  13.240 ms
 7  12.122.10.137 (12.122.10.137)  35.504 ms  33.945 ms  33.786 ms
 8  gbr6-p40.attga.ip.att.net (12.122.12.46)  32.958 ms  32.980 ms  32.967 ms
 9  gar3-p370.attga.ip.att.net (12.123.21.85)  33.043 ms  33.040 ms  33.064 ms
10  12.124.65.62 (12.124.65.62)  33.641 ms  41.059 ms  33.663 ms
11  mctybbrc02-pos0102.rd.no.cox.net (68.1.0.11)  44.586 ms  44.598 ms  44.442 ms
12  mctydsrc02-pos0901.rd.no.cox.net (68.1.0.69)  44.437 ms  44.483 ms  44.578 ms
13  68.11.12.89 (68.11.12.89)  44.748 ms  44.565 ms  44.513 ms

[Skuzzy]

Look guys, I am trying to keep this thread free of discussion so Savvis personnel can read it.  It would be appreciated if you would move any discussions to another thread.  Thank you.

[Octavius]

Not having connection problems, but I ran a tracert for the hell of it:

I'm in Milwaukee

[Zuum]

[Skuzzy]

Zuum, this is a trace back to your second IP in your traceroute from 216.91.187.39;
=====
traceroute to 62.121.46.161 (62.121.46.161), 30 hops max, 40 byte packets
 1  216.91.187.34 (216.91.187.34)  0.812 ms  0.375 ms  0.399 ms
 2  208.172.1.221 (208.172.1.221)  6.631 ms  6.541 ms  6.348 ms
 3  dcr1-so-2-3-0.Chicago.savvis.net (208.172.3.85)  6.489 ms  6.455 ms  6.526 ms
 4  dcr1-loopback.Washington.savvis.net (206.24.226.99)  23.313 ms  23.509 ms  23.407 ms
 5  cable-and-wireless-americas-operations.Washington.savvis.net (206.24.238.18)  23.256 ms  23.234 ms  23.168 ms
 6  so-7-0-0-dcr1.nyk.cw.net (195.2.3.2)  27.978 ms  27.967 ms  28.647 ms
 7  so-2-0-0-dcr1.tsd.cw.net (195.2.10.114)  99.325 ms  98.963 ms  98.929 ms
 8  so-0-0-0-dcr2.amd.cw.net (195.2.10.145)  105.651 ms  105.809 ms  106.092 ms
 9  so-5-0-0-bcr3.amd.cw.net (195.2.10.85)  105.826 ms  105.695 ms  105.793 ms
10  so-1-0-0-ycr2.cpi.cw.net (208.173.211.234)  118.951 ms  118.929 ms  118.881 ms
11  so-2-0-0-ycr1.cpi.cw.net (208.173.216.1)  119.203 ms  119.049 ms  118.930 ms
12  so-1-0-0-ycr1.skt.cw.net (208.173.216.26)  127.227 ms  127.199 ms  127.257 ms
13  ge-1-3-0-zar1.skt.cw.net (166.63.220.147)  127.270 ms  127.249 ms  127.207 ms
14  finnet-verkot-oy1.stk.cw.net (166.63.220.82)  127.348 ms  127.339 ms  127.446 ms
15  217.78.198.233 (217.78.198.233)  132.866 ms  132.850 ms  132.835 ms
16  217.78.198.225 (217.78.198.225)  136.340 ms  136.062 ms  136.359 ms
17  adsl-gw-46.161.ssp.fi (62.121.46.161)  137.231 ms  137.272 ms  137.336 ms