http://www.dslreports.com/forum/r20836310 en Tue, 02 Dec 2008 14:25:08 EDT Tue, 02 Dec 2008 14:25:08 EDT http://www.dslreports.com/forum/remark,20836310 justbits : My workplace has Comcast Business Workplace Internet. We have 5 static IPs.
What I'm seeing is that some of the True Static IP hosts have about a 30ms ping time to various servers on the Internet. However, others have 60ms (double) ping times to those same servers. This problem started on July 13th around 4pm and was in full effect at 10pm.

It seems that the .172 host takes this route:
2 ge-2-8-ur01.elmhurst.il.chicago.comcast.net (68.86.115.225) 14.566 ms 9.948 ms 6.929 ms 3 ge-1-4-ar01.mishawaka.in.sbend.comcast.net (68.87.230.238) 7.518 ms 12.571 ms 9.427 ms 4 pos-0-11-0-0-ar01.area4.il.chicago.comcast.net (68.86.90.50) 28.582 ms 14.033 ms 8.632 ms 5 pos-0-6-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.49) 18.916 ms 243.352 ms 252.825 ms 6 xe-10-1-0.edge1.Chicago2.Level3.net (4.71.248.17) 247.603 ms 241.833 ms 336.011 ms 7 ae-23-56.car3.Chicago1.Level3.net (4.68.101.167) 248.519 ms ae-13-53.car3.Chicago1.Level3.net (4.68.101.71) 18.489 ms ae-23-54.car3.Chicago1.Level3.net (4.68.101.103) 11.586 ms 8 sbc-level3-te.chicago1.level3.net (4.68.110.198) 11.279 ms 13.823 ms 14.050 ms 9 bb2-p2-0.emhril.ameritech.net (151.164.42.140) 18.770 ms 11.440 ms 11.160 ms10 dist1-g2-3.emhril.sbcglobal.net (151.164.94.165) 12.772 ms 13.933 ms 12.437 ms11 rback4-g1-0.emhril.ameritech.net (68.22.72.71) 14.906 ms 10.308 ms 12.453 ms
The .170 and .174 hosts take this route:
2 ge-2-8-ur01.elmhurst.il.chicago.comcast.net (68.86.115.225) 10.063 ms 16.086 ms 9.917 ms 3 68.87.231.113 (68.87.231.113) 14.43 ms 9.366 ms 12.139 ms 4 pos-0-10-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.90.174) 19.006 ms 22.63 ms 19.227 ms 5 pos-0-0-0-0-cr01.nashville.tn.ibone.comcast.net (68.86.90.173) 29.052 ms 26.776 ms 31.115 ms 6 pos-0-3-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.66) 39.108 ms 34.26 ms 35.519 ms 7 te-4-3.car1.atlanta2.level3.net (4.71.252.25) 37.644 ms 35.207 ms 33.944ms 8 ae-72-52.ebr2.atlanta2.level3.net (4.68.103.61) 40.534 ms 34.149 ms 36.801 ms 9 ae-63-60.ebr3.atlanta2.level3.net (4.69.138.4) 38.119 ms 48.59 ms 36.84 ms10 ae-2.ebr1.washington1.level3.net (4.69.132.86) 50.473 ms 51.916 ms 53.956 ms11 ae-71-71.csw2.washington1.level3.net (4.69.134.134) 53.241 ms 51.086 ms 53.878 ms12 ae-24-79.car4.washington1.level3.net (4.68.17.70) 52.232 ms 55.682 ms 52.667 ms13 asn3356-level3.eqabva.sbcglobal.net (4.68.111.186) 171.935 ms 205.971 ms72.94 ms14 bb1-p11-0.emhril.ameritech.net (151.164.240.194) 47.691 ms 41.571 ms 42.783 ms15 dist1-g1-1.emhril.sbcglobal.net (151.164.43.83) 41.095 ms 41.553 ms 40.703 ms16 rback4-g1-0.emhril.ameritech.net (68.22.72.71) 47.522 ms 42.134 ms 41.1 ms
The traces above were from the Comcast line to a Chicagoland AT+T DSL host. Traceroute to a different AT+T DSL host doesn't exhibit this latency issue.

Traceroute originated from external networks to the Comcast business IPs don't show this issue, in fact the final route is the same from their perspectives.
Traceroute from the Comcast business IPs doesn't show this issue.
Ping from external networks reveals the issue.
Ping from the Comcast business IPs reveals the issue.

Any ideas?
]]> http://www.dslreports.com/forum/remark,20836310 Wed, 23 Jul 2008 12:14:23 EDT