DadeMurphy
Rbettenc
Premium
join:2002-07-25
Danvers, MA
clubs:
 ·Verizon FIOS
 ·Comcast
| reply to deblin
Re: limited newsgroup usage
I know that in my area Cable is less of a crap shoot than DSL.
Verizon DSL in Danvers is notorious for their lack of uptime and constant crap pings.
With comcast I get stable pings and stable speeds, as does all my friends that live throughout the town.
My only issue was when Comcast upgraded to QAM 256 from QAM 64 and I had to throw a splitter on my line to stabilize the signal levels.
--
BLAHHH! |
|
deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE
| reply to PTA
What part of "it varies" am I not clearly communicating? No matter how many people report that it works great for them (or not), the fact remains that cable is a crap shoot. Thank you for proving my point. Nowhere did I say it was bad in all areas. And in heavily populated areas, some of the local cable companies go the extra mile (no pun intended) to "split nodes" or mitigate congestion. But many areas (mine notoriously) do not. Sucks for me, but luckily I have DSL available. Some in my area aren't so lucky.
--
"I drank what?" -Socrates |
|
PTA
@comcast.net
|  reply to deblin
I have Cable Internet and there are a lot of people in my area that do. I have No problimes with Comcast. It is faster that Qwest's DSL Service. It also helped when AT&T Broadband upgraded our area, they put power boosters in when they first started with the upgrade to help with the problem. |
|
deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE
| reply to dadkins
You can't tell just by how many of your neighbors have it. You have no idea how Comcast has their node structure organized.
ping yahoo.com 25 times in a row and look at the ping fluxuations. Mine used to be horrible, with spikes during the night up in the triple digits. Makes for crappy performance in real-time applications and gaming.
$ tracert www.dslreports.com
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 11 ms 11 ms 11 ms adsl-66-218-55-1.dslextreme.com [66.218.55.1]
3 11 ms 11 ms 11 ms f0-1-1.cr1.sjc1.dslextreme.com [66.218.44.57]
4 11 ms 11 ms 11 ms GigabitEthernet4-3.GW2.SJC7.ALTER.NET [157.130.241.237]
5 11 ms 11 ms 11 ms POS4-0.XR1.SJC7.ALTER.NET [152.63.51.46]
6 12 ms 11 ms 11 ms POS5-0.XR1.SJC1.ALTER.NET [152.63.52.133]
7 11 ms 12 ms 12 ms 0.so-0-0-0.XL1.SJC1.ALTER.NET [152.63.55.114]
8 15 ms 15 ms 15 ms 0.so-3-0-0.TL1.SAC1.ALTER.NET [152.63.53.250]
9 78 ms 79 ms 78 ms 0.so-1-2-0.TL1.NYC9.ALTER.NET [152.63.10.77]
10 78 ms 78 ms 78 ms 0.so-5-0-0.XL1.NYC9.ALTER.NET [152.63.0.174]
11 78 ms 79 ms 80 ms POS6-0.GW1.NYC9.ALTER.NET [152.63.99.177]
12 80 ms 80 ms 80 ms nac-nj-oc12-gw.customer.alter.net [157.130.60.182]
13 81 ms 81 ms 80 ms 0.ge-0-0-0.gbr1.oct.nac.net [209.123.11.49]
14 81 ms 80 ms 80 ms www.dslreports.com [209.123.109.175]
Trace complete.
Granted, this is during the day so your numbers may be better than they would at night when more people are on and people have their TVs on and whatnot.
Look at the variance even now in your tracert. Not really anything bad at all, but I would regularly see all hops with variations of 50ms or more. In your case, either your neighbors are light users, or there are multiple nodes in your area, reducing the load at the aggregation point.
--
"I drank what?" -Socrates |
|
dadkins
Can you do Blu?
Premium,MVM
join:2003-09-26
Hercules, CA
·Comcast
| reply to deblin
ALL of my neighbors *Do* have Comcast. DSL @ 384k down for $69.99 per month is not an option. DSL is also area/distance dependant! My pings to DSLR:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\David Adkins>tracert www.dslreports.com
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 2 ms 1 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 19 ms 29 ms 12.244.97.97
4 14 ms 14 ms 10 ms 12.244.67.86
5 24 ms 13 ms 9 ms 12.127.32.65
6 10 ms 12 ms 12 ms tbr1-p012301.sffca.ip.att.net [12.123.13.173]
7 52 ms 52 ms 53 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5]
8 76 ms 74 ms 71 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
9 71 ms 72 ms 70 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181]
10 74 ms 71 ms 72 ms att-gige.esd1.nwr.nac.net [12.119.140.26]
11 71 ms 71 ms 71 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
12 72 ms 71 ms 74 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
13 87 ms 74 ms 74 ms www.dslreports.com [209.123.109.175]
Trace complete.
Works for me.
--
No Firefox here, move along! |
|
deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE
| reply to dadkins
said by dadkins  :running 10s outbound test (client to server) . . . . . 371.88Kb/s running 10s inbound test (server to client) . . . . . . 4.08Mb/s ...rather consistantly, any time of the day - any day of the week. YMMV. That's exactly the problem. Cable is a crap shoot. In my neighborhood, before DSL was available, everyone had Comcast since it was the only option. It was horrid. 200ms pings, fluxuating speeds, long periods of down time, etc. My friend on the other side of town (close to a CO where DSL was readily available) used to have ZERO problems. That's my beef with cable, you NEVER know what you're going to get. And it go down the toilet at any time. If 10 of your neihgbors all the sudden decide to get cable, you may be SOL.
--
"I drank what?" -Socrates |
|
