Stupid Comcast

[necine]

I have comcast and my connection keeps dropping. So far technicians have been to my home two times to look for the problem. My signal strength is perfect. I've disconnected my router and have it plugged directly into my computer.

I perfromed a tracert, and this is my results. Anyone else in the NJ, PA, DE area getting this???


tracert comcast.net

Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 10.125.128.1
2 6 ms 5 ms 8 ms ge-6-1-ur01.absecon.nj.panjde.comcast.net [68.86
.215.37]
3 8 ms 11 ms 6 ms te-1-1-ur02.absecon.nj.panjde.comcast.net [68.86
.210.122]
4 13 ms 5 ms 7 ms te-2-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.126]
5 9 ms 10 ms 19 ms po10-ar01.audubon.nj.panjde.comcast.net [68.86.2
08.22]
6 17 ms 28 ms 13 ms 68.86.211.10
7 25 ms 11 ms 13 ms 12.118.114.13
8 292 ms 298 ms * tbr1-p012301.phlpa.ip.att.net [12.123.137.62]
9 287 ms 291 ms 286 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 295 ms 301 ms 297 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
11 293 ms 291 ms 291 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 307 ms 301 ms 300 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 294 ms 291 ms 299 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
14 295 ms 292 ms 308 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
15 * * * Request timed out.
16 * * * Request timed out.
17 279 ms 281 ms 282 ms www.comcast.net [204.127.195.15]

Trace complete.

----

I called them several times to let them know about their bottleneck. They don't seem to care.

 

[Alkesh]

I have no idea what that means, and I'm kinda glad that I don't

 

[LikeLinus]

Originally posted by: necine
I have comcast and my connection keeps dropping. So far technicians have been to my home two times to look for the problem. My signal strength is perfect. I've disconnected my router and have it plugged directly into my computer.

I perfromed a tracert, and this is my results. Anyone else in the NJ, PA, DE area getting this???


tracert comcast.net

Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 10.125.128.1
2 6 ms 5 ms 8 ms ge-6-1-ur01.absecon.nj.panjde.comcast.net [68.86
.215.37]
3 8 ms 11 ms 6 ms te-1-1-ur02.absecon.nj.panjde.comcast.net [68.86
.210.122]
4 13 ms 5 ms 7 ms te-2-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.126]
5 9 ms 10 ms 19 ms po10-ar01.audubon.nj.panjde.comcast.net [68.86.2
08.22]
6 17 ms 28 ms 13 ms 68.86.211.10
7 25 ms 11 ms 13 ms 12.118.114.13
8 292 ms 298 ms * tbr1-p012301.phlpa.ip.att.net [12.123.137.62]
9 287 ms 291 ms 286 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 295 ms 301 ms 297 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
11 293 ms 291 ms 291 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 307 ms 301 ms 300 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 294 ms 291 ms 299 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
14 295 ms 292 ms 308 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
15 * * * Request timed out.
16 * * * Request timed out.
17 279 ms 281 ms 282 ms www.comcast.net [204.127.195.15]

Trace complete.

----

I called them several times to let them know about their bottleneck. They don't seem to care.

That's an ATT server outside of their network and out of their control.

How exactly they are idiots for that? There's nothing they can do.

 

[necine]

Originally posted by: LikeLinus

Originally posted by: necine
I have comcast and my connection keeps dropping. So far technicians have been to my home two times to look for the problem. My signal strength is perfect. I've disconnected my router and have it plugged directly into my computer.

I perfromed a tracert, and this is my results. Anyone else in the NJ, PA, DE area getting this???


tracert comcast.net

Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 10.125.128.1
2 6 ms 5 ms 8 ms ge-6-1-ur01.absecon.nj.panjde.comcast.net [68.86
.215.37]
3 8 ms 11 ms 6 ms te-1-1-ur02.absecon.nj.panjde.comcast.net [68.86
.210.122]
4 13 ms 5 ms 7 ms te-2-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.126]
5 9 ms 10 ms 19 ms po10-ar01.audubon.nj.panjde.comcast.net [68.86.2
08.22]
6 17 ms 28 ms 13 ms 68.86.211.10
7 25 ms 11 ms 13 ms 12.118.114.13
8 292 ms 298 ms * tbr1-p012301.phlpa.ip.att.net [12.123.137.62]
9 287 ms 291 ms 286 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 295 ms 301 ms 297 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
11 293 ms 291 ms 291 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 307 ms 301 ms 300 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 294 ms 291 ms 299 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
14 295 ms 292 ms 308 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
15 * * * Request timed out.
16 * * * Request timed out.
17 279 ms 281 ms 282 ms www.comcast.net [204.127.195.15]

Trace complete.

----

I called them several times to let them know about their bottleneck. They don't seem to care.

That's an ATT server outside of their network and out of their control.

How exactly they are idiots for that? There's nothing they can do.

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot. Comcast is buying peering peering transit from ATT. The bottleneck is where comcast peers with ATT. Comcast should purchase a peer that can handle their network load?

Definitely comcasts problem.

 

[LikeLinus]

Originally posted by: necine

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot.

Again, at this point it is out of their hands. ATT is the idiot in this situation. As stated, theres really nothing that COMCAST can do.

 

[mzkhadir]

Originally posted by: necine

Originally posted by: LikeLinus

Originally posted by: necine
I have comcast and my connection keeps dropping. So far technicians have been to my home two times to look for the problem. My signal strength is perfect. I've disconnected my router and have it plugged directly into my computer.

I perfromed a tracert, and this is my results. Anyone else in the NJ, PA, DE area getting this???


tracert comcast.net

Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 10.125.128.1
2 6 ms 5 ms 8 ms ge-6-1-ur01.absecon.nj.panjde.comcast.net [68.86
.215.37]
3 8 ms 11 ms 6 ms te-1-1-ur02.absecon.nj.panjde.comcast.net [68.86
.210.122]
4 13 ms 5 ms 7 ms te-2-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.126]
5 9 ms 10 ms 19 ms po10-ar01.audubon.nj.panjde.comcast.net [68.86.2
08.22]
6 17 ms 28 ms 13 ms 68.86.211.10
7 25 ms 11 ms 13 ms 12.118.114.13
8 292 ms 298 ms * tbr1-p012301.phlpa.ip.att.net [12.123.137.62]
9 287 ms 291 ms 286 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 295 ms 301 ms 297 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
11 293 ms 291 ms 291 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 307 ms 301 ms 300 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 294 ms 291 ms 299 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
14 295 ms 292 ms 308 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
15 * * * Request timed out.
16 * * * Request timed out.
17 279 ms 281 ms 282 ms www.comcast.net [204.127.195.15]

Trace complete.

----

I called them several times to let them know about their bottleneck. They don't seem to care.

That's an ATT server outside of their network and out of their control.

How exactly they are idiots for that? There's nothing they can do.

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot. Comcast is buying peering peering transit from ATT. The bottleneck is where comcast peers with ATT. Comcast should purchase a peer that can handle their network load?



Definitely comcasts problem.

To me it looks like you are the idiot for not recognizing that this is an att issue and not a comcast issue.

 

[necine]

Originally posted by: LikeLinus

Originally posted by: necine

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot.

Again, that this point it is out of their hands. ATT is the idiot in this situation. As stated, theres really nothing that COMCAST can do.

My contract is with Comcast to get a service that works. I actually think it is comcasts problem because they started routing too many nodes through that one area... probably to save money. Comcast knows exactly how much their peer can handle and they are sending too much data through the philly peer.

 

[LikeLinus]

Originally posted by: necine

Originally posted by: LikeLinus

Originally posted by: necine

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot.

Again, that this point it is out of their hands. ATT is the idiot in this situation. As stated, theres really nothing that COMCAST can do.

It's not a shared responsibility. My contract is with Comcast to get a service that works. I actually think it is comcasts problem because they started routing too many nodes through that one area... probably to save money. Comcast knows exactly how much their peer can handle and they are sending too much data through the philly peer.

Where is your proof that Comcast is overloading the ATT nodes and oversaturating their networks.

How about you just grab a blanket...take a midol and cry about it some more.

Have you ever read your TOS? Where does it state 100% uptime. Just wondering.

 

[necine]

Originally posted by: mzkhadir

Originally posted by: necine

Originally posted by: LikeLinus

Originally posted by: necine
I have comcast and my connection keeps dropping. So far technicians have been to my home two times to look for the problem. My signal strength is perfect. I've disconnected my router and have it plugged directly into my computer.

I perfromed a tracert, and this is my results. Anyone else in the NJ, PA, DE area getting this???


tracert comcast.net

Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 10.125.128.1
2 6 ms 5 ms 8 ms ge-6-1-ur01.absecon.nj.panjde.comcast.net [68.86
.215.37]
3 8 ms 11 ms 6 ms te-1-1-ur02.absecon.nj.panjde.comcast.net [68.86
.210.122]
4 13 ms 5 ms 7 ms te-2-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.126]
5 9 ms 10 ms 19 ms po10-ar01.audubon.nj.panjde.comcast.net [68.86.2
08.22]
6 17 ms 28 ms 13 ms 68.86.211.10
7 25 ms 11 ms 13 ms 12.118.114.13
8 292 ms 298 ms * tbr1-p012301.phlpa.ip.att.net [12.123.137.62]
9 287 ms 291 ms 286 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 295 ms 301 ms 297 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
11 293 ms 291 ms 291 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 307 ms 301 ms 300 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 294 ms 291 ms 299 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
14 295 ms 292 ms 308 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
15 * * * Request timed out.
16 * * * Request timed out.
17 279 ms 281 ms 282 ms www.comcast.net [204.127.195.15]

Trace complete.

----

I called them several times to let them know about their bottleneck. They don't seem to care.

That's an ATT server outside of their network and out of their control.

How exactly they are idiots for that? There's nothing they can do.

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot. Comcast is buying peering peering transit from ATT. The bottleneck is where comcast peers with ATT. Comcast should purchase a peer that can handle their network load?



Definitely comcasts problem.

To me it looks like you are the idiot for not recognizing that this is an att issue and not a comcast issue.

Comcast is my provider, not ATT. Comcast routes their connection through ATT, as a backbone for their connections. Comcast chooses how many people to route through that connection, not ATT. Comcast is overloading the network, not ATT.

ATT is paid to provide a backbone, probably OC-48. If comcast decides to route 3 states w/ probably 1+ million customers... whose the idiot? me or comcast?

 

[LikeLinus]

Originally posted by: necine

Comcast is my provider, not ATT. Comcast routes their connection through ATT, as a backbone for their connections. Comcast chooses how many people to route through that connection, not ATT. Comcast is overloading the network, not ATT.

ATT is paid to provide a backbone, probably OC-48. If comcast decides to route 3 states w/ probably 1+ million customers... whose the idiot? me or comcast?

Actually you are the idiot here. You have no clue what the contract states or what is even going on. You are throwing around so much FUD it's rediculous.

Can you supply data on how many people they are sending and the contractual agreement between each company? Please include the section where it states if there is a specific number of users allowed on each node, or if comcast is allowed to just "send everyone they want!" to that server location.

Here's the solution. QUIT FREAKING USING COMCAST. Now you're the idiot if you keep using the. Switch to DSL, another cable provider or sat. It's your choice. You have no contract with them and they never said 100% uptime. Read your TOS and quit your whining like a little girl.

Switch providers if they are that bad.

 

[mzkhadir]

C:\>tracert www.comcast.net

Tracing route to www.comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 25 ms 15 ms * 172.31.17.38
4 10 ms 12 ms * sl-gw32-chi-2-0.sprintlink.net [160.81.194.217]

5 12 ms 10 ms * sl-bb21-chi-4-2.sprintlink.net [144.232.26.33]
6 11 ms 10 ms * sl-bb20-chi-14-0.sprintlink.net [144.232.26.1]
7 11 ms 12 ms * sl-st20-chi-12-0.sprintlink.net [144.232.8.219]

8 13 ms 11 ms * sprint-gw.cgcil.ip.att.net [192.205.32.149]
9 67 ms 62 ms * tbr1-p032501.cgcil.ip.att.net [12.122.82.13]
10 79 ms 66 ms * tbr1-cl1.sffca.ip.att.net [12.122.10.6]
11 63 ms 66 ms * gar4-p300.sffca.ip.att.net [12.123.13.174]
12 58 ms 61 ms * idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
13 251 ms 399 ms 909 ms 63.241.85.98
14 255 ms 78 ms * 192.168.64.73
15 62 ms 62 ms * www.comcast.net [204.127.195.15]
16 58 ms 61 ms * www.comcast.net [204.127.195.15]
17 70 ms 58 ms * www.comcast.net [204.127.195.15]
18 70 ms 57 ms * www.comcast.net [204.127.195.15]
19 72 ms 68 ms * www.comcast.net [204.127.195.15]

trace from chicago to comcast.net

 

[necine]

Originally posted by: mzkhadir
C:\>tracert www.comcast.net

Tracing route to www.comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 25 ms 15 ms * 172.31.17.38
4 10 ms 12 ms * sl-gw32-chi-2-0.sprintlink.net [160.81.194.217]

5 12 ms 10 ms * sl-bb21-chi-4-2.sprintlink.net [144.232.26.33]
6 11 ms 10 ms * sl-bb20-chi-14-0.sprintlink.net [144.232.26.1]
7 11 ms 12 ms * sl-st20-chi-12-0.sprintlink.net [144.232.8.219]

8 13 ms 11 ms * sprint-gw.cgcil.ip.att.net [192.205.32.149]
9 67 ms 62 ms * tbr1-p032501.cgcil.ip.att.net [12.122.82.13]
10 79 ms 66 ms * tbr1-cl1.sffca.ip.att.net [12.122.10.6]
11 63 ms 66 ms * gar4-p300.sffca.ip.att.net [12.123.13.174]
12 58 ms 61 ms * idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
13 251 ms 399 ms 909 ms 63.241.85.98
14 255 ms 78 ms * 192.168.64.73
15 62 ms 62 ms * www.comcast.net [204.127.195.15]
16 58 ms 61 ms * www.comcast.net [204.127.195.15]
17 70 ms 58 ms * www.comcast.net [204.127.195.15]
18 70 ms 57 ms * www.comcast.net [204.127.195.15]
19 72 ms 68 ms * www.comcast.net [204.127.195.15]

trace from chicago to comcast.net

Thanks for the help, but it looks like you're in a different area. Looks like CA. Where do you live?

 

[LikeLinus]

Question, just because you have a 200MS hop...that would not make you "drop" your own connection. You should not see any loss of connection or anything actual lag to your web browsing or downloading.

Is your connection really completely dropping?

 

[LikeLinus]

Originally posted by: necine

Originally posted by: mzkhadir


trace from chicago to comcast.net

Thanks for the help, but it looks like you're in a different area. Looks like CA. Where do you live?

Nevermind, you are the idiot here.

I'm still waiting for the details of node overload (concurrent users connected) and the contractual agreement terms between ATT and Comcast that you seem to know so much about.

 

[mzkhadir]

Originally posted by: necine

Originally posted by: mzkhadir
C:\>tracert www.comcast.net

Tracing route to www.comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 25 ms 15 ms * 172.31.17.38
4 10 ms 12 ms * sl-gw32-chi-2-0.sprintlink.net [160.81.194.217]

5 12 ms 10 ms * sl-bb21-chi-4-2.sprintlink.net [144.232.26.33]
6 11 ms 10 ms * sl-bb20-chi-14-0.sprintlink.net [144.232.26.1]
7 11 ms 12 ms * sl-st20-chi-12-0.sprintlink.net [144.232.8.219]

8 13 ms 11 ms * sprint-gw.cgcil.ip.att.net [192.205.32.149]
9 67 ms 62 ms * tbr1-p032501.cgcil.ip.att.net [12.122.82.13]
10 79 ms 66 ms * tbr1-cl1.sffca.ip.att.net [12.122.10.6]
11 63 ms 66 ms * gar4-p300.sffca.ip.att.net [12.123.13.174]
12 58 ms 61 ms * idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
13 251 ms 399 ms 909 ms 63.241.85.98
14 255 ms 78 ms * 192.168.64.73
15 62 ms 62 ms * www.comcast.net [204.127.195.15]
16 58 ms 61 ms * www.comcast.net [204.127.195.15]
17 70 ms 58 ms * www.comcast.net [204.127.195.15]
18 70 ms 57 ms * www.comcast.net [204.127.195.15]
19 72 ms 68 ms * www.comcast.net [204.127.195.15]

trace from chicago to comcast.net

Thanks for the help, but it looks like you're in a different area. Looks like CA. Where do you live?

Arlington Heights, IL

 

[necine]

Originally posted by: LikeLinus

Originally posted by: necine

Originally posted by: mzkhadir


trace from chicago to comcast.net

Thanks for the help, but it looks like you're in a different area. Looks like CA. Where do you live?

Nevermind, you are the idiot here.

I'm still waiting for the details of node overload (concurrent users connected) and the contractual agreement terms between ATT and Comcast that you seem to know so much about.

Comcast technician told me when he came.

 

[LikeLinus]

Originally posted by: necine

Originally posted by: LikeLinus

Originally posted by: necine

Originally posted by: mzkhadir


trace from chicago to comcast.net

Thanks for the help, but it looks like you're in a different area. Looks like CA. Where do you live?

Nevermind, you are the idiot here.

I'm still waiting for the details of node overload (concurrent users connected) and the contractual agreement terms between ATT and Comcast that you seem to know so much about.

Comcast technician told me when he came.

Well thats proof enough for me! I'm dropping comcast right now and moving to DSL!!!

haha, yeah comcast is the "idiot" here.

Good luck with your bitching...

FYI you never answered my question about the connection dropping? The ATT latency problem would not cause your actual connection to drop. Webpages would time out, but the actual connection to comcast would still be available. So WTF are you talking about your connections dropping?

 

[spidey07]

I don't see any problem here, and I giggle at the lunacy.

Just a quick backup - the entire class A 12./8 is AT&T.

This has nothing to do with comcast or you losing service.

 

[spidey07]

Originally posted by: necine

Originally posted by: mzkhadir

Originally posted by: necine

Originally posted by: LikeLinus

Originally posted by: necine
I have comcast and my connection keeps dropping. So far technicians have been to my home two times to look for the problem. My signal strength is perfect. I've disconnected my router and have it plugged directly into my computer.

I perfromed a tracert, and this is my results. Anyone else in the NJ, PA, DE area getting this???


tracert comcast.net

Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 10.125.128.1
2 6 ms 5 ms 8 ms ge-6-1-ur01.absecon.nj.panjde.comcast.net [68.86
.215.37]
3 8 ms 11 ms 6 ms te-1-1-ur02.absecon.nj.panjde.comcast.net [68.86
.210.122]
4 13 ms 5 ms 7 ms te-2-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.126]
5 9 ms 10 ms 19 ms po10-ar01.audubon.nj.panjde.comcast.net [68.86.2
08.22]
6 17 ms 28 ms 13 ms 68.86.211.10
7 25 ms 11 ms 13 ms 12.118.114.13
8 292 ms 298 ms * tbr1-p012301.phlpa.ip.att.net [12.123.137.62]
9 287 ms 291 ms 286 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 295 ms 301 ms 297 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
11 293 ms 291 ms 291 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 307 ms 301 ms 300 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 294 ms 291 ms 299 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
14 295 ms 292 ms 308 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
15 * * * Request timed out.
16 * * * Request timed out.
17 279 ms 281 ms 282 ms www.comcast.net [204.127.195.15]

Trace complete.

----

I called them several times to let them know about their bottleneck. They don't seem to care.

That's an ATT server outside of their network and out of their control.

How exactly they are idiots for that? There's nothing they can do.

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot. Comcast is buying peering peering transit from ATT. The bottleneck is where comcast peers with ATT. Comcast should purchase a peer that can handle their network load?



Definitely comcasts problem.

To me it looks like you are the idiot for not recognizing that this is an att issue and not a comcast issue.

Comcast is my provider, not ATT. Comcast routes their connection through ATT, as a backbone for their connections. Comcast chooses how many people to route through that connection, not ATT. Comcast is overloading the network, not ATT.

ATT is paid to provide a backbone, probably OC-48. If comcast decides to route 3 states w/ probably 1+ million customers... whose the idiot? me or comcast?

LOL!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

-edit-

wait, now that I'm done choking...

bwahahahahhahahahhhahahahhahahhahahhahhahaahhahahahahhahahahahha.

Really? So that's how it works?

 

[necine]

Originally posted by: LikeLinus

Originally posted by: necine

Originally posted by: LikeLinus

Originally posted by: necine

Originally posted by: mzkhadir


trace from chicago to comcast.net

Thanks for the help, but it looks like you're in a different area. Looks like CA. Where do you live?

Nevermind, you are the idiot here.

I'm still waiting for the details of node overload (concurrent users connected) and the contractual agreement terms between ATT and Comcast that you seem to know so much about.

Comcast technician told me when he came.

Well thats proof enough for me! I'm dropping comcast right now and moving to DSL!!!

haha, yeah comcast is the "idiot" here.

Good luck with your bitching...

FYI you never answered my question about the connection dropping? The ATT latency problem would not cause your actual connection to drop. Webpages would time out, but the actual connection to comcast would still be available. So WTF are you talking about your connections dropping?

Yeah... dunno the connection just drops every 10 minutes or so..

 

[necine]

Originally posted by: spidey07

Originally posted by: necine

Originally posted by: mzkhadir

Originally posted by: necine

Originally posted by: LikeLinus

Originally posted by: necine
I have comcast and my connection keeps dropping. So far technicians have been to my home two times to look for the problem. My signal strength is perfect. I've disconnected my router and have it plugged directly into my computer.

I perfromed a tracert, and this is my results. Anyone else in the NJ, PA, DE area getting this???


tracert comcast.net

Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 10.125.128.1
2 6 ms 5 ms 8 ms ge-6-1-ur01.absecon.nj.panjde.comcast.net [68.86
.215.37]
3 8 ms 11 ms 6 ms te-1-1-ur02.absecon.nj.panjde.comcast.net [68.86
.210.122]
4 13 ms 5 ms 7 ms te-2-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.126]
5 9 ms 10 ms 19 ms po10-ar01.audubon.nj.panjde.comcast.net [68.86.2
08.22]
6 17 ms 28 ms 13 ms 68.86.211.10
7 25 ms 11 ms 13 ms 12.118.114.13
8 292 ms 298 ms * tbr1-p012301.phlpa.ip.att.net [12.123.137.62]
9 287 ms 291 ms 286 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 295 ms 301 ms 297 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
11 293 ms 291 ms 291 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 307 ms 301 ms 300 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 294 ms 291 ms 299 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
14 295 ms 292 ms 308 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
15 * * * Request timed out.
16 * * * Request timed out.
17 279 ms 281 ms 282 ms www.comcast.net [204.127.195.15]

Trace complete.

----

I called them several times to let them know about their bottleneck. They don't seem to care.

That's an ATT server outside of their network and out of their control.

How exactly they are idiots for that? There's nothing they can do.

ATT provides their backbone. They have peer agreements. If you can't resolve a crappy backbone in 2 week, you = idiot. Comcast is buying peering peering transit from ATT. The bottleneck is where comcast peers with ATT. Comcast should purchase a peer that can handle their network load?



Definitely comcasts problem.

To me it looks like you are the idiot for not recognizing that this is an att issue and not a comcast issue.

Comcast is my provider, not ATT. Comcast routes their connection through ATT, as a backbone for their connections. Comcast chooses how many people to route through that connection, not ATT. Comcast is overloading the network, not ATT.

ATT is paid to provide a backbone, probably OC-48. If comcast decides to route 3 states w/ probably 1+ million customers... whose the idiot? me or comcast?

LOL!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

-edit-

wait, now that I'm done choking...

bwahahahahhahahahhhahahahhahahhahahhahhahaahhahahahahhahahahahha.

Really? So that's how it works?

Thought so... at least thats how it was explained to me. Care to let me know how it works?

 

[necine]

It doesn't make sense though. If the problem were with my lines I'd have high latency throughout each of the hops. It only starts when I get to the ATT hop. I'm probably an idiot when it comes to this but shouldn't that mean the connection is not on my lines it's somewhere throughout the comcast network???

They've already sent 2 technicians and the third is coming thursday. It just sucks that they can't fix whatever the issue may be.

 

[necine]

Originally posted by: spidey07
I don't see any problem here, and I giggle at the lunacy.

Just a quick backup - the entire class A 12./8 is AT&T.

This has nothing to do with comcast or you losing service.

So what does this have to do with... As per my research alot of people in my area are having the same problems.

 

[spidey07]

Originally posted by: necine

Originally posted by: spidey07
I don't see any problem here, and I giggle at the lunacy.

Just a quick backup - the entire class A 12./8 is AT&T.

This has nothing to do with comcast or you losing service.

So what does this have to do with... As per my research alot of people in my area are having the same problems.

There is no guarantee for latency on your connection.

that means there isn't a problem.

 

[1sikbITCH]

Here you go, OP:

http://www.dslreports.com/forum/remark,14763419

There's 7 pages of Comcast customers all complaining about that same ATT node.

In the future, when having ISP and internet related issues (as opposed to networking issues), you may find it helpful to start by checking the Comcast forum at broadbandreports.com. Even though I've nver had problems with Comcast, I still visit occasionally to see what the latest upgrades or price increases are coming.