Reply
New Visitor
Posts: 1
Registered: ‎09-22-2005

Slow Connection in Bel Air, MD

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

1 3 ms 2 ms 2 ms pcp0011480771pcs.chrchv01.md.comcast.net
2 10 ms 10 ms 8 ms 73.139.120.1
3 12 ms 9 ms 10 ms ge-1-21-ur01.churchville.md.bad.comcast.net
4 10 ms 7 ms 7 ms te-9-1-ur02.churchville.md.bad.comcast.net
5 9 ms 9 ms 9 ms te-8-4-ar01.whitemarsh.md.bad.comcast.net
6 12 ms 19 ms 12 ms po10-ar01.capitolhghts.md.bad.comcast.net
7 11 ms 14 ms 11 ms 68.87.16.165
8 91 ms 89 ms 90 ms pos-0-0-cr01.whitemarsh.md.core.comcast.net
9 182 ms 180 ms 180 ms 12.118.102.9
10 161 ms 159 ms 161 ms tbr1-p010101.n54ny.ip.att.net
11 163 ms 164 ms 161 ms 12.122.81.1
12 159 ms 158 ms 165 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net
13 181 ms 184 ms 180 ms sccsbix11-3-1.attbi.com
14 190 ms 192 ms 189 ms 192.168.72.14
15 174 ms 175 ms 175 ms 192.168.72.65
16 167 ms 165 ms 165 ms 192.168.201.11
17 180 ms 181 ms 178 ms www.comcast.net

Trace complete.



C:\Documents and Settings\Jeff Akers>ping -t www.comcast.net

Pinging www.comcast.net with 32 bytes of data:

Reply from 204.127.205.8: bytes=32 time=223ms TTL=56
Reply from 204.127.205.8: bytes=32 time=209ms TTL=56
Reply from 204.127.205.8: bytes=32 time=200ms TTL=56
Reply from 204.127.205.8: bytes=32 time=198ms TTL=56
Reply from 204.127.205.8: bytes=32 time=204ms TTL=56
Reply from 204.127.205.8: bytes=32 time=208ms TTL=56
Reply from 204.127.205.8: bytes=32 time=207ms TTL=56
Reply from 204.127.205.8: bytes=32 time=214ms TTL=56
Reply from 204.127.205.8: bytes=32 time=203ms TTL=56
Reply from 204.127.205.8: bytes=32 time=221ms TTL=56
Reply from 204.127.205.8: bytes=32 time=202ms TTL=56
Reply from 204.127.205.8: bytes=32 time=207ms TTL=56
Reply from 204.127.205.8: bytes=32 time=207ms TTL=56
Reply from 204.127.205.8: bytes=32 time=223ms TTL=56
Reply from 204.127.205.8: bytes=32 time=209ms TTL=56
Reply from 204.127.205.8: bytes=32 time=211ms TTL=56
Reply from 204.127.205.8: bytes=32 time=204ms TTL=56
Reply from 204.127.205.8: bytes=32 time=207ms TTL=56
Reply from 204.127.205.8: bytes=32 time=202ms TTL=56
Reply from 204.127.205.8: bytes=32 time=206ms TTL=56
Reply from 204.127.205.8: bytes=32 time=211ms TTL=56
Reply from 204.127.205.8: bytes=32 time=215ms TTL=56
Reply from 204.127.205.8: bytes=32 time=219ms TTL=56
Reply from 204.127.205.8: bytes=32 time=217ms TTL=56
Reply from 204.127.205.8: bytes=32 time=223ms TTL=56
Reply from 204.127.205.8: bytes=32 time=229ms TTL=56
Reply from 204.127.205.8: bytes=32 time=226ms TTL=56
Reply from 204.127.205.8: bytes=32 time=229ms TTL=56
Reply from 204.127.205.8: bytes=32 time=239ms TTL=56
Reply from 204.127.205.8: bytes=32 time=238ms TTL=56
Reply from 204.127.205.8: bytes=32 time=238ms TTL=56
Reply from 204.127.205.8: bytes=32 time=238ms TTL=56
Reply from 204.127.205.8: bytes=32 time=228ms TTL=56
Reply from 204.127.205.8: bytes=32 time=232ms TTL=56
Reply from 204.127.205.8: bytes=32 time=240ms TTL=56
Request timed out.
Reply from 204.127.205.8: bytes=32 time=248ms TTL=56
Reply from 204.127.205.8: bytes=32 time=238ms TTL=56
Reply from 204.127.205.8: bytes=32 time=246ms TTL=56
Reply from 204.127.205.8: bytes=32 time=245ms TTL=56
Reply from 204.127.205.8: bytes=32 time=243ms TTL=56
Reply from 204.127.205.8: bytes=32 time=239ms TTL=56
Reply from 204.127.205.8: bytes=32 time=251ms TTL=56
Reply from 204.127.205.8: bytes=32 time=250ms TTL=56
Reply from 204.127.205.8: bytes=32 time=256ms TTL=56
Reply from 204.127.205.8: bytes=32 time=257ms TTL=56
Reply from 204.127.205.8: bytes=32 time=257ms TTL=56
Reply from 204.127.205.8: bytes=32 time=253ms TTL=56
Reply from 204.127.205.8: bytes=32 time=249ms TTL=56
Reply from 204.127.205.8: bytes=32 time=245ms TTL=56
Reply from 204.127.205.8: bytes=32 time=246ms TTL=56
Reply from 204.127.205.8: bytes=32 time=260ms TTL=56
Reply from 204.127.205.8: bytes=32 time=243ms TTL=56
Reply from 204.127.205.8: bytes=32 time=242ms TTL=56
Reply from 204.127.205.8: bytes=32 time=243ms TTL=56
Reply from 204.127.205.8: bytes=32 time=229ms TTL=56
Reply from 204.127.205.8: bytes=32 time=232ms TTL=56
Reply from 204.127.205.8: bytes=32 time=240ms TTL=56

Ping statistics for 204.127.205.8:
Packets: Sent = 58, Received = 57, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 260ms, Average = 228ms
Control-C
^C
Regular Contributor
Posts: 79
Registered: ‎03-12-2005

Re: Slow Connection in Bel Air, MD

hey man thats the problem i posted about earlier :/
i'm over in reisterstown and my tracert is:

Tracing route to midpointgaming503.sxpress.com
over a maximum of 30 hops:

1 6 ms 5 ms 6 ms 10.88.240.1
2 4 ms 6 ms 5 ms ge-1-21-ur02.owingsmills.md.bad.comcast.net
3 6 ms 5 ms 7 ms te-9-2-ur01.towson.md.bad.comcast.net
4 5 ms 5 ms 6 ms te-9-1-ur02.towson.md.bad.comcast.net
5 6 ms 5 ms 5 ms te-9-2-ur01.parkville.md.bad.comcast.net
6 6 ms 6 ms 7 ms te-9-4-ur01.aberdeen.md.bad.comcast.net
7 6 ms 33 ms 6 ms te-9-3-ur01.churchville.md.bad.comcast.net
8 7 ms 5 ms 5 ms te-9-1-ur02.churchville.md.bad.comcast.net
9 7 ms 8 ms 12 ms te-8-4-ar01.whitemarsh.md.bad.comcast.net
10 9 ms 9 ms 9 ms po10-ar01.capitolhghts.md.bad.comcast.net
11 10 ms 10 ms 9 ms 68.87.16.161
12 80 ms 78 ms 81 ms pos-0-0-cr01.whitemarsh.md.core.comcast.net
13 198 ms 196 ms 194 ms 12.118.102.5
14 177 ms 180 ms 180 ms tbr1-p010101.n54ny.ip.att.net
15 203 ms 204 ms 205 ms ggr2-p310.n54ny.ip.att.net
16 223 ms 317 ms 217 ms dcr1-so-3-0-0.newyork.savvis.net
17 202 ms 241 ms 213 ms mar1-pos-5-0.NewYorknyd.savvis.net
18 181 ms 179 ms 179 ms 204.8.102.90
19 247 ms 222 ms 204 ms midpointgaming503.sxpress.com

Trace complete.
New Visitor
Posts: 13
Registered: ‎07-17-2005

Re: Slow Connection in Bel Air, MD

and the problems continue...last issue took 3 months to fix. im guessing this one takes 2 1/2 months. any takers?

Bel Air, MD:

Microsoft Windows XP
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Joe>ping comcast.net

Pinging comcast.net with 32 bytes of data:

Reply from 204.127.195.15: bytes=32 time=275ms TTL=53
Reply from 204.127.195.15: bytes=32 time=286ms TTL=53
Reply from 204.127.195.15: bytes=32 time=294ms TTL=53
Reply from 204.127.195.15: bytes=32 time=295ms TTL=53

Ping statistics for 204.127.195.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 275ms, Maximum = 295ms, Average = 287ms

C:\Documents and Settings\Joe>tracert comcast.net

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

1 8 ms 7 ms 7 ms 73.139.80.1
2 7 ms 8 ms 7 ms ge-1-22-ur02.churchville.md.bad.comcast.net
3 9 ms 18 ms 7 ms te-8-4-ar01.whitemarsh.md.bad.comcast.net
4 10 ms 9 ms 11 ms po10-ar01.capitolhghts.md.bad.comcast.net
5 11 ms 11 ms 10 ms 68.87.16.165
6 97 ms 98 ms 97 ms pos-0-0-cr01.whitemarsh.md.core.comcast.net
7 221 ms 214 ms 216 ms 12.118.102.9
8 288 ms 276 ms 279 ms tbr1-p010101.n54ny.ip.att.net
9 272 ms 274 ms 281 ms tbr1-cl14.cgcil.ip.att.net
10 262 ms 268 ms 273 ms tbr1-cl1.sffca.ip.att.net
11 267 ms 269 ms 274 ms gar4-p300.sffca.ip.att.net
12 281 ms 277 ms 281 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net
13 279 ms 275 ms 273 ms rwcsbix11-1-6.attbi.com
14 281 ms 271 ms 272 ms 192.168.64.14
15 274 ms 278 ms 281 ms 192.168.64.65
16 297 ms 283 ms 290 ms www.comcast.net

Trace complete.

C:\Documents and Settings\Joe>
Message was edited by: jlazzaro
Regular Contributor
Posts: 79
Registered: ‎03-12-2005

Re: Slow Connection in Bel Air, MD

I called comcast 3 times, and they somehow can't see anything?

And they push that a tech at my house would some how help, when they don't. It is obviously comcasts problem not my line. I hope this doesn't take a month, because mine is so high that it lags out every 15 min?

Fix this asap :/
New Visitor
Posts: 13
Registered: ‎07-17-2005

Re: Slow Connection in Bel Air, MD

Unfortunately 12.118.102.5 is an AT&T hop, nothing much comcast can do but push the issue. I noticed the post about the high pings are night on the AT&T network, but this just started happening to me tonight...
New Visitor
Posts: 4
Registered: ‎07-20-2005

Re: Slow Connection in Bel Air, MD

Ya im getting this too, im not gona bother posting my tracert and ping times as its pretty much the same as your all getting. On top of that the max speeds i can get are:

Download Speed: 1659 kbps (207.4 KB/sec transfer rate)
Upload Speed: 197 kbps (24.6 KB/sec transfer rate)

And i have the 8mb/768Kbps deal. This sucks. Hope it gets fixed soon.

O and i live in Ocean City, Maryland..so im guessing this is a MD problem :smileysad:
Message was edited by: Anon1382348
Regular Contributor
Posts: 79
Registered: ‎03-12-2005

Re: Slow Connection in Bel Air, MD

Yea but: 6 97 ms 98 ms 97 ms pos-0-0-cr01.whitemarsh.md.core.comcast.net

is not a at&t hop, and that should not be any where close that high.
Most Valued Poster
Michael
Posts: 6,099
Registered: ‎06-30-2003

Re: Slow Connection in Bel Air, MD

Please see my reply in this thread.