RCN → Chicago latency packet loss

From me to local or first hop:

Tracing route to 172.30.232.1 over a maximum of 30 hops

0 eq2.cable.rcn.com [24.148.28.163]

1 172.30.232.1

Computing statistics for 25 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 eq2.cable.rcn.com [24.148.28.163]

37/ 100 = 37% |

1 96ms 37/ 100 = 37% 0/ 100 = 0% 172.30.232.1

Trace complete.

Thats a 37% packet loss in 1 hop?

I've talked to CS and they are very nice but see no problem from their end.

I'm a gamer and play on a server in California.

Doing a pathping to last rcn node gives me things like this:
Tracing route to ge4-0.core4.sfrn.ca.rcn.net [208.59.255.19]

over a maximum of 30 hops:

0 eq2.cable.rcn.com [24.148.28.163]

1 172.30.232.1

2 vl2.aggr1.chgo.il.rcn.net [207.229.191.129]

3 fe1-1-0.core3.chgo.il.rcn.net [208.59.216.210]

4 * ge0-0-2.core1.chsl.il.rcn.net [207.172.19.41]

5 pos5-0.core3.sfrn.ca.rcn.net [208.59.95.98]

6 ge4-0.core4.sfrn.ca.rcn.net [208.59.255.19]

Computing statistics for 150 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 eq2.cable.rcn.com [24.148.28.163]

15/ 100 = 15% |

1 8ms 21/ 100 = 21% 6/ 100 = 6% 172.30.232.1

0/ 100 = 0% |

2 13ms 20/ 100 = 20% 5/ 100 = 5% vl2.aggr1.chgo.il.rcn.net [207.229.191.129]

0/ 100 = 0% |

3 20ms 19/ 100 = 19% 4/ 100 = 4% fe1-1-0.core3.chgo.il.rcn.net [208.59.216.210]

0/ 100 = 0% |

4 10ms 22/ 100 = 22% 7/ 100 = 7% ge0-0-2.core1.chsl.il.rcn.net [207.172.19.41]

0/ 100 = 0% |

5 64ms 15/ 100 = 15% 0/ 100 = 0% pos5-0.core3.sfrn.ca.rcn.net [208.59.95.98]

1/ 100 = 1% |

6 63ms 16/ 100 = 16% 0/ 100 = 0% ge4-0.core4.sfrn.ca.rcn.net [208.59.255.19]

Trace complete.

I've attached the txt file if that makes it easier to read.

Just a little history. When I moved a few years ago I made sure I was moving to an area where RCN had service.

Mac: 0004751B61C0

Leaf

Any help is appreciated..Joe you about?

first things first, 3com modems do not properly report downchannel power remotely, but your transmit power is very high. I would schedule a truck roll to start - get your RF levels in spec.

temporarily, you could remove all splitters ( and TVs ) and anything else in the house that could cause ingress and loss and try testing that way.

So I should call and get a truck out?

I did what you said and now have no tv in my office gulp..heheh anyway that seems to have helped a bit packet loss dropped some ran five pathpings range from 3 to 25%. Download speeds still 20% of advertised.

I would call support - there isnt much I can do for this one without making sure everything in house is ok

gah double post - mind not working today

Joe,

I'm still checking my end of the modem to be sure it's no something here.

I'll let ya know

I think I may be loosing my mind.

I been at this for hours.

At one point it looked like the problem was on my end. When pathpinging my Modem's ip I got this horrid packet loss. I uninstalled then reinstalled my onboard nic(abit nf7-s ver.2..nforce2 platform) and saw 0 packet loss.

Ran that several times and all was honky dory.

Played an online game..EQ2 for a few hours and game play got worse and worse. Logged out of game and packet loss is back. Installed a netgear nic card and see same problem...Tried 4 different network cables..no change.

Uninstalled and reinstalled onboard nic several times...Just ran chi.speakeasy.net 34 down 708 up.

It's 2 am and I'm giving up for the moment.

Any Ideas?

OK fixed,

I'm a bit upset that cs kept saying it was on my end.
It just didn't make any sence. I tried 4 different nic's a total of 8 different cables. Was getting packet loss all over the place.
My speeds were nice but not what I am paying for.

CS pretty much refused to send a truck cause everything looked so good on their end.

Solution: Went down to Compusa and took the last Moto 5100 on the shelf....zero packet loss speed to chi.speakeasy over 9k.

Maybe this should be in FAQ? or trouble shooting or something.

Anyway thanks for taking your time Joe.

Tom from CS thanks for tryin bud.