Comcast user connection issues

[DakOne]

I've got Embarq DSL and am getting the same Disco issues about every 15 minutes from sign on.

[rainnman]

Just food for thought.  I am using pingplotter and just did a check on the system and found that my first 10 hops which are mainly comcast or level 3 were all in the green working just fine.  Hops 11 thru 19 which are all att were yellow or red and losing packets.  Seems to me at least today the culprit is att not comcast.

[skopro]

Mine started going crazy starting the 1st of dec.Normally i would have a 32 ping to the server,but it was at 117,ran ping plotter and found ridiculous amounts of PL.Has gotten alot better and haven't really had any major issues but thought i would post my results




Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 9:10:17 PM to 12/19/2008 9:10:26 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.1.1]
 2    7 ms    7 ms    9 ms   10 ms    8 ms    8 ms    7 ms   12 ms   15 ms    8 ms  [96.169.36.1]
 3    8 ms    7 ms    7 ms   13 ms   16 ms    8 ms    6 ms   12 ms   12 ms    8 ms  ge-4-13-ur01.arvada.co.denver.comcast.net [68.85.220.61]
 4    8 ms    8 ms   10 ms   10 ms   10 ms    9 ms    9 ms   12 ms   15 ms    9 ms  te-9-1-ur02.arvada.co.denver.comcast.net [68.86.103.126]
 5    8 ms    9 ms   10 ms    9 ms   10 ms    8 ms    8 ms   16 ms   12 ms    9 ms  te-8-2-ar01.aurora.co.denver.comcast.net [68.86.103.41]
 6    9 ms   10 ms   13 ms   11 ms   11 ms   10 ms    9 ms   12 ms   12 ms   11 ms  te-0-4-0-0-cr01.denver.co.ibone.comcast.net [68.86.91.1]
 7   15 ms   10 ms   12 ms   10 ms  194 ms  194 ms   67 ms  142 ms   *        9 ms  te-4-3.car2.Denver1.Level3.net [4.79.82.53]
 8    9 ms   18 ms   14 ms   22 ms   17 ms   12 ms   *       12 ms   24 ms   18 ms  ae-32-54.ebr2.Denver1.Level3.net [4.68.107.126]
 9   15 ms   10 ms   23 ms   12 ms   13 ms   20 ms   10 ms   23 ms   16 ms   10 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
10   26 ms   36 ms   29 ms   26 ms   35 ms   28 ms   38 ms   *       28 ms   34 ms  ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11   32 ms   25 ms   36 ms   29 ms   *       *       27 ms   37 ms   30 ms   28 ms  ae-92-92.csw4.Dallas1.Level3.net [4.69.136.150]
12   24 ms   25 ms   25 ms   27 ms   28 ms   26 ms   28 ms   22 ms   78 ms   25 ms  ae-4-99.edge2.Dallas3.Level3.net [4.68.19.204]
13   53 ms   52 ms   52 ms   53 ms   54 ms   51 ms   51 ms   52 ms   54 ms   51 ms  [192.205.35.225]
14   55 ms   55 ms   54 ms   66 ms   56 ms   55 ms   56 ms   55 ms   55 ms   54 ms  tbr1.dlstx.ip.att.net [12.123.16.202]
15   57 ms   54 ms   55 ms   57 ms   56 ms   53 ms   56 ms   57 ms   55 ms   54 ms  cr1.dlstx.ip.att.net [12.122.18.145]
16   66 ms   52 ms   50 ms   54 ms   53 ms   51 ms   *       52 ms   51 ms  N/A     gar5.dlstx.ip.att.net [12.122.139.5]
17   55 ms   52 ms   55 ms   58 ms   56 ms   54 ms   57 ms   56 ms   55 ms  N/A     mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
18   59 ms   *       54 ms   56 ms   56 ms   53 ms   56 ms   56 ms   53 ms  N/A     mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]
19   56 ms   52 ms   54 ms   57 ms   57 ms   52 ms   56 ms   54 ms   52 ms  N/A     [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 52ms, Maximum = 57ms, Average = 54ms

[StokesAk]

Its Fixed        I can now play in all the arena without discoing evry second <<<<<<S>>>>>> Skuzzy thgank You for all the Help.

[ROC]

For comparison, I have not noticed any issues, Sacramento CA, Wavecable (used to be Charter)
If you need to show anyone that others are not having issues.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms    10 ms     9 ms  10.15.0.1
  3     8 ms    14 ms     9 ms  172.29.120.2
  4    11 ms    12 ms    11 ms  hrsp.rk.wavecable.com [76.14.96.1]
  5    16 ms    16 ms    14 ms  66.239.40.49.ptr.us.xo.net [66.239.40.49]
  6    16 ms    16 ms    16 ms  p3-0-0d0.mar2.roseville-ca.us.xo.net [207.88.80.
77]
  7    16 ms    15 ms    16 ms  p3-0-0d0.rar2.sanjose-ca.us.xo.net [65.106.5.209
]
  8    29 ms    30 ms    30 ms  207.88.12.181.ptr.us.xo.net [207.88.12.181]
  9    24 ms    28 ms    28 ms  207.88.12.182.ptr.us.xo.net [207.88.12.182]
 10    24 ms    25 ms    29 ms  206.111.12.146.ptr.us.xo.net [206.111.12.146]
 11    71 ms    70 ms    73 ms  tbr2.sffca.ip.att.net [12.123.13.70]
 12    65 ms    66 ms    66 ms  cr2.sffca.ip.att.net [12.122.19.77]
 13    61 ms    60 ms    61 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 14    72 ms    72 ms    68 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 15    65 ms    63 ms    61 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    60 ms    62 ms    60 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 17    61 ms   518 ms    64 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    71 ms    65 ms    69 ms  206.16.60.38

Trace complete.


Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    10 ms     8 ms     9 ms  10.15.0.1
  3    12 ms    11 ms     9 ms  172.29.120.2
  4    13 ms    11 ms    13 ms  hrsp.rk.wavecable.com [76.14.96.1]
  5    20 ms    21 ms    30 ms  66.239.40.49.ptr.us.xo.net [66.239.40.49]
  6    15 ms    16 ms    16 ms  p3-0-0d0.mar2.roseville-ca.us.xo.net [207.88.80.
77]
  7    26 ms    27 ms    25 ms  p3-0-0d0.rar2.sanjose-ca.us.xo.net [65.106.5.209
]
  8    23 ms    24 ms    22 ms  207.88.12.181.ptr.us.xo.net [207.88.12.181]
  9    18 ms    18 ms    17 ms  207.88.12.182.ptr.us.xo.net [207.88.12.182]
 10    27 ms    28 ms    24 ms  206.111.12.146.ptr.us.xo.net [206.111.12.146]
 11    65 ms    69 ms    69 ms  tbr2.sffca.ip.att.net [12.123.13.70]
 12    61 ms    60 ms    60 ms  cr2.sffca.ip.att.net [12.122.19.77]
 13    64 ms    60 ms    60 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 14    64 ms    62 ms    63 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 15    63 ms    63 ms    62 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    61 ms    62 ms    64 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 17    62 ms    61 ms    59 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    61 ms    60 ms    64 ms  206.16.60.38

Trace complete.


Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     9 ms     9 ms  10.15.0.1
  3    10 ms     9 ms     9 ms  172.29.120.2
  4    13 ms    11 ms    11 ms  hrsp.rk.wavecable.com [76.14.96.1]
  5    13 ms    14 ms    14 ms  66.239.40.49.ptr.us.xo.net [66.239.40.49]
  6    21 ms    20 ms    19 ms  p3-0-0d0.mar2.roseville-ca.us.xo.net [207.88.80.
77]
  7    19 ms    14 ms    15 ms  p3-0-0d0.rar2.sanjose-ca.us.xo.net [65.106.5.209
]
  8    16 ms    19 ms    15 ms  207.88.12.181.ptr.us.xo.net [207.88.12.181]
  9    14 ms    16 ms    17 ms  207.88.12.182.ptr.us.xo.net [207.88.12.182]
 10    17 ms    17 ms    17 ms  206.111.12.146.ptr.us.xo.net [206.111.12.146]
 11    59 ms    59 ms    69 ms  tbr2.sffca.ip.att.net [12.123.13.70]
 12    59 ms    62 ms    66 ms  cr2.sffca.ip.att.net [12.122.19.77]
 13    60 ms    60 ms    61 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 14    66 ms    69 ms    66 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 15    61 ms    57 ms    58 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    59 ms    60 ms    61 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 17    63 ms    62 ms    60 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    59 ms    59 ms    58 ms  206.16.60.38

Trace complete.

[kvuo75]

I'm guessing they won't be calling me back within 24 hours then.   

no probs since 7pm my time -- about an hour before FSO time..

[HighGTrn]

You think this could have anything to do with our problem?

http://www.networkworld.com/news/2008/121908-undersea-cable-cuts-disrupt-internet.html

[Sincraft]

Skuzzy : Here is my info.  My hops to level 3 are GREAT but after that...
After running a ping plot my worst area is at the last 2 hops on your end.  I have ZERO packet loss OMG.  Far cry from the well overloaded routers just 30 miles to the east where I used to live.  I'm happy with it but the ping times and hops could be better. 

Anyway - here are my tracert results.

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1   xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

  2    xxxxxxxxxxxxxxxxxxxxxxxxxx
  3    12 ms     9 ms     9 ms  ge-2-1-ur01.mckeesport.pa.pitt.comcast.net [68.8
6.102.241]
  4     9 ms     8 ms     9 ms  te-8-3-ar01.mckeesport.pa.pitt.comcast.net [68.8
6.100.45]
  5    16 ms    13 ms    14 ms  te-0-4-0-0-cr01.pittsburgh.pa.ibone.comcast.net
[68.86.90.101]
  6    14 ms    15 ms    14 ms  xe-8-0-0.edge1.Washington1.Level3.net [4.79.20.1
7]
  7    16 ms    16 ms    14 ms  ae-4-99.edge1.Washington3.Level3.net [4.68.17.20
3]
  8    15 ms    17 ms    15 ms  att-level3-oc192.Washington1.Level3.net [209.244
.219.142]
  9    86 ms    88 ms    87 ms  tbr2.wswdc.ip.att.net [12.123.8.118]
 10    86 ms    87 ms    87 ms  cr2.wswdc.ip.att.net [12.122.16.85]
 11    86 ms    87 ms    88 ms  cr1.attga.ip.att.net [12.122.1.173]
 12    87 ms    86 ms    88 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 13    87 ms    87 ms    85 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 14    86 ms    86 ms    86 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 15    87 ms    88 ms    89 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.
46]
 16    89 ms    87 ms    86 ms  206.16.60.38

Trace complete.

[drdeathx]

I'm guessing they won't be calling me back within 24 hours then.   

Called Comcast.Told Tech to make a report seeing he said they were probably aware of it. I replied if all you techs say this I  bet no report has been made! Boom, up in running 1 hour later!!!

DRDEATH you truely rock!

 

[Skuzzy]

The problem was a routing issue between Comcast and AT&T.  At one point no one on Comcasts's network could reach any site in AT&T's network.  Bad routes injected into the Level3 network were aggravating the problem.  Someone, somewhere fat-fingered the routing tables.

There may have been one other ISP involved who actually caused the problem.

Getting this fixed is not going to solve the overall problem with Level3's network being oversold.

[VonMessa]

At least I was OK for FSO 

And now we know the proper way to rattle their cage. 

[Paladin3]

Once again Skuzzy, MAJOR points for the help you gave me. Much appriciated sir. 

[Wayout]

From the Detroit area.

[Max]

<--- sent an e-mail to Obama this morning suggesting the creation of a Cabinet Level post: Internet Czar,

Skuzzy I hope you don't mind me mentioning your name 

[TankBstr]

Write Al Gore and complain to him. He invented the damn thing.