NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
1 edit | Re: [Connectivity] Major Slow Down in San Jose, CA
said by XTCBoY2K  :The problem is the second hop. My second hop has been down for several weeks now. Do you mean the hop that fails? Like everybody else's trace routes show? I am told that it's your CMTS, and that is is configured to not respond to ICMP packets; no ping.
10/21/05 01:36:12 Slow traceroute Ikuko
Trace Ikuko (67.171.201.211) ...
192.168.102.1 RTT: 0ms TTL: 64 (Chihiro ok)
192.168.0.1 RTT: 41ms TTL:170 (Suzuka ok)
71.132.15.254 RTT: 28ms TTL:170 (adsl-71-132-15-254.dsl.sntc01.pacbell.net ok)
63.203.51.65 RTT: 27ms TTL:170 (dist1-vlan60.sntc01.pbi.net ok)
64.161.1.145 RTT: 28ms TTL:170 (bb1-g8-0-1.sntcca.sbcglobal.net ok)
151.164.40.170 RTT: 27ms TTL:170 (bb2-p6-0.sntc01.sbcglobal.net ok)
151.164.241.197 RTT: 27ms TTL:170 (core2-p6-2.crscca.sbcglobal.net ok)
151.164.40.62 RTT: 55ms TTL:170 (bb1-p8-0.crscca.sbcglobal.net ok)
151.164.242.230 RTT: 27ms TTL:170 (ex2-p14-0.eqsjca.sbcglobal.net ok)
151.164.191.201 RTT: 28ms TTL:170 (ex1-p9-0.eqsjca.sbcglobal.net ok)
144.223.242.81 RTT: 41ms TTL:170 (sl-st20-sj-0-0.sprintlink.net ok)
144.232.9.67 RTT: 27ms TTL:170 (sl-st21-sj-1-0.sprintlink.net ok)
144.232.9.206 RTT: 55ms TTL:170 (No rDNS)
12.123.13.193 RTT: 83ms TTL:170 (tbr2-p012201.sffca.ip.att.net bogus rDNS: host not found [authoritative])
12.122.12.114 RTT: 55ms TTL:170 (tbr1-cb10.st6wa.ip.att.net bogus rDNS: host not found [authoritative])
12.123.44.145 RTT: 55ms TTL:170 (gar3-p360.st6wa.ip.att.net bogus rDNS: host not found [authoritative])
12.119.199.22 RTT: 69ms TTL:170 (No rDNS)
68.87.216.6 RTT: 55ms TTL:170 (No rDNS)
68.87.216.57 RTT: 55ms TTL:170 (No rDNS)
* * * failed
67.171.201.211 RTT: 68ms TTL: 41 (Ikuko ok)
I noticed quite a few are posting tracer routes going through Level3. I'd kind of take those with a grain of salt, given the peering wars going on.
I also wonder what will go on with the AT&T routers. With SBC poised to buy AT&T, how long will any peering and transit agreements hold?
Comcast may be adding capacity to take up any slack from the AT&T buyout; who knows? I also have no idea about the affect of Comcast lighting up large swaths of the south S.F. Bay Area. Until about nine months ago, Comcast was not available in my neighborhood. That was when they "lit up" the line behind my house. Black sheath with red stripe; fiber on the poles? Could they have added customers in west San José faster than they added capacity, and are now playing "catch up"?
Just rambling. I was suffering serious DSL lag, and decreased down sync rate; worried that the copper was going bad, and I'd maybe have to go over to Comcast. Now that the cable maintenance guy fixed the open on the "ring" side of the loop, all is well again. Took them 48 hours to fix it, though, because of the "protocol". Service techs have to wave their wands over pole connections and cross-connect boxes before they bring in cable maintenance.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
