*** Free High Speed Internet *** Please Read!!!

[faamecanic]

Do you understand what packet loss is? How are you determining, your packet loss to the first hop? unless you have an analyzer on the first device there isnt a way to find that out.
I suggest you go ahead an report the cable provider. let us know what happens when they tell you that it has been divulged and you signed acceptance of it.
Actually the way Ethernet works is amazing anyways since the entire medium works with Collisions and packet loss, they are built into the correction.

Actually finding you packetloss (as well as ping times) is as easy as opening your command prompt (Start-accessories- commandprompt) and typing in tracert 64.233.167.99 (googles IP address...or insert any know IP address here).

1 27 10.207.224.1
2 26 33 63.147.48.193 (equip1-stm-167.gmpexpress.net)
3 20 67 67.133.246.53 (dca-edge-13.inet.qwest.net)
4 31 205.171.209.73 (dca-core-01.inet.qwest.net)
5 53 67.14.8.10 (cer-core-01.inet.qwest.net)
6 43 205.171.139.162 (chx-edge-01.inet.qwest.net)
7 46 65.112.69.202
8 47 33 216.239.46.1
9 47 72.14.232.53
10 46 72.14.232.57
11 57 72.14.232.74
12 47 33 64.233.167.99 (google.com)

First number is the hop (1 is usually your head end, 2nd is the CMTS....NOTE the packet loss in BOLD). Second number is ping, third is Packet loss, and 4th are the different hops.

This one is actully pretty good as of late. But its only 5:30...by 7pm it will be horrible.

EDIT: And at 8:21pm I have this

1 44 67 10.207.224.1
2 54 33 63.147.48.193 (equip1-stm-167.gmpexpress.net)
3 91 67.133.246.53 (dca-edge-13.inet.qwest.net)
4 69 67 205.171.209.73 (dca-core-01.inet.qwest.net)
5 69 33 205.171.209.114 (dcx-core-02.inet.qwest.net)
6 50 205.171.251.38 (dcp-brdr-02.inet.qwest.net)
7 37 193.251.247.193 (po3-3.ashcr2.Ashburn.opentransit.net)
8 61 33 193.251.243.2
9 35 193.251.241.113 (po9-0.nykcr2.NewYork.opentransit.net)
10 40 193.251.241.238 (po6-0.nykbb3.NewYork.opentransit.net)
11 45 193.251.250.34 (google-us-peers-6.GW.opentransit.net)
12 38 216.239.49.35
13 61 33 72.14.236.219
14 61 72.14.236.181
15 88 72.14.236.134
16 67 33 72.14.207.99 (google.com)

NOTE: 67% packet LOSS on the first hop....NOT GOOD.


Collisions... could they be caused by a overloaded CMTS? Say one where 200 people to a port is max reccomended but right now Metrocast has 420 people on a port? Yes.... and when packets get lost multiple times (outside the range of what is compensated for) you get a connection that will drop. Maybe not enough to notice when surfing or emailing... but definately enough to interfere with Web based applications that think you have disconnected from a server.

Now.... yes I understand full well that there are no gaurenteed speeds. Most users wont really see a difference between 2,000 kb/s and 4,000 if all they do is surf the web or email with their connections. But small business users, and those of us that know a bit about computers and networking will.

Metrocast cannot expect to keep customers if my $69/mo cable connection gives me worse performance than 56k dialup (dont have the packet loss with dialup). And especially if DSL is more widely spread.

Nice thing is if you check here (for those of us suffering with bad speeds/packet loss) Broad Band Reports on Metorcast

You will see a rep from Metrocast has posted here several times. As long as he/she isnt blowing smoke up our rear ends.... Metrocast is aware of the problem,and are on it. We SHOULD have our speeds back (minus packet loss) by the end of this week or next.... (crosses fingers).

My whole point is it is bad business to have a cable modem connection drop to the point where it IS noticiable to most users. And its even WORSE business to not notify them about the problem and give us an eta on a fix(they can MASS email all thier internet customers...they have done it in previous instances).