H-Town dude
@rr.com
| reply to adasdf
Re: Houston Road Runner... High Pings Again##&&@@
I'm kinda wanting to cancel my cable service because i get packet loss everyday and now i am getting high pings but when the cable repair guy gets her the connection decides to act right.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\bevishead>ping -n 50 www.yahoo.com
Pinging www.yahoo.akadns.net [216.109.118.76] with 32 bytes of data:
Reply from 216.109.118.76: bytes=32 time=48ms TTL=46
Reply from 216.109.118.76: bytes=32 time=323ms TTL=46
Reply from 216.109.118.76: bytes=32 time=442ms TTL=46
Reply from 216.109.118.76: bytes=32 time=325ms TTL=46
Reply from 216.109.118.76: bytes=32 time=435ms TTL=46
Reply from 216.109.118.76: bytes=32 time=309ms TTL=46
Reply from 216.109.118.76: bytes=32 time=391ms TTL=46
Reply from 216.109.118.76: bytes=32 time=117ms TTL=46
Reply from 216.109.118.76: bytes=32 time=311ms TTL=46
Reply from 216.109.118.76: bytes=32 time=303ms TTL=46
Reply from 216.109.118.76: bytes=32 time=49ms TTL=46
Reply from 216.109.118.76: bytes=32 time=423ms TTL=46
Reply from 216.109.118.76: bytes=32 time=213ms TTL=46
Reply from 216.109.118.76: bytes=32 time=295ms TTL=46
Reply from 216.109.118.76: bytes=32 time=195ms TTL=46
Reply from 216.109.118.76: bytes=32 time=282ms TTL=46
Reply from 216.109.118.76: bytes=32 time=446ms TTL=46
Reply from 216.109.118.76: bytes=32 time=56ms TTL=46
Reply from 216.109.118.76: bytes=32 time=125ms TTL=46
Reply from 216.109.118.76: bytes=32 time=274ms TTL=46
Reply from 216.109.118.76: bytes=32 time=50ms TTL=46
Reply from 216.109.118.76: bytes=32 time=429ms TTL=46
Reply from 216.109.118.76: bytes=32 time=477ms TTL=46
Reply from 216.109.118.76: bytes=32 time=348ms TTL=46
Reply from 216.109.118.76: bytes=32 time=629ms TTL=46
Reply from 216.109.118.76: bytes=32 time=652ms TTL=46
Reply from 216.109.118.76: bytes=32 time=606ms TTL=46
Reply from 216.109.118.76: bytes=32 time=392ms TTL=46
Reply from 216.109.118.76: bytes=32 time=581ms TTL=46
Reply from 216.109.118.76: bytes=32 time=607ms TTL=46
Reply from 216.109.118.76: bytes=32 time=755ms TTL=46
Reply from 216.109.118.76: bytes=32 time=775ms TTL=46
Reply from 216.109.118.76: bytes=32 time=754ms TTL=46
Reply from 216.109.118.76: bytes=32 time=516ms TTL=46
Reply from 216.109.118.76: bytes=32 time=138ms TTL=46
Reply from 216.109.118.76: bytes=32 time=1004ms TTL=46
Reply from 216.109.118.76: bytes=32 time=620ms TTL=46
Reply from 216.109.118.76: bytes=32 time=840ms TTL=46
Reply from 216.109.118.76: bytes=32 time=477ms TTL=46
Reply from 216.109.118.76: bytes=32 time=206ms TTL=46
Reply from 216.109.118.76: bytes=32 time=239ms TTL=46
Reply from 216.109.118.76: bytes=32 time=436ms TTL=46
Reply from 216.109.118.76: bytes=32 time=83ms TTL=46
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.118.76: bytes=32 time=180ms TTL=46
Reply from 216.109.118.76: bytes=32 time=49ms TTL=46
Reply from 216.109.118.76: bytes=32 time=189ms TTL=46
Reply from 216.109.118.76: bytes=32 time=408ms TTL=46
Ping statistics for 216.109.118.76:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 1004ms, Average = 378ms
C:\Documents and Settings\bevishead> |
|
Konaguy
Live From Kailua-Kona, Hawaii
Premium
join:2000-10-21
Kailua Kona, HI | Re: Houston Road Runner... High Pings Again##&&@
noc@atdn.net
»atdn.net/existing_peer_faq.shtml |
|
Rainier
Shingo
join:2003-11-23
Flushing, NY
1 edit | reply to H-Town dude
Um, ever had 22-minute pings on RoadRunner? That's what I got. You're probably better off with a direct-connection (DSL or so). Got a time? Because: Cable gets truly congested at certain peak times.
EDIT: If you are wondering why I'm commenting about RoadRunner, I'm a past-customer.
EDIT: *!*@24-*.nyc.rr.com |
|
QTraXQ RR
join:2003-11-26
San Antonio, TX
| reply to papillon
Re: Houston Road Runner... High Pings Again##&&@@
Eeee.. very bad Ping Times. If you are Recving heavy amounts of Packets Loss(no matter what you ping), or notice that at times you have a slow internet connection(accessing urls) then you should call your office and possibly have a ping Test Scheduled by L3.
Note:My local office has the capability to do 24-48HR ping test but yours may not. You may need to speak directly to L3 to get a definitive answer..
James
Time Warner Cable
-Broadband Network Services- |
|
Hall
Premium,MVM
join:2000-04-28
Dayton, OH
 ·EarthLink
·AT&T Midwest
 ·Earthlink Cable Mo..
| reply to Karl Bode
Re: Houston Road Runner... High Pings Again##&&@
said by Karl Bode  :
...inform ATDN that they've got a hosed router, which they're already probably aware of....
That's one thing you can be sure of, they knew about the problem long before any users noticed it. They surely have monitoring in place with much different thresholds that we're used to dealing with. I mean, we could see a 10ms increase and not get worried, but they might see a 1ms increase and know something's going wrong.
--
I lost my .sig... Where did it go ?? |
|
papillon
join:2002-03-10
Minnetonka, MN
1 edit |  reply to QTraXQ RR
Re: Houston Road Runner... High Pings Again##&&@@
Thanks, James.
All good for now. However, I know every few months there will be a ATDN fubared router somewhere on the network that will affect myself, and I'm sure, a host of other users. Such is technology I guess.
Thanks for the tips.
I'm out-
pappy |
|
Good Ol Dan
join:2000-05-15
Rochelle Park, NJ
| reply to papillon
said by papillon :
All RR techs on deck... last three nights in the sugar land area of houston - pings in the 80 to 130 mls range. Normally pings are around 7 to 40. Anyone else seen this?
Nope, not here...
C:\>ping sfo.speakeasy.net
Pinging sfo.speakeasy.net [64.81.79.2] with 32 bytes of data:
Reply from 64.81.79.2: bytes=32 time=70ms TTL=47
Reply from 64.81.79.2: bytes=32 time=70ms TTL=47
Reply from 64.81.79.2: bytes=32 time=71ms TTL=47
Reply from 64.81.79.2: bytes=32 time=70ms TTL=47
Ping statistics for 64.81.79.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 71ms, Average = 70ms
C:\ping nyc.speakeasy.net
Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data:
Reply from 216.254.95.2: bytes=32 time=60ms TTL=45
Reply from 216.254.95.2: bytes=32 time=61ms TTL=45
Reply from 216.254.95.2: bytes=32 time=61ms TTL=45
Reply from 216.254.95.2: bytes=32 time=61ms TTL=45
Ping statistics for 216.254.95.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 61ms, Average = 60ms
But then I'm on SBC DSL, too. There's more to this stuff than speed alone... that's why I left TWC. They couldn't get it fixed while I was a customer... hope it works out for you guys.
Dan (near Houston) |
|
Den435
@rr.com | Internet connections speed in Pearland TX for RR are way down, going up and slowing to a halt randomly. Where did the speed go? |
|
CO_Chris
Premium
join:2001-08-28
Broomfield, CO
·Comcast
·Earthlink Cable Mo..
 ·Comcast Digital Vo..
| 2003-11-29 22:09:10 EST: 2973 / 366
Your download speed : 2973843 bps, or 2973 kbps.
A 363 KB/sec transfer rate.
Your upload speed : 366905 bps, or 366 kbps.
Seems like broadband .. above the 1mbit barrier!
I live in Pearland sliver lake area and my speed is down a little just under 3000 but still running great no big deal here.
Speed test was done at Http://hou.speakeasy.net at 9.10 Pm sat night
--
Super Bowl Bound The Houston TEXANS. Well we will have the Super Bowl here this year Anyway |
|
k_m_p
@mindspring.com | My speed is hoses as well. Horrible ping and packet loss. Anyone have any updates?? |
|
jade0010
join:2003-11-25
|  reply to papillon
Yep, Copperfield area of Houston here. Games UNPLAYABLE due to high ping but mainly packet loss! I'm at the end of my rope with this.
SBC is sounding pretty nice right about now. I'd be better off with a 56K than this current RR connection anyway. I'm even experiencing this with a game server located in Dallas. |
|
MogX
Kim Jong
Premium
join:2003-03-30
Pearland, TX
| said by jade0010 :
Yep, Copperfield area of Houston here. Games UNPLAYABLE due to high ping but mainly packet loss! I'm at the end of my rope with this.
SBC is sounding pretty nice right about now. I'd be better off with a 56K than this current RR connection anyway. I'm even experiencing this with a game server located in Dallas.
Lol, I'm pretty glad I didn't get roadrunner now. :| I'm over by Pearland Highschool, alot of my friends are having these same issues with RR, Packetloss/Routing problems/etc. |
|
papillon
join:2002-03-10
Minnetonka, MN | reply to H-Town dude
Again... last night between 7 and 10 pm. A fubared hou.rr router. Trace routes sent to localissues... but they seldom respond. I'll post trace routes hear later tonight. |
|
papillon
join:2002-03-10
Minnetonka, MN
| Again... fubared router somewhere in the tw/aohell network. Are there any RR geeks working on this stuff? Ok... dsl... here we come! |
|
papillon
join:2002-03-10
Minnetonka, MN
| Ok... see? Just after 10pm and all is back to ...normal?
Anyway... This happens every night! |
|
papillon
join:2002-03-10
Minnetonka, MN
| Every F*((ing night! RR tw dorks.... FIX THiS Problem!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
|
papillon
join:2002-03-10
Minnetonka, MN
| UGH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! FIX This...oh...ok I see dsl is available. Will move to the better side of BROADBaND! |
|
Orcin
@207.243.x.x
| I am having the same problem here in Missouri City (near Sugar Land). I play Diablo II on battlenet. Earlier in November, my connection was consistently excellent. Sometime around Thanksgiving, I started having lost packets and very poor response times. It causes me to lag badly in games, even when I am playing alone.
Road Runner of course says that it is my setup, when in fact nothing has changed on my end.
I cannot get DSL in my area, so it looks like I am stuck with this problem. |
|
jgs
join:2003-12-08
Houston, TX
| reply to H-Town dude
Im haven the same issues with my connection. Roadrunner sais they can do nothing about it. Im maken 23 Hops to a dallas ip.
Tracing route to 209.120.238.13 over a maximum of 30 hops
1 15 ms 16 ms ping 209.120.238.13
Pinging 209.120.238.13 with 32 bytes of data:
Reply from 209.120.238.13: bytes=32 time=63ms TTL=49
Reply from 209.120.238.13: bytes=32 time=47ms TTL=49
Reply from 209.120.238.13: bytes=32 time=63ms TTL=49
Reply from 209.120.238.13: bytes=32 time=63ms TTL=49
Ping statistics for 209.120.238.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 63ms, Average = 59ms
That ping used to be under 20ms. Im play games online. Once you get on the servers and play pings jump to like 160 ingame. From what used to be 60-110 at most. I was informed by them that that tracert looks good and is ok. There is nothing they can do. With that kind of performance im moven to the cheaper dsl. I can get just as good or better with dsl for a cheaper price. RR Houston is unwilling to adress the issue with atdn aol. |
|
jgs
join:2003-12-08
Houston, TX
| Tracing route to 209.120.238.13 over a maximum of 30 hops
1 15 ms 16 ms 10 ms 10.48.64.1
2 10 ms 16 ms 10 ms pos5-1.hstntxtid-rtr1.houston.rr.com [24.28.97.6
5]
3 10 ms 15 ms 10 ms srp8-0.hstntxtid-rtr3.texas.rr.com [24.93.33.147
]
4 10 ms 16 ms 10 ms son0-0-3.hstqtxl3-rtr1.texas.rr.com [24.93.33.16
1]
5 10 ms 16 ms 10 ms pop1-hou-P0-1.atdn.net [66.185.133.145]
6 16 ms 10 ms 16 ms bb1-hou-P0-0.atdn.net [66.185.146.96]
7 16 ms 15 ms 16 ms bb1-dls-P6-0.atdn.net [66.185.152.132]
8 16 ms 15 ms 16 ms bb2-dls-P2-0.atdn.net [66.185.153.29]
9 31 ms 16 ms 31 ms bb2-kcy-P6-0.atdn.net [66.185.152.129]
10 15 ms 31 ms 32 ms bb1-kcy-P1-0.atdn.net [66.185.152.126]
11 47 ms 32 ms 46 ms bb1-chi-P6-0.atdn.net [66.185.152.124]
12 31 ms 32 ms 47 ms pop1-chi-P0-0.atdn.net [66.185.141.85]
13 32 ms 31 ms 47 ms bpr2-so-3-0-0.ChicagoEquinix.cw.net [208.174.224
.29]
14 79 ms 78 ms 78 ms 208.174.224.26
15 47 ms 47 ms 47 ms chcgil1wcx2-oc48.wcg.net [64.200.103.117]
16 47 ms 62 ms 47 ms dnvrco1wcx2-pos10-0.wcg.net [64.200.210.66]
17 63 ms 47 ms 47 ms 64.200.108.5
18 63 ms 47 ms 47 ms dllstx1wcx3-pos1-0.wcg.net [64.200.240.213]
19 47 ms 47 ms 47 ms dllstx9lcx1-pos9-0.wcg.net [64.200.232.210]
20 47 ms 46 ms 63 ms dllstx9lcx1-pos6-0.wcg.net [64.200.232.14]
21 47 ms 47 ms 62 ms dllstx9lce1-yipes.wcg.net [64.200.226.118]
22 62 ms 47 ms 47 ms 66.7.164.66
23 47 ms 62 ms 47 ms 209.120.238.13
Trace complete.
jgs |
|
