Packet loss...

[kyle1745]

Ok, I use insight cables RR which is just a sub company that sell Time Warners RR in my area.

At night and on weekends I experience very bad packet loss and temporary loss of connection due to the packet loss.

First off the first IP in a tracert confuses me since it is 10.39.128.1.

Is this the neighborhood router? If I ping this at night the pings can get well over 400ms with 50% packet loss. I can normally ping thigns beyond that ok but still have the drops and 20-30% packet loss to say www.yahoo.com.

They refuse to talk with me concerning this issue as I have had them tell me everything from clear my explorer cache to set my nic to 10mbit. They don't even think to try to understand the graphs I send them from pingplotter to show that it changed during peak horus which proves that it is not my issue.

Anyways does anyone have any ideas how to get through to them, and is this IP the neighborhood router?

Thanks,
Kyle

[blebs]

Welcome to Speedguide kyle1745.

Your best bet here would be to talk to our Moderator Kip Patterson.

It sounds to me like a definate problem at your first hop, but you know that already. Kip may be able to help you find away to convey what your seeing to the ISP.

Have you called your cable company direct or are you going through the RR national help desk?

[kyle1745]

Well i have been e-mailing them, trying to avoid the normal hour phone call. They can't seem to understand that it is not my issue.

I think will call tomorrow.

Kyle

[crazyjw1971]

Tracing route to www.yahoo.akadns.net [216.115.102.81]

over a maximum of 30 hops:



1 7 ms 7 ms 9 ms 10.72.248.1

2 * * * Request timed out.

3 * * * Request timed out.

4 7 ms 7 ms 7 ms 68.48.0.50

5 8 ms 7 ms 8 ms 12.126.174.73

6 8 ms 7 ms 11 ms gbr6-p30.wswdc.ip.att.net [12.123.9.70]

7 9 ms 10 ms 12 ms 12.122.11.169

8 7 ms 7 ms 7 ms ggr1-p340.wswdc.ip.att.net [12.122.11.234]

9 8 ms 9 ms 8 ms pos6-3.core1.Washington1.Level3.net [209.244.219.157]

10 9 ms 9 ms 10 ms ae0-52.mp2.Washington1.Level3.net [64.159.18.34]

11 80 ms 80 ms 80 ms so-3-0-0.mp1.SanJose1.Level3.net [64.159.1.129]

12 79 ms 80 ms 80 ms gige9-2.ipcolo4.SanJose1.Level3.net [64.159.2.138]

13 * * * Request timed out.

14 81 ms 82 ms 82 ms ge-2-3-0.msr2.pao.yahoo.com [216.115.101.46]

15 82 ms 81 ms 82 ms vl21.bas2.snv.yahoo.com [216.115.100.229]

16 85 ms 83 ms 82 ms w9.snv.yahoo.com [216.115.102.81]



Trace complete.


Notice hops 2 and 3...

Node problems baby!

You'd be better off calling them and complaining. Tell them that you want a ticket written up on the problem. Im having packet loss problems myself and I had to call comcast and PROVE MY POINT. They hate having customers that know what theyre talking about...

BTW... that trace route came from MY COMPUTER and I was just transitioned TODAY!

Comcast.net...

They suck!

[kyle1745]

Ok, but what is the 10.*.*.* address?

Does anyone know? That is my problem.

As I said I think it is the neighborhood router, but I want to verify it before I rip into them.

Kyle

[Kip Patterson]

The 10.x.x.x address is the CMTS at the headend. If you have excessive lost packets and high pings, something is definitely wrong in the ISP's plant. The pings can result from traffic, but the packet loss indicates that something isn't right. A myriad of possible causes, including noise from a bad TV, infiltration, bad taps, bad amps, etc. They need to fix it. Try writing a letter is they won't respond to phone calls.

CrazyJoe - your trace route looks great! You couldn't do much better if you tried. The routers at 2, 3, and 13 have been intentionally programmed by your ISP to ignore the ICMP packets used by ping and traceroute. I don't happen to agree with the ISP's decision to do that, but it is their choice.

Kip