said by bret3d
:I'll put my details and history below but here is the gist of the problem. I have "found" a ridiculously slow route from Pittsburgh to Columbus. Specifically from my parent's house to my house although there are other people who have been experiencing this problem. This has been going on since November of 2007. At the time, my parent's ISP was Comcast (15Mbps down/768kbps up) and I assumed it was Comcasts' fault. 3 weeks ago I convinced my parents to change to Verizon Fios (15Mbps down/15Mbps up) and the problem persists. I have Time Warner Road Runner Turbo (15Mbps down/768kbps up). Both our speeds most other places are fine. And anything I send them is fine. But if the data is being sent to me it goes to a crawl. I have not seen it go faster
than 200kbps and typically it's somewhere between 120kbps and 30kbps.
I've tried all times of the day.
I have called Time Warner Road Runner support twice in the last two weekends and given my sob story with no response. I've also called Verizon just to get them working on it even though I'm pretty sure it's not their fault.
I am not convinced this is not intentional. Something like this if it was a bad piece of hardware would have been fixed a while ago. I can get "around" this by using a VPN like my work or Hotspot Shield and I have seen speeds around 1200 kbps doing that.
My easiest way out of this is to change providers to WOW Cable (6Mbps down/1Mbps up) assuming all is fine there. But I have been a Road Runner subscriber since 1997 and have been very pleased with their customer service up to now.
Is there something else I can do to show Road Runner where to look? I've already given them the traceroutes and speed tests you can find from this thread( »
www.slingcommunity.com/forum/thr···er-bad./ ). And if I can localize it and they choose to do nothing I would like to advertise that to everyone. They have yet to let me to talk to someone technical who is local.
Any help would be appreciated. I'm not a total novice but I'm nowhere near an expert.
Thanks.
-Bret
------------------------
traceroute from Pittsburgh(Verizon-Fios) to Columbus(RR-Columbus). 8th hop always drops at least one.
Tracing route to cpe-75-185-xxx-xxx.columbus.res.rr.com [75.185.xxx.xxx] with TTL of 32:
1 5ms 1ms 1ms Wireless_Broadband_Router.home [192.168.1.1]
2 6ms 6ms 5ms 96.236.150.1
3 7ms 6ms 6ms G5-1-220.LCR-02.PITBPA.verizon-gni.net [130.81.129.92]
4 15ms 14ms 17ms 130.81.17.199
5 37ms 15ms 15ms ge-6-1-4.pr0.dca10.tbone.rr.com [66.109.9.33]
6 15ms 34ms 15ms ae-2-0.cr0.dca20.tbone.rr.com [66.109.6.164]
7 38ms 24ms 23ms 66.109.6.71
8 * 51ms * gig0-3-0.mtgmoh1-rtr0.columbus.rr.com [24.95.81.213]
9 54ms 45ms 32ms gig5-0-0.clmboh1-rtr2.columbus.rr.com [65.25.137.246]
10 31ms 31ms 34ms srp1-1.uparoh1-ybr2.columbus.rr.com [65.25.129.34]
11 48ms 34ms 35ms gig0-3.uparoh1-ubr2.columbus.rr.com [24.95.86.142]
12 97ms 97ms 113ms cpe-75-185-xxx-xxx.columbus.res.rr.com [75.185.xxx.xxx]
Traceroute complete.
If the router was his problem it would impact every connection equally. If he only has problems to Pittsburgh, something other than the router is the problem.