US Cable Support > Comcast HSI > Routing Issues Today ?

Routing Issues Today ?

No, haven't seen any issues out here on the Left Coast.

I haven't noticed any connectivity problems here in the mid south either. I do see a similar lack of ICMP echo replies to cnn.com and comcast.net that you do, but I have no difficulty actually connecting to the web sites.

These days, with so many routers and servers giving extremely low priority to ICMP probes (or even ignoring them entirely unless done from specific IP addresses in an ACL), both ping and traceroute have become almost useless as a general Internet troubleshooting tool.

C:\>tracert cnn.com
 
Tracing route to cnn.com [157.166.226.25]
over a maximum of 30 hops:
 
  1    38 ms    29 ms    29 ms  174.49.8.1
  2     9 ms     9 ms     7 ms  xe-4-0-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
  3    11 ms    12 ms    10 ms  xe-2-1-1-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.53]
  4    20 ms    17 ms    20 ms  68.86.90.101
  5    19 ms    82 ms    23 ms  4.28.24.73
  6    47 ms    60 ms    46 ms  ae-2-52.edge4.Atlanta2.Level3.net [4.69.150.77]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10  ^C
C:\>tracert comcast.net
 
Tracing route to comcast.net [207.223.8.109]
over a maximum of 30 hops:
 
  1    36 ms    29 ms    22 ms  174.49.8.1
  2    10 ms     9 ms    10 ms  xe-4-0-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
  3    11 ms    10 ms    11 ms  xe-5-1-3-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105]
  4    20 ms    19 ms    19 ms  68.86.90.181
  5    41 ms    35 ms    35 ms  he-0-7-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.89.165]
  6    35 ms    35 ms    35 ms  te-1-1-pe01.philadelphia.pa.ibone.comcast.net [68.86.84.178]
  7    37 ms    35 ms    36 ms  75.149.230.250
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11  ^C
 
 

reply to Oregonian
Not really in New England but I have had an issue with
he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net

with a pretty decent latency jump since getting service. It's not that noticeable though.

Tracing route to Comcast.net [76.96.39.101]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 8 ms 7 ms 7 ms
3 7 ms 7 ms 7 ms
4 10 ms 10 ms 12 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
5 14 ms 15 ms 15 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.69]
6 48 ms 47 ms 47 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
7 51 ms 47 ms 47 ms 68.86.88.134
8 51 ms 47 ms 47 ms 68.86.88.21
9 68 ms 66 ms 67 ms pos-1-8-0-0-cr01.denver.co.ibone.comcast.net [68.86.87.222]
10 66 ms 67 ms 67 ms te-4-1-ar01.potomac.co.ndcwest.comcast.net [68.86.91.10]
11 68 ms 67 ms 67 ms 68.86.206.114
12 * * * Request timed out.
13 * * * Request timed out.
14 * *

reply to ExoticFish
The problems seem to have subsided now. *Knock on wood*
--
»www.VAJeeps.com

reply to NetFixer