kirk1233
join:2003-08-15
Pittsburgh, PA
| CRAN in Pittsburgh - sucks
I wish they would remove this CRAN junk. Not only does it create more hops, latency to some sites went from the 20s to the 150s to 250s. I also am having packet loss that I never had before the change.
Is this just me or do other people in the Pittsburgh are notice this too? |
|
J D McDorce
Premium
join:2001-12-29
Westland, MI | Could you post a tracert so we could see where the problem might lie? |
|
JeepMatt
Delaware Fios
Premium
join:2001-12-28
Wilmington, DE | First of all - and LAST..lol..
Pittsburgh is NOT on the CRAN -
At the present, this is only for NJ,DE, and South Central and Southeast PA.
--
"ONE team - ONE city - ONE dream!!" |
|
blondebaldy
join:2001-12-13
Williamsport, PA | reply to kirk1233
like philly boy stated not in CRAN yet.......post some results and see where your issues are.......Im north of pittsburgh and have been rock solid since day one |
|
kirk1233
join:2003-08-15
Pittsburgh, PA
| reply to kirk1233
68. addresses are CRAN, right? Check the dropped packets and latency at the end. Like this for most but not all sites:
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 26 ms 6 ms 6 ms 10.170.139.1
2 6 ms 5 ms 20 ms 68.86.101.221
3 7 ms 7 ms 10 ms 68.86.100.65
4 10 ms 11 ms 9 ms 68.86.100.57
5 8 ms 8 ms 7 ms 68.86.100.53
6 13 ms 9 ms 12 ms 68.86.100.49
7 18 ms 19 ms 19 ms 12.118.118.9
8 19 ms 20 ms 21 ms tbr1-p013901.phlpa.ip.att.net [12.123.137.70]
9 21 ms 24 ms 21 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 21 ms 22 ms 26 ms gar1-p341.nwrnj.ip.att.net [12.123.0.37]
11 * * * Request timed out.
12 22 ms 22 ms 22 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
13 22 ms 26 ms 22 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
14 480 ms * 246 ms www.dslreports.com [209.123.109.175]
Trace complete. |
|
Big_D
Premium
join:2003-06-02
Augusta, GA | Regardless if you are on CRAN or not, the problem in the provided trace is at the destination, completely unrelated to Comcast.
--
You want the truth? You can't handle the truth! |
|
camarozz2828
join:2003-07-17
Hanover, MA | reply to kirk1233
" 11 * * * Request timed out."
dont worry about that it's normal either it ignored the ping from low priority set to them or it is set to ignore them totally |
|
rockotman
...Blown On The Steel Breeze
Emerging Research
join:2000-08-06
DSotM
clubs:
 ·Verizon FIOS
| reply to kirk1233
I am in the Pgh area as well, and seem to have pretty good times to dslreports.
C:>tracert www.dslreports.com
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 28 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 20 ms 8 ms 9 ms 12.244.28.17
4 16 ms 8 ms 9 ms 12.244.65.53
5 17 ms 16 ms 20 ms 12.125.176.121
6 42 ms 19 ms 16 ms gbr1-p70.phlpa.ip.att.net [12.123.137.22]
7 18 ms 19 ms 17 ms tbr1-p012501.phlpa.ip.att.net [12.122.12.97]
8 19 ms 21 ms 20 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
9 19 ms 23 ms 19 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181]
10 * * * Request timed out.
11 27 ms 22 ms 25 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
12 52 ms 54 ms 27 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
13 20 ms 22 ms 20 ms www.dslreports.com [209.123.109.175]
Trace complete.
C:\>ping www.dslreports.com
Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=33ms TTL=49
Reply from 209.123.109.175: bytes=32 time=19ms TTL=49
Reply from 209.123.109.175: bytes=32 time=27ms TTL=49
Reply from 209.123.109.175: bytes=32 time=21ms TTL=49
Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 33ms, Average = 25ms
--
...is there anybody out there... |
|
Combat Chuck
Too Many Cannibals
Premium
join:2001-11-29
Erie, PA
| No problem here in Penn Hills
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 18 ms 12 ms 12 ms 10.172.108.1
2 12 ms 16 ms 11 ms 12.244.89.129
3 14 ms 11 ms 26 ms 12.244.65.42
4 23 ms 20 ms 18 ms 12.244.72.66
5 19 ms 23 ms 20 ms gbr2-p70.phlpa.ip.att.net [12.123.137.26]
6 23 ms 21 ms 19 ms tbr1-p012601.phlpa.ip.att.net [12.122.12.101]
7 26 ms 22 ms 43 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
8 24 ms 21 ms 24 ms gar1-p341.nwrnj.ip.att.net [12.123.0.37]
9 * * * Request timed out.
10 43 ms 21 ms 21 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
11 27 ms 23 ms 34 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
12 22 ms 22 ms 23 ms www.dslreports.com [209.123.109.175]
Trace complete.
Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=29ms TTL=51
Reply from 209.123.109.175: bytes=32 time=22ms TTL=51
Reply from 209.123.109.175: bytes=32 time=25ms TTL=51
Reply from 209.123.109.175: bytes=32 time=22ms TTL=51
Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 29ms, Average = 24ms
--
Beagles really should come in convienent 10 packs. |
|
kirk1233
join:2003-08-15
Pittsburgh, PA | reply to kirk1233
Looks like I'm the only one in the area with the 68. addresses in the hops... |
|
rockotman
...Blown On The Steel Breeze
Emerging Research
join:2000-08-06
DSotM
clubs:
·Verizon FIOS
| said by kirk1233  :Looks like I'm the only one in the area with the 68. addresses in the hops... I use a router, and I have it clone the MAC of one of the computers. Depending on which PC I have it cloning, I pull a differenct IP from Comcast. My old PC (which I took off-line about a month ago), used to pull and IP that started with something other than the typical "24" that the rest of the here PCs evoke. IIRC, tracerts looked much different when I had that IP as opposed to one of the IPs starting with a "24" in the first triplet. I don't know that this helps you much; just an observation.
--
...is there anybody out there... |
|
