Comcast/Sprint Customers

[Skuzzy]

Unfortunately, the switchover to new routers at AT&T (supposed to be more peering) did not help the lousy situation with Comcast and Sprint customers.

At this point, all we can do is start the search for a new ISP.  That will take a bit of time.  A few months, at least.

[Denholm]

Although I don't play. I haven't seen a company trying harder to adapt to its customer's needs. You are a great bunch of people!

[SRD]

Although I don't play. I haven't seen a company trying harder to adapt to its customer's needs. You are a great bunch of people!

Agreed, your efforts are appreciated. 

If it makes you feel any better it seems comcast may be working on their routing.

This used to be my route to the server:


Over the last few days I've been getting this:

[Hawk55]

What Denholm said!      <S> Skuz and the rest of the AH crew.

[Skuzzy]

SRD, the problem is the return trip.

traceroute to 68.86.245.241 (68.86.245.241), 30 hops max, 40 byte packets
 1  206.16.60.46 (206.16.60.46)  0.354 ms  0.284 ms  0.233 ms
 2  mdf001c7613r0001-gig-12-2.dal1.attens.net (63.241.193.13)  0.264 ms  0.278 ms  0.249 ms
 3  gar26.dlstx.ip.att.net (12.122.254.193)  1.224 ms  1.075 ms  1.043 ms
 4  cr2.dlstx.ip.att.net (12.122.138.186)  1.897 ms  1.375 ms  1.357 ms
 5  ggr3.dlstx.ip.att.net (12.122.138.17)  1.192 ms  1.149 ms  1.136 ms
 6  cr2-pos-0-3-3-3.dallas.savvis.net (208.172.139.225)  1.555 ms  1.308 ms  1.401 ms
 7  cr2-tengig-0-7-0-0.losangeles.savvis.net (204.70.196.154)  34.348 ms  34.148 ms  34.188 ms
 8  er2-tengig-3-1.lay.savvis.net (204.70.198.10)  33.835 ms  33.781 ms  33.770 ms
 9  comcast-net.lay.savvis.net (208.172.41.162)  34.638 ms  34.448 ms  34.704 ms
10  pos-0-14-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.142)  35.900 ms  35.769 ms  36.485 ms
11  te-7-2-ar01.dannythomas.tn.malt.comcast.net (68.86.91.206)  45.518 ms  45.504 ms  45.433 ms
12  te-8-1-ur03.jacksonnorth.ms.malt.comcast.net (68.86.240.134)  50.384 ms  50.426 ms  50.687 ms
13  te-9-3-ur02.jacksonnorth.ms.malt.comcast.net (68.86.241.53)  50.562 ms  50.387 ms  50.360 ms
14  te-8-1-ur01.jacksonnorth.ms.malt.comcast.net (68.86.241.9)  50.533 ms  50.423 ms  50.420 ms
15  pos-3-1-ur02.westmonroe.la.malt.comcast.net (68.86.241.34)  53.020 ms  53.021 ms  52.956 ms
16  te-9-1-ur01.monroe.la.malt.comcast.net (68.86.241.202)  53.214 ms *  53.249 ms

See how the packet leaves Dallas, then hits Los Angeles for 3 hops.
Then back to Dallas (hope #10).
Then to Tennessee (hop #11)
Then to Jackson, Mississippi for 3 hops (hop #12, 13, 14)
Then to West Monroe, Louisiana for a hop (15)
Then finally to Monroe, Louisiana.

Those hops in Los Angeles are the killers.  That hub is a very busy hub and is prone to dropping packets during prime time hours.  It impacts all Comcast customers.  Comcast and Savvis will admit it is a problem.  Yet, nothing is being done to correct it.  Savvis has said they have no intention of fixing it.

The only hope we had was for AT&T to get a peering arrangement with Comcast, but that did not happen.

[SRD]

SRD, the problem is the return trip.

Ah, I see.  Well atleast my trip to the server is better now.  I was going all over the place then through savvis in chicago.

[CRYPTIC]

good luck skuzzy. My only choice is comcast or they would have been gone long ago.I will never go back to dial up. I've been told for 3 years DLS is coming soon. funny part is it's right around the corner not even a quarter mile.

[Wizer]

I am not a Comcast/Sprint Customer; My provider is Att.net.  However, I am forwarding my ping plotter for evaluation/comment.

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 6/4/2009 7:44:00 AM to 6/4/2009 7:51:15 AM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    30   0   0.0   0   2   0  home [192.168.1.254]
 2    30   0   0.0  20  24  21  99-13-44-2.lightspeed.bcvloh.sbcglobal.net [99.13.44.2]
 3    27  15  55.6  21  24  21  [75.25.216.72]
 4    28   2   7.1  21  24  22  [75.25.192.64]
 5    30   0   0.0  21  28  21  [75.25.192.2]
 6    30   0   0.0  20 215  34  bb1-g4-0.bcvloh.sbcglobal.net [151.164.241.134]
 7    30  30 100.0   0   0   0   [-]
 8    30   0   0.0  28  80  32  gar3.cgcil.ip.att.net [12.122.79.85]
 9    30   0   0.0  55  59  55  cr2.cgcil.ip.att.net [12.122.132.210]
10    30   0   0.0  55  58  55  cr2.sl9mo.ip.att.net [12.122.2.22]
11    30   0   0.0  55  57  55  cr1.sl9mo.ip.att.net [12.122.2.217]
12    30   0   0.0  55  56  55  cr2.dlstx.ip.att.net [12.122.3.221]
13    30   0   0.0  54 195  68  gar23.dlstx.ip.att.net [12.122.138.161]
14    30   0   0.0  55 253  68  12-122-254-154.attens.net [12.122.254.154]
15    30   0   0.0  55 158  59  mdf001c7613r0003-gig-12-1.dal1.attens.net [63.241.193.22]
16    30   0   0.0  55  56  55  [206.16.60.38]

[Denholm]

Call AT&T pointing them to this thread. See if a Tier 2 support guy will look at your ping-plot. Looks like hops 3 and 7 are your trouble-makers. I'm going to run a trace to 99.13.44.2 to see how the return trip looks from south Dallas, it might reveal something else.

EDIT: So much for that, I can't even reach you...

Target Name: 99-13-44-2.lightspeed.bcvloh.sbcglobal.net
         IP: 99.13.44.2
  Date/Time: 6/4/2009 2:47:21 PM to 6/4/2009 2:48:01 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    19   0   0.0   0   1   0  home [192.168.1.254]
 2    19   0   0.0  46  76  50  ppp-xx-xxx-xxx-xxx.dsl.rcsntx.swbell.net [xx.xxx.xxx.xxx]
 3    19   0   0.0  47  60  49  dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
 4    19   0   0.0  46  56  49  [151.164.93.188]
 5    19   0   0.0  77 358  98  [12.83.61.133]
 6    18  18 100.0   0   0   0   [-]
 7    18  18 100.0   0   0   0   [-]
 8    18  18 100.0   0   0   0   [-]
 9    18  18 100.0   0   0   0   [-]
10    18  18 100.0   0   0   0   [-]
11    18  18 100.0   0   0   0   [-]
12    18  18 100.0   0   0   0   [-]
13    18  18 100.0   0   0   0   [-]
14    18  18 100.0   0   0   0   [-]
15    18  18 100.0   0   0   0   [-]
16    18  18 100.0   0   0   0   [-]
17    18  18 100.0   0   0   0   [-]
18    18  18 100.0   0   0   0   [-]
19    18  18 100.0   0   0   0   [-]
20    18  18 100.0   0   0   0   [-]
21    18  18 100.0   0   0   0   [-]
22    18  18 100.0   0   0   0   [-]
23    18  18 100.0   0   0   0   [-]
24    18  18 100.0   0   0   0   [-]
25    18  18 100.0   0   0   0   [-]
26    18  18 100.0   0   0   0   [-]
27    18  18 100.0   0   0   0   [-]
28    18  18 100.0   0   0   0   [-]
29    18  18 100.0   0   0   0   [-]
30    18  18 100.0   0   0   0   [-]
31    18  18 100.0   0   0   0   [-]
32    18  18 100.0   0   0   0   [-]
33    18  18 100.0   0   0   0   [-]
34    18  18 100.0   0   0   0   [-]
35    18  18 100.0   0   0   0   [-]

Destination not reached in 35 hops