site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
2597
Share Topic
Post a:
Post a:
AuthorAll Replies

david000

join:2010-02-10
Hamilton, OH

Zoomtown or Road Runner?

I am so fed up with Cincinnati Bell and looking for something else. I've been a long time Zoomtown customer and recently, their service just plain sucks during peak times (I blame fios). I am currently subscribed to their 5 meg plan and I think it's time for a switch. I'm a WoW junky and can not raid due to packet loss/ping during peak times. It's so bad to where I would just log off in frustration because their service sucks. My game would just hang, then speed up after it got all of the information, and finally my ping would skyrocket to 400-500. I called their tech support and sent them over trace routes of where the problem is (on their end) but they assured me that because I'm getting their rated speed, I should just bend over and take it in the ass because I'm getting fucked in this deal. I guess quantity>quality in their ideal world and this terrible service is showing me just that.

My question to you guys is this. You think Road Runner will be a better choice for me?

Sorry for the language. I am just fed up with this craptastic company (and to think at one time they were great!)

I just want to raid with a stable ping and no packet loss.


Handyman7

@parallax.ws

Never noticed a lag during "peak" or any other times with Zoomtown. I am an extended territories customer, though.

I did have the lag (seriously) with RoadRunner from TWC, though. In fact, it got so bad during the evenings that I was lucky to get 1 megabit in speed tests (normally got 7megabit), and dumped TWC for ZT, and really never looked back. I get a consistent 4.2 megabit from ZT and am satisfied with it.


rtm330

join:2001-09-13
Dayton, OH

Just wait, Handyman. They'll come for you like they came for me.

I was rock solid at 4200 down until September 2010, when they dialed me and my neighbors back. I still sit at 4000kbps, and that's only if I use the ancient (11 years old) Wirespeed modem I got from Ameriyuck. If I use that Westell that CinBell sent out, performance just goes into the to!let.

Whenever I see ads claiming "5 mpbs", I go all Admiral Ackbar -- "It's a trappppp."



Handyman7

@parallax.ws

Those Westel modems have been known to go bad. I would try swapping it out for a new one at your local CB store. If that doesn't work, you might insist that they send someone out with a line tester which will tell you what your DSL line is capable of. Mine can do 5200/896 but they won't provision it any higher than 5000/768 which yields for me about 4200/650 in practical use.


WTwitchell

join:2011-02-21
Columbus, OH

We have TW Roadrunner and everything is fine except the CA Security slows everything down.


david000

join:2010-02-10
Hamilton, OH

4 edits

reply to david000

Deleted



david0001

@fuse.net

reply to david000
Let's play a game! Guess where the problems lie!

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms unknown [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.200.1
3 11 ms 15 ms 16 ms HM-ESR1-74-83-64-1.fuse.net [74.83.64.1]
4 15 ms 9 ms 9 ms 10ge2-4.ws-osr1.zoomtown.com [216.68.6.203]
5 * 17 ms * 10ge1-4.sw1.core.fuse.net [216.68.6.202]
6 9 ms 9 ms 9 ms sw2.svs.fuse.net [216.68.6.19]
7 17 ms 14 ms 12 ms register.fuse.net [216.68.1.60]

Trace complete.

C:\Users\Dave>tracert fuse.net

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 tracert fuse.net

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 tracert fuse.net

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 tracert fuse.net

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms unknown [192.168.1.1]
2 1 ms 2 ms 1 ms 192.168.200.1
3 7 ms 8 ms 9 ms HM-ESR1-74-83-64-1.fuse.net [74.83.64.1]
4 9 ms 9 ms 10 ms 10ge2-4.ws-osr1.zoomtown.com [216.68.6.203]
5 * * * Request timed out.
6 21 ms 8 ms 10 ms sw2.svs.fuse.net [216.68.6.19]
7 9 ms 13 ms 9 ms register.fuse.net [216.68.1.60]

Trace complete.

C:\Users\Dave>tracert fuse.net

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 tracert fuse.net

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms unknown [192.168.1.1]
2 1 ms 2 ms 2 ms 192.168.200.1
3 9 ms 8 ms 7 ms HM-ESR1-74-83-64-1.fuse.net [74.83.64.1]
4 9 ms 8 ms 9 ms 10ge2-4.ws-osr1.zoomtown.com [216.68.6.203]
5 * * * Request timed out.
6 10 ms 9 ms 9 ms sw2.svs.fuse.net [216.68.6.19]
7 19 ms 15 ms 13 ms register.fuse.net [216.68.1.60]

Trace complete.

C:\Users\Dave>tracert fuse.net

Tracing route to fuse.net [216.68.1.60]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms unknown [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.200.1
3 7 ms 7 ms 6 ms HM-ESR1-74-83-64-1.fuse.net [74.83.64.1]
4 10 ms 10 ms 14 ms 10ge2-4.ws-osr1.zoomtown.com [216.68.6.203]
5 9 ms * 9 ms 10ge1-4.sw1.core.fuse.net [216.68.6.202]
6 9 ms 10 ms 9 ms sw2.svs.fuse.net [216.68.6.19]
7 9 ms 10 ms 9 ms register.fuse.net [216.68.1.60]

Trace complete.

C:\Users\Dave>tracert google.com

Tracing route to google.com [74.125.226.116]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms unknown [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.200.1
3 10 ms 6 ms 6 ms HM-ESR1-74-83-64-1.fuse.net [74.83.64.1]
4 8 ms 8 ms 8 ms 10ge2-4.ws-osr1.zoomtown.com [216.68.6.203]
5 10 ms * * 10ge1-4.sw1.core.fuse.net [216.68.6.202]
6 13 ms 15 ms 12 ms 10ge0-1-0-0.core2.core.fuse.net [216.68.6.197]
7 16 ms 15 ms 15 ms core1-t7-4.chi.fuse.net [216.68.6.215]
8 26 ms 25 ms 20 ms 74.83.240.33
9 16 ms 16 ms 19 ms 209.85.254.120
10 50 ms 48 ms 48 ms 216.239.46.216
11 47 ms 45 ms 47 ms 216.239.48.24
12 42 ms 42 ms 42 ms 74.125.226.116

PS Fix your fisher price backbone Zoomtown!


qnadad

join:2004-05-30
Covington, KY

reply to david000
Make a direct connection to whatever DSL modem you have and come back with ping and trace results. I can't find anything wrong with anything you've posted.
YMMV but remember, ICMP is like the redheaded stepchild of the internet. I'm not overly concerned about the non responsive routes and it's quite common on enterprise level networks.


Monday, 04-Jun 01:38:16 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics