Comcast subscribers in NJ, PA, MD region

[psteng19]

tracert to any site or server.
Pings jump as soon as the handoff from comcast.net to att.net

Couple of friends in my area are complaining of the same issue.
Tech support is too stupid to even understand a tracert :|

 

[slackerinabox]

You know, I live in NYC (Bk) and noticed my Comcast connection being quite sluggish today. It's so bad that I'm stealing my neighbor's signal right now

P.S. She stole from us before, it's all good.

 

[Rubycon]

Lemme guess, that router in NJ is screwing up?

12.118.102.9 or close?

 

[acemcmac]

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

C:\Documents and Settings\Administrator>ping google.com

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=101ms TTL=235
Reply from 72.14.207.99: bytes=32 time=97ms TTL=235
Reply from 72.14.207.99: bytes=32 time=107ms TTL=235
Reply from 72.14.207.99: bytes=32 time=98ms TTL=235

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 107ms, Average = 100ms

thanks for the heads up... oddly, I hadn't noticed

 

[psteng19]

Originally posted by: C6FT7
Lemme guess, that router in NJ is screwing up?

12.118.102.9 or close?

Close, I guess.
12.126.124.141

Just checked BBR and Comcast forums and apparently they're aware of it.
It's been ongoing since the beginning of Nov.

Text
Text

The speed is so poor, it's affecting even browsing. Don't even mention gaming with this type of lag...

 

[KarenMarie]

From Lyndhurst. NJ


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

C:\Documents and Settings\KarenMarie>ping google.com

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=125ms TTL=238
Reply from 72.14.207.99: bytes=32 time=117ms TTL=238
Reply from 72.14.207.99: bytes=32 time=121ms TTL=238
Reply from 72.14.207.99: bytes=32 time=121ms TTL=238

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 125ms, Average = 121ms

 

[Linux23]

I just don't see any problems here. Am I missing something?

Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms neoroute.neosoft.com [192.168.10.10]
2 * * * Request timed out.
3 10 ms 11 ms 9 ms ge-2-1-ur02.jerseycity.nj.panjde.comcast.net [68
.86.220.173]
4 15 ms 11 ms 60 ms po10-ur01.narlington.nj.panjde.comcast.net [68.8
6.209.250]
5 10 ms 14 ms 12 ms po70-ar01.verona.nj.panjde.comcast.net [68.86.20
9.254]
6 13 ms 12 ms 15 ms ar01.plainfield.nj.panjde.comcast.net [68.86.208
.5]
7 12 ms 17 ms 36 ms 68.86.211.2
8 12 ms 16 ms 55 ms 12.118.102.21
9 16 ms 55 ms 16 ms tbr2-p032501.n54ny.ip.att.net [12.123.3.86]
10 37 ms 39 ms 17 ms ggr2-p3120.n54ny.ip.att.net [12.123.3.109]
11 73 ms 73 ms 45 ms so-7-1.car3.NewYork1.Level3.net [4.68.127.5]
12 97 ms 72 ms 55 ms ae-1-51.bbr1.NewYork1.Level3.net [4.68.97.1]
13 55 ms 51 ms 62 ms ae-0-0.bbr2.Atlanta1.Level3.net [64.159.1.46]
14 53 ms 94 ms 81 ms ae-21-54.car1.Atlanta1.Level3.net [4.68.103.98]

15 85 ms 63 ms 86 ms 4.78.212.74
16 74 ms 54 ms 56 ms 66.249.95.125
17 53 ms 55 ms 71 ms 216.239.49.226
18 68 ms 59 ms 81 ms 64.233.187.99

Trace complete.

 

[Vich]

yes

 

[psteng19]

Originally posted by: Linux23
I just don't see any problems here. Am I missing something?

Apparently you're not effected.
Look at hops 14 and 15 :|

11 13 ms 14 ms 14 ms po10-ur01.narlington.nj.panjde.comcast.net [68.86.209.250]
12 14 ms 14 ms 14 ms po70-ar01.verona.nj.panjde.comcast.net [68.86.209.254]
13 15 ms 33 ms 14 ms ar01.plainfield.nj.panjde.comcast.net [68.86.208.5]
14 15 ms 14 ms 15 ms 68.86.211.2
15 201 ms 203 ms 202 ms 12.119.12.17
16 210 ms 210 ms 205 ms tbr1-p013902.n54ny.ip.att.net [12.123.219.129]
17 199 ms 200 ms 202 ms ggr2-p310.n54ny.ip.att.net [12.123.3.105]
18 244 ms 239 ms 245 ms so-8-1.car3.NewYork1.Level3.net [4.68.127.149]
19 247 ms 248 ms 244 ms ae-1-54.bbr2.NewYork1.Level3.net [4.68.97.97]
20 226 ms 232 ms 226 ms ae-0-0.bbr2.Chicago1.Level3.net [64.159.1.34]
21 218 ms 219 ms 223 ms ae-22-52.car2.Chicago1.Level3.net [4.68.101.163]
22 214 ms 212 ms 210 ms 4.79.66.150
23 236 ms 230 ms 226 ms 64.233.175.97
24 234 ms 229 ms 227 ms 72.14.236.181
25 225 ms 225 ms 226 ms 66.249.94.73
26 234 ms 230 ms 237 ms 72.14.236.134
27 235 ms 229 ms 225 ms 72.14.207.99

Trace complete.

 

[Rubycon]

LOL at this. Even the INSIDE ip's are bad.

Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:

1 435 ms 343 ms 336 ms 10.20.30.119
2 331 ms 339 ms 332 ms 10.20.30.1
3 349 ms 351 ms 357 ms 10.1.36.1
4 343 ms 341 ms 349 ms at-1-2-0-1718.core-rtr1.res.verizon-gni.net [130.81.11.237]
5 355 ms 355 ms 361 ms 130.81.20.16
6 354 ms 347 ms 352 ms 130.81.10.90
7 351 ms 362 ms 349 ms so-2-1-0-0.gar3.washington1.level3.net [4.79.192.5]
8 351 ms 350 ms 404 ms ae-2-54.bbr2.washington1.level3.net [4.68.121.97]
9 373 ms 381 ms 373 ms ae-0-0.bbr1.chicago1.level3.net [64.159.1.33]
10 365 ms 370 ms 363 ms ae-12-53.car2.chicago1.level3.net [4.68.101.67]
11 351 ms 353 ms 349 ms 4.79.66.150
12 363 ms 364 ms 363 ms 64.233.175.97
13 367 ms 370 ms 374 ms 66.249.94.69
14 387 ms 373 ms 374 ms 72.14.236.183
15 386 ms 395 ms 399 ms 72.14.207.99

 

[Linux23]

Apparently you're not effected.

Yay me.


/surfs at insanely fast speeds.

 

[Linux23]

Originally posted by: C6FT7
LOL at this. Even the INSIDE ip's are bad.

Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:

1 435 ms 343 ms 336 ms 10.20.30.119
2 331 ms 339 ms 332 ms 10.20.30.1
3 349 ms 351 ms 357 ms 10.1.36.1
4 343 ms 341 ms 349 ms at-1-2-0-1718.core-rtr1.res.verizon-gni.net [130.81.11.237]
5 355 ms 355 ms 361 ms 130.81.20.16
6 354 ms 347 ms 352 ms 130.81.10.90
7 351 ms 362 ms 349 ms so-2-1-0-0.gar3.washington1.level3.net [4.79.192.5]
8 351 ms 350 ms 404 ms ae-2-54.bbr2.washington1.level3.net [4.68.121.97]
9 373 ms 381 ms 373 ms ae-0-0.bbr1.chicago1.level3.net [64.159.1.33]
10 365 ms 370 ms 363 ms ae-12-53.car2.chicago1.level3.net [4.68.101.67]
11 351 ms 353 ms 349 ms 4.79.66.150
12 363 ms 364 ms 363 ms 64.233.175.97
13 367 ms 370 ms 374 ms 66.249.94.69
14 387 ms 373 ms 374 ms 72.14.236.183
15 386 ms 395 ms 399 ms 72.14.207.99

power cycle that modem.

 

[ChaoZ]

I'm in California and my connection was crap the whole last week.

 

[Rubycon]

Originally posted by: Linux23

power cycle that modem.

There's no modem here. Funny thing latency is high but can download and upload > 10 Mbps just about anywhere. That's freaky.

 

[GoSharks]

ping www.google.com

Pinging www.l.google.com [64.233.161.104] with 32 bytes of data:

Reply from 64.233.161.104: bytes=32 time=234ms TTL=240
Reply from 64.233.161.104: bytes=32 time=593ms TTL=240
Reply from 64.233.161.104: bytes=32 time=258ms TTL=240
Reply from 64.233.161.104: bytes=32 time=229ms TTL=240

Ping statistics for 64.233.161.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 229ms, Maximum = 593ms, Average = 328ms

In Baltimore, MD with comcast.

 

[wiredspider]

In DE, but I connect to PA comcast for some reason... and yea it's been cr@p. I called in and the guy said it might be my modem and then said he was gonna send a guy out. Then it started working ok.... I should switch to FIOS...

 

[Rainsford]

I'm in MD, and I get the same issue at the hop from comcast to att as well...

12 12 ms 13 ms 12 ms 68.87.16.157
13 25 ms 25 ms 24 ms pos-0-0-cr01.whitemarsh.md.core.comcast.net [68.87.16.21]
14 226 ms 226 ms 225 ms 12.118.149.21
15 221 ms 220 ms 214 ms tbr2-p014001.n54ny.ip.att.net [12.123.3.14]
16 209 ms 206 ms 209 ms ggr2-p390.n54ny.ip.att.net [12.123.3.62]

I don't play a lot of online games, so I didn't really notice it...but that's pretty bad.