How Sad
@attbi.co
| Comcast of ATLANTA, SHAMEFUL!!!!!
This thread and its contents are directed and meant to be seen by any Comcast employees in the Georgia area that peruse these boards and HAVE THE POWER TO FIX OUR PROBLEM.
OUR PROBLEM: (OUR MEANS US ATLANTANS -- MAYBE MORE OF US)
Every now and then we have a ping problem. At least, that's the name we've given it. I call it PING HELL. Here is a trace route showing it to you:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\>tracert www.google.com
Tracing route to www.google.com [216.239.39.99]
over a maximum of 30 hops:
1 59 ms 37 ms 45 ms 10.238.136.1
2 19 ms 28 ms 10 ms c-66-56-22-74.atl.client2.attbi.com [66.56.22.74
]
3 12 ms 49 ms 12 ms c-66-56-23-46.atl.client2.attbi.com [66.56.23.46
]
4 31 ms 67 ms 12 ms c-66-56-66-10.atl.client2.attbi.com [66.56.66.10
]
5 426 ms 454 ms 428 ms 12.124.58.41
6 432 ms 432 ms 417 ms gbr5-p80.attga.ip.att.net [12.123.21.74]
7 404 ms 403 ms 411 ms tbr1-p013501.attga.ip.att.net [12.122.12.21]
8 441 ms 430 ms 433 ms ggr1-p340.attga.ip.att.net [12.122.12.30]
As you can see it all starts here:
5 426 ms 454 ms 428 ms 12.124.58.41
This makes surfing the internet mighty slow. Dial-up has better latency. How can you $#@$# sell us this $#$#$ for $50+ a month? You all (comcast) have no excuse for not fixing this problem yet. I say YET because us "atlantans" have been documenting this SAME issue since LAST YEAR.
DO SOMETHING FOR US. ACTIONS SPEAK LOUDER than your customer service rep's constant "have you powercycled?"
I'm glad I have vented....
The below opinions (which will follow) are those of other "atlantans" having problems...
Geez, this is Atlanta. Imagine Comcast selling this $#$# to us. AND IT HAS BEEN GOING ON FOR OVER **1 YEAR**
And yes, I've called customer support, I've had technicians dispatched out here to waste my time and your money, and I've spoken to Tom Ringkamp (yeah, now you know how far I've gone). It's too bad you all (Comcast of Georgia) have sent off the hard-working employees like Veree Freeman out of Georgia. It's a shame. |
|
Kett2000
Kett2000
join:2002-04-23
Atlanta, GA
clubs:
| I have the same problem and have sent an email to the At&t Backbone Network Technicians since they are in charge of the router with ip address 12.124.58.41. Send them an email with a few traceroutes of the problem as well as some pings. If enough people email them and bug them they will hopefully get the idea and fix the problem. The email is help@ip.att.net .
Thanks for the suggestion Big_D.
Here is a sample of a traceroute I just took:
Tracing route to yahoo.com [66.218.71.198]
over a maximum of 30 hops:
1 43 ms 11 ms 12 ms 10.238.208.1
2 13 ms 12 ms 10 ms c-66-56-67-82.atl.client2.attbi.com [66.56.67.82
]
3 11 ms 23 ms 11 ms c-66-56-23-46.atl.client2.attbi.com [66.56.23.46
]
4 12 ms 11 ms 11 ms c-66-56-66-10.atl.client2.attbi.com [66.56.66.10
]
5 436 ms 457 ms 443 ms 12.124.58.41
6 435 ms 433 ms 434 ms gbr6-p80.attga.ip.att.net [12.123.21.78]
7 446 ms 441 ms 435 ms tbr1-p013601.attga.ip.att.net [12.122.12.25]
8 459 ms 459 ms 465 ms tbr2-p013801.wswdc.ip.att.net [12.122.10.69] |
|
UNGAgruntgrunt
| reply to How Sad
I'm not sure, but I'll check with my tier here in SAV.. If the transfer from the AT&T crap has been yanked and replaced with the upgrade... I would figure that ATL would be first on the list... here in SAV we aswell use an AT&T backbone that traveles via ATL but no problems here EVER on high pings.... but I WILL check up on it for ya... not sure if I can come up with something or not... we'll see... |
|
UNGAgruntgrunt
| reply to How Sad
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\>tracert www.yahoo.com
Tracing route to www.yahoo.akadns.net [216.109.125.75]
over a maximum of 30 hops:
1 11 ms 8 ms 7 ms 10.171.152.1
2 11 ms 8 ms 8 ms 172.30.78.81
3 15 ms 16 ms 18 ms 12.124.58.45 ----- right here is the POP entrance for us... where you are haveing problems..!!
4 16 ms 23 ms 16 ms gbr6-p80.attga.ip.att.net [12.123.21.78]
5 17 ms 18 ms 18 ms tbr2-p013601.attga.ip.att.net [12.122.12.45]
6 15 ms 15 ms 16 ms ggr1-p370.attga.ip.att.net [12.123.20.253]
7 17 ms 15 ms 16 ms att-gw.atl.cw.net [192.205.32.126]
8 15 ms 15 ms 17 ms agr3-loopback.Atlanta.cw.net [208.172.66.103]
9 17 ms 15 ms 15 ms dcr1-so-0-2-0.Atlanta.cw.net [208.172.75.9]
10 30 ms 29 ms 30 ms dcr2-loopback.Washington.cw.net [206.24.226.100]
11 33 ms 31 ms 32 ms bhr1-pos-10-0.Sterling1dc2.cw.net [206.24.238.16
6]
12 31 ms 31 ms 32 ms csr11-ve241.Sterling2dc3.cw.net [216.109.66.90]
13 31 ms 32 ms 31 ms 216.109.84.162
14 33 ms 32 ms 31 ms vl30.bas1-m.dcn.yahoo.com [216.109.120.142]
15 33 ms 31 ms 31 ms w2.www.dcn.yahoo.com [216.109.125.75]
Trace complete
Looks like it's a router(gateway) issue up there... we go thru the same backbone... funny that it was not picked up by now thou... hmmmm... This is on a Comcast PRO account.. (386 upstream / 3.5 downstream) |
|
zep
join:2002-11-10
Alpharetta, GA
| reply to How Sad
Tracing route to www.google.com [216.239.39.99]
over a maximum of 30 hops:
1 10 ms 30 ms 10 ms 10.239.80.1
2 10 ms 10 ms 30 ms c-66-56-67-157.atl.client2.attbi.com [66.56.67.1
57]
3 10 ms 40 ms 10 ms c-66-56-67-126.atl.client2.attbi.com [66.56.67.1
26]
4 10 ms 10 ms 10 ms c-66-56-23-38.atl.client2.attbi.com [66.56.23.38
]
5 10 ms 10 ms 10 ms c-66-56-22-146.atl.client2.attbi.com [66.56.22.1
46]
6 461 ms 471 ms 490 ms 12.118.184.41
7 460 ms 501 ms 471 ms gbr2-p70.attga.ip.att.net [12.123.21.6]
8 461 ms 471 ms 470 ms tbr1-p013602.attga.ip.att.net [12.122.12.17]
9 461 ms 470 ms 481 ms ggr1-p360.attga.ip.att.net [12.123.20.249]
10 480 ms 451 ms 441 ms acr2-so-3-0-0.Atlanta.cw.net [208.172.65.121]
11 471 ms 470 ms 471 ms agr4-loopback.Atlanta.cw.net [208.172.66.104]
12 450 ms 451 ms 481 ms dcr2-so-1-3-0.Atlanta.cw.net [208.172.75.157]
13 471 ms 480 ms 471 ms dcr2-loopback.Washington.cw.net [206.24.226.100]
14 480 ms 481 ms 471 ms bhr1-pos-10-0.Sterling1dc2.cw.net [206.24.238.16
6]
15 471 ms 471 ms 480 ms csr11-ve241.Sterling2dc3.cw.net [216.109.66.90]
16 481 ms 480 ms 491 ms 218-google-exodusdc.exodus.net [216.109.88.218]
17 471 ms 481 ms 491 ms 216.239.47.46
18 491 ms 490 ms 481 ms 216.239.39.99
Trace complete.
Tracing route to www.comcast.com [164.109.28.3]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 10.239.80.1
2 10 ms 10 ms 10 ms c-66-56-67-157.atl.client2.attbi.com [66.56.67.1
57]
3 10 ms 10 ms 10 ms c-66-56-67-126.atl.client2.attbi.com [66.56.67.1
26]
4 10 ms 11 ms 10 ms c-66-56-23-38.atl.client2.attbi.com [66.56.23.38
]
5 10 ms 10 ms 10 ms c-66-56-22-146.atl.client2.attbi.com [66.56.22.1
46]
6 460 ms 461 ms 431 ms 12.118.184.41
7 421 ms 440 ms 431 ms gbr1-p70.attga.ip.att.net [12.123.21.2]
8 430 ms 441 ms 450 ms tbr1-p013502.attga.ip.att.net [12.122.12.13]
9 471 ms 470 ms 451 ms ggr1-p340.attga.ip.att.net [12.122.12.30]
10 451 ms 461 ms 460 ms att-gw.atl.uu.net [192.205.32.130]
11 451 ms 440 ms 441 ms 0.so-2-3-0.XL2.ATL5.ALTER.NET [152.63.82.194]
12 451 ms 451 ms 450 ms 0.so-0-0-0.TL2.ATL5.ALTER.NET [152.63.10.106]
13 480 ms 491 ms 511 ms 0.so-7-0-0.TL2.DCA6.ALTER.NET [152.63.146.42]
14 451 ms 461 ms 460 ms 0.so-6-0-0.XL2.DCA6.ALTER.NET [152.63.38.74]
15 480 ms 501 ms 481 ms 0.so-7-0-0.GW6.DCA6.ALTER.NET [152.63.41.225]
16 481 ms 471 ms 460 ms digex-gw.customer.alter.net [157.130.214.102]
17 480 ms 491 ms 481 ms vlan39.dca2a-fdisa-sw1-msfc1.netsrv.digex.com [1
64.109.3.149]
18 471 ms 491 ms 621 ms 164.109.28.3
Trace complete.
Tracing route to www.attbi.com [204.127.202.8]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 10.239.80.1
2 10 ms 10 ms 40 ms c-66-56-67-157.atl.client2.attbi.com [66.56.67.1
57]
3 10 ms 10 ms 10 ms c-66-56-67-126.atl.client2.attbi.com [66.56.67.1
26]
4 10 ms 10 ms 10 ms c-66-56-23-46.atl.client2.attbi.com [66.56.23.46
]
5 10 ms 10 ms 20 ms c-66-56-23-38.atl.client2.attbi.com [66.56.23.38
]
6 10 ms 10 ms 10 ms c-66-56-22-146.atl.client2.attbi.com [66.56.22.1
46]
7 450 ms 471 ms 471 ms 12.244.72.89
8 451 ms 461 ms 460 ms gbr2-p70.attga.ip.att.net [12.123.21.6]
9 470 ms 471 ms 501 ms tbr1-p013602.attga.ip.att.net [12.122.12.17]
10 461 ms 461 ms 470 ms tbr2-p013801.wswdc.ip.att.net [12.122.10.69]
11 490 ms 481 ms 481 ms tbr1-p013701.n54ny.ip.att.net [12.122.10.53]
12 481 ms 491 ms 490 ms gbr2-p20.n54ny.ip.att.net [12.122.11.22]
13 461 ms 480 ms 471 ms gar1-p370.n54ny.ip.att.net [12.123.1.133]
14 481 ms 491 ms 480 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255
.162]
15 491 ms 491 ms 500 ms sccsbix12-1-4.attbi.com [63.240.64.46]
16 490 ms 491 ms 491 ms 192.168.201.5
17 470 ms 481 ms 491 ms www.attbi.com [204.127.202.8]
Trace complete. |
|
ki1o
Premium
join:2001-04-12
Atlanta, GA
| reply to How Sad
I've been having this problem for over 3 weeks already. Today is the worst so far with pings in the 400. 3 weeks ago I opened a ticket number and 1 week later the script readers techs said it was a problem on my end. I called Robin who works at the customer advocacy team 3 different times 3 weeks apart before she would call me back. I got her number after I complained to the BBB back in December of last year of a similar ping problem. After the second time of her not calling me back, I complained to the BBB and the Dekalb County Franchise Authority and a week later I called Robin back and she returned my call. She told me to send an email to someone at Comcast and then a lady who works at Comcast from Canada called me and told me to send an email to another address. Anyway to make a long story short, it took 3 weeks of non stop complaining to the people I mentioned above before the idiots at Comcast would admit their was a problem. If you haven't called tech support at 1-866-447-7333 or chatted with them at help.broadband.att.com already, please do. Also, mention this ticket number 2832372 and my attbi user name st3ph3n2 and tell them you are having the same problem as me. (I don't use this email address at all, so if any of you low life spammers decide to spam me, it won't bother me any) Also mention this forum web link. The techs are admitting that their is a problem, but if more people complain, than it might make Comcast fix this problem faster.
--
Boycott The RIAA |
|
Holyearth
I Like This Forum
join:2002-07-18
Atlanta, GA
|  Dial up works better COMCAST. What an excuse for POOR service. How long will this go on? What kind of employees here in Georgia are you employing? @!#%^$#
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\>ping google.com
Pinging google.com [216.239.53.100] with 32 bytes of data:
Reply from 216.239.53.100: bytes=32 time=543ms TTL=46
Reply from 216.239.53.100: bytes=32 time=546ms TTL=46
Reply from 216.239.53.100: bytes=32 time=528ms TTL=46
Reply from 216.239.53.100: bytes=32 time=525ms TTL=46
Ping statistics for 216.239.53.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 525ms, Maximum = 546ms, Average = 535ms |
|
JTRockville
Data Ho
Premium,MVM
join:2002-01-28
Rockville, MD
clubs:
 ·LINGO
 ·Sprint Mobile Broa..
 ·surpasshosting
 ·Verizon FIOS
| reply to ki1o
ki1o  , where did you find contact information for the Dekalb County Franchise Authority? Maybe you could post it here so others can follow your lead.
Did you ask for credit until the problem is fixed? |
|
Big_D
Premium
join:2003-06-02
Augusta, GA
| reply to Holyearth
said by Holyearth :
Dial up works better COMCAST. What an excuse for POOR service. How long will this go on? What kind of employees here in Georgia are you employing? @!#%^$#
It's not really fair to bash comcast so harshly when your ping problems start at the router owned by AT&T worldnet services. Try sending them an email. help@ip.att.net Hopefully if enough people send them complaints they will look into the problem and do something about it.
--
You want the truth? You can't handle the truth! |
|
ki1o
Premium
join:2001-04-12
Atlanta, GA
| reply to JTRockville
said by JTRockville :
ki1o , where did you find contact information for the Dekalb County Franchise Authority? Maybe you could post it here so others can follow your lead.
Did you ask for credit until the problem is fixed?
I looked on my cable bill and it said my Local Franchise Authority was the Dekalb County Commission (I think) I went to an online phone book and looked up that place. They said they don't handle complaints and connected me to the main switch board. Then the operator connected me to another department, and that department gave me the phone number just for cable complaints. Also, I found this website »clarkhoward.com/library/rolodex_···ion.html that has the phone number for other county cable complaints. The number Dekalb County gave me was different than the number on that website, but I think both of those numbers for Dekalb County connect you to the same place.
EDIT I did ask for a credit to one of the tech support people, he said he would forward it to the accounting department and 1 week later after I asked, I didn't receive the credit. Back in December with the last ping problem, tech support wouldn't give me a credit either. As long as I can surf, they won't give me a credit. I guess I can always unplug my modem and call support and tell them I can't get online  .
--
Boycott The RIAA
[text was edited by author 2003-06-25 22:53:38] |
|
ki1o
Premium
join:2001-04-12
Atlanta, GA
| reply to Big_D
said by Big_D :
It's not really fair to bash comcast so harshly when your ping problems start at the router owned by AT&T worldnet services. Try sending them an email. help@ip.att.net Hopefully if enough people send them complaints they will look into the problem and do something about it.
We are still on the AT&T network. Also, every one in Atlanta had this same problem back in December and after 2 weeks of complaining to tech support and the BBB, they finally fixed it. Also, when the Canadian woman called me back, when she saw my tracerts from my first email I sent her, she admitted their was a problem on Comcasts network. So one way or another, that router must be owned by AT&T Broadband/Comcast.
--
Boycott The RIAA |
|
Big_D
Premium
join:2003-06-02
Augusta, GA
| said by ki1o :
said by Big_D :
It's not really fair to bash comcast so harshly when your ping problems start at the router owned by AT&T worldnet services. Try sending them an email. help@ip.att.net Hopefully if enough people send them complaints they will look into the problem and do something about it.
We are still on the AT&T network. Also, every one in Atlanta had this same problem back in December and after 2 weeks of complaining to tech support and the BBB, they finally fixed it. Also, when the Canadian woman called me back, when she saw my tracerts from my first email I sent her, she admitted their was a problem on Comcasts network. So one way or another, that router must be owned by AT&T Broadband/Comcast.
Thats where your mistaken AT&T worldnet services is not owned by comcast. Only the broadband operations were sold to comcast. any router with a 12.x.x.x address is still owned by AT&T worldnet. Here is a whois on that router
OrgName: AT&T WorldNet Services
OrgID: ATTW
Address: 400 Interpace Parkway
City: Parsippany
StateProv: NJ
PostalCode: 07054
Country: US
NetRange: 12.0.0.0 - 12.255.255.255
CIDR: 12.0.0.0/8
NetName: ATT
NetHandle: NET-12-0-0-0-1
Parent:
NetType: Direct Allocation
NameServer: DBRU.BR.NS.ELS-GMS.ATT.NET
NameServer: DMTU.MT.NS.ELS-GMS.ATT.NET
NameServer: CBRU.BR.NS.ELS-GMS.ATT.NET
NameServer: CMTU.MT.NS.ELS-GMS.ATT.NET
Comment: For abuse issues contact abuse@att.net
RegDate: 1983-08-23
Updated: 2002-08-23
TechHandle: DK71-ARIN
TechName: Kostick, Deirdre
TechPhone: +1-919-319-8249
TechEmail: help@ip.att.net
OrgAbuseHandle: ATTAB-ARIN
OrgAbuseName: ATT Abuse
OrgAbusePhone: +1-919-319-8130
OrgAbuseEmail: abuse@att.net
OrgTechHandle: ICC-ARIN
OrgTechName: IP Customer Care
OrgTechPhone: +1-888-613-6330
OrgTechEmail: qhoang@att.com
OrgTechHandle: IPSWI-ARIN
OrgTechName: IP SWIP
OrgTechPhone: +1-888-613-6330
OrgTechEmail: swipid@nipaweb.vip.att.net
# ARIN WHOIS database, last updated 2003-06-24 21:05
# Enter ? for additional hints on searching ARIN's WHOIS database.
--
You want the truth? You can't handle the truth! |
|
IanJKorman
join:2003-06-18
Ypsilanti, MI |  reply to How Sad
Probably all the techs are northerners. I guess you should just be happy the worst thing they are doing is messing up your HSI. I wouldn't get them any angrier or they just might burn your city to the ground for a second time. |
|
JTRockville
Data Ho
Premium,MVM
join:2002-01-28
Rockville, MD
clubs:
·LINGO
·Sprint Mobile Broa..
·surpasshosting
·Verizon FIOS
| reply to Big_D
said by Big_D :
It's not really fair to bash comcast so harshly when your ping problems start at the router owned by AT&T worldnet services.
Oh really? When you signed up for service, were you asked which backbone you wanted to connect to?
Comcast (NOT the subscriber) contracts for the backbone. It most certainly IS their responsibility to see that their contracted services are performing properly! |
|
toasterhead1
Toasterhead
join:2002-07-01
Norcross, GA
clubs:
| Tracing route to www.yahoo.akadns.net [216.109.125.76]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 11 ms 69 ms 10 ms 10.238.252.1
3 16 ms 9 ms 9 ms c-66-56-66-2.atl.client2.attbi.com [66.56.66.2]
4 11 ms 13 ms 12 ms c-66-56-23-38.atl.client2.attbi.com [66.56.23.38
]
5 13 ms 13 ms 10 ms c-66-56-22-146.atl.client2.attbi.com [66.56.22.1
46]
6 465 ms 472 ms 476 ms 12.118.184.41
7 467 ms 453 ms 466 ms gbr2-p70.attga.ip.att.net [12.123.21.6]
8 465 ms 475 ms 477 ms tbr1-p013602.attga.ip.att.net [12.122.12.17]
9 456 ms 493 ms 469 ms ggr1-p340.attga.ip.att.net [12.122.12.30]
10 479 ms 479 ms 470 ms acr2-so-3-0-0.Atlanta.cw.net [208.172.65.121]
11 477 ms 467 ms 491 ms agr3-loopback.Atlanta.cw.net [208.172.66.103]
12 473 ms 471 ms 475 ms dcr1-so-0-2-0.Atlanta.cw.net [208.172.75.9] |
|
toasterhead1
Toasterhead
join:2002-07-01
Norcross, GA
clubs: | BTW its funny because today I got an email asking me to close my BBB complaint with comcast from comcast =P HA! |
|
JTRockville
Data Ho
Premium,MVM
join:2002-01-28
Rockville, MD
clubs: | CALL Comcast, and tell them as soon as you can connect to the BBB, you'll close your complaint! |
|
Big_D
Premium
join:2003-06-02
Augusta, GA
| reply to JTRockville
said by JTRockville :
Oh really? When you signed up for service, were you asked which backbone you wanted to connect to?
Comcast (NOT the subscriber) contracts for the backbone. It most certainly IS their responsibility to see that their contracted services are performing properly!
You make a good point there. However, given Comcast tech's track record I think it will probably get fixed faster if you go straight to AT&T.
--
You want the truth? You can't handle the truth! |
|
ki1o
Premium
join:2001-04-12
Atlanta, GA
| reply to toasterhead1
Re: Comcast of ATLANTA, SHAMEFUL!!!!!
said by toasterhead1 :
BTW its funny because today I got an email asking me to close my BBB complaint with comcast from comcast =P HA!
Today I got a call from some lady from Customer Advocacy Team who called and left a message on my answering machine saying "We are currently working on your problem, why did you complain to the BBB?" (not in those exact words) and I called right back and told her why. I told her about Robin and how she never returned 2 of my calls (read my first post in this forum for more information about Robin and what I had to go through to get Comcast to admit their was a problem). I'm sure she had all that information in the complaint the BBB sent her. I guess Yesterday 6/25 was BBB response day. At least this time it took Comcast about 2 weeks to respond to my complaint instead of 3 months when I complained back in December.
--
Boycott The RIAA |
|
