 azume
join:2007-01-03 Rochester, NY
| [TWC] Anyone in Rochester, NY having latency issues?
»/linequality/nil/2404310
line quality test shows just high latency but little/no packet loss?
Any ideas what could be causing this? It's fine during the day but once 6pm EST hits it gets terrible until about 1am EST. No router - it's directly connected modem to pc. |
|
  Stray Bullet Dangerous? Premium join:2004-04-03 Rochester, NY | Not you man, I just made a post the same time you did...
»[TWC] [Rochester] Oh my ping!!! |
|
  hobgoblin Sortof Agoblin Premium join:2001-11-25 Orchard Park, NY clubs: | reply to azume Give em a call....Try to get to tier 3.
Hob |
|
 azume
join:2007-01-03 Rochester, NY
| reply to Stray Bullet Seems to have been happening since about Wednesday. I have guy coming out to take a look at it tomorrow but between 12-4pm, so i don't think it will do any good.
Can't raid tonight (WoW) with 600ms+  |
|
  hobgoblin Sortof Agoblin Premium join:2001-11-25 Orchard Park, NY clubs: | Looking at that trace I doubt there is ANYTHING he can do.
hob |
|
  Stray Bullet Dangerous? Premium join:2004-04-03 Rochester, NY
| reply to azume Just getting worse too...
C:\Documents and Settings\Stray>tracert 208.167.245.46
Tracing route to 208.167.245.46.choopa.net [208.167.245.46] over a maximum of 30 hops:
1 2 ms 1 ms 1 ms router.critical-damage.com [192.168.1.1] 2 11 ms 8 ms 9 ms 10.241.0.1 3 8 ms 10 ms 9 ms gig4-2.rochnygts-rtr01.nyroc.rr.com [24.93.4.149] 4 324 ms 316 ms 333 ms srp7-0.rochnymth-rtr03.nyroc.rr.com [24.93.3.119] 5 359 ms 340 ms 335 ms ge-7-3-0.syrcnycsr-rtr03.nyroc.rr.com [24.92.224.10] 6 331 ms 329 ms 354 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72] 7 362 ms 336 ms 330 ms ae-0-0.cr0.chi30.tbone.rr.com [66.109.6.21] 8 347 ms 330 ms 350 ms ae-4-0.cr0.nyc20.tbone.rr.com [66.109.6.24] 9 356 ms 358 ms 367 ms ae-0-0.pr0.nyc30.tbone.rr.com [66.109.6.159] 10 360 ms 187 ms 160 ms t4-2.ar1.ewr1.us.nlayer.net [69.31.94.57] 11 372 ms 377 ms 379 ms choopa.tge1-2.ar1.ewr1.us.nlayer.net [69.31.95.90] 12 368 ms 381 ms 377 ms p-tge1-4-cr2.ewr2.Choopa.net [64.237.32.46] 13 356 ms 369 ms 360 ms 208.167.245.46.choopa.net [208.167.245.46]
Trace complete. -- Kill With The Best... Or Die Like The Rest... Critical Damage Incorporated...Visit Us Here! |
|
 thevorpal
join:2007-11-16 Endicott, NY
| reply to azume From Binghamton I'm not seeing any latency issues, though videos streamed from youtube and similar services have taken a DRASTIC hit in the last 3 days for me.
Not sure if this will help for your comparisons, but here it is anyway.
|
|
  liquidred4
@rr.com
| reply to azume Having major latency in Rochester as well, although it seems like the albany hop is what is killing my connection. Already got a ticket open with T3 support, but they close at 8pm so i gotta call tomorrow
2 9 ms 9 ms 10 ms 10.122.208.1 3 12 ms 9 ms 7 ms gig1-1.rochnyrga-rtr01.nyroc.rr.com [24.93.4.69] 4 13 ms 16 ms 10 ms srp2-0.rochnybtn-rtr01.nyroc.rr.com [24.93.3.120] 5 352 ms 361 ms 333 ms ge-6-0-0.albynywav-rtr03.nyroc.rr.com [24.92.224.122] 6 367 ms 341 ms 329 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74] 7 338 ms 330 ms 331 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28] 8 356 ms 362 ms 354 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165] 9 292 ms 294 ms 264 ms 66.109.9.66 10 279 ms 302 ms 301 ms 216.239.48.108 11 326 ms 386 ms 360 ms 209.85.248.221 12 344 ms 371 ms 360 ms 72.14.238.89 13 388 ms 385 ms 381 ms 64.233.175.26 14 389 ms 394 ms 383 ms py-in-f99.google.com [64.233.167.99] |
|
  jcleve
@rr.com
| reply to azume Yeah, lots of latency issues, at the same router you guys are seeing problems at - 24.93.3.119
And of course, dunderhead TW tech support. After putting up with this peak usage time problem for the last week, I finally sent this message yesterday to ....
In the past week or two, internet access has been very slow in evenings. I assumed it would clear up, but it hasn't. Below is a copy of a Tracert I ran to Yahoo.com. As you can see, latency is VERY high at the third hop - it jumps to 300 Ms while still within the local RR network. If your techs could look into this, it would be appreciated.
Tracing route to www.yahoo-ht3.akadns.net [69.147.76.15] over a maximum of 30 hops:
1 9 ms 9 ms 18 ms 10.108.64.1 2 10 ms 11 ms 11 ms pos0-2.rochnystf-rtr01.nyroc.rr.com [24.93.2.85]
3 294 ms 292 ms 306 ms srp7-0.rochnymth-rtr03.nyroc.rr.com [24.93.3.119 ] 4 301 ms 294 ms 302 ms ge-7-3-0.syrcnycsr-rtr03.nyroc.rr.com [24.92.224 .10] 5 325 ms 330 ms 329 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72] 6 336 ms 328 ms 321 ms ae-0-0.cr0.chi30.tbone.rr.com [66.109.6.21] 7 330 ms 331 ms 333 ms ae-4-0.cr0.nyc20.tbone.rr.com [66.109.6.24] 8 348 ms 347 ms 358 ms ae-0-0.cr0.nyc30.tbone.rr.com [66.109.6.26] 9 356 ms 347 ms 357 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28] 10 357 ms 343 ms 351 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.167] 11 355 ms 338 ms 376 ms 66.109.9.165 12 360 ms 345 ms 347 ms ae1-p161.msr1.re1.yahoo.com [216.115.108.27] 13 83 ms 92 ms 104 ms ge-1-43.bas-a2.re3.yahoo.com [66.196.112.205] 14 343 ms 339 ms 336 ms f1.www.vip.re1.yahoo.com [69.147.76.1, [/] Now, how could someone with even the slightest knowledge of the internet think this problem is in any way "local" to my machine? The logjam is CLEARLY at this ip - 24.93.3.119
Answer - Time Warner's robotic tech support - They sent me the standard "clear your browser's cache" response. Jeebus - don't they know that Tracert is a DOS function - it's totally independent of Firefox, or IE, or any browser?!
So I sent them ANOTHER e-mail tonight - rather than fight city hall, I told them "their suggestions didn't solve the problem" and another Tracert. The problem is still the same tonight
These steps did not help the problem. Here is a tracert I ran tonight at 9:41 PM Eastern time, to Yahoo.com. As you can see, the problem begins at IP 24.93.3.119, 3 srp7-0.rochnymth-rtr03.nyroc.rr.com. This evidently is one of the Rochester Road Runner network's servers. It's definitely NOT at my house, or at the first local node, as the first two hops, from my modem to the first node, only have a combined latency of 10 ms. Again, this problem only has been occurring during peak usage times. The network and my connection speed is fine during the daytime. It appears to be demand-related.
Thanks for your help.
Jim
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>tracert www.yahoo.com
Tracing route to www.yahoo-ht3.akadns.net [69.147.76.15] over a maximum of 30 hops:
1 9 ms 9 ms 9 ms 10.108.64.1 2 9 ms 9 ms 10 ms pos0-2.rochnystf-rtr01.nyroc.rr.com [24.93.2.85]
3 341 ms 334 ms 340 ms srp7-0.rochnymth-rtr03.nyroc.rr.com [ ] 4 347 ms 315 ms 310 ms ge-7-3-0.syrcnycsr-rtr03.nyroc.rr.com [24.92.224 .10]
Maybe they'll finally start to fix the problem, considering I'm not the only one reporting it. |
|
  hobgoblin Sortof Agoblin Premium join:2001-11-25 Orchard Park, NY clubs: | Sending an email is not the best way to do this. Call locally and try to get to the Tier 3 group.
They should know.
Hob -- "A foolish consistency is the hobgoblin of little minds." - Ralph Waldo Emerson
|
|
 pepsiaddict
join:2007-10-31 Rochester, NY
| reply to azume Here are my results ... things have been off and on a little on the slow side tonight where I am (border of Brighton/Henrietta).
Tracing route to google.com [64.233.187.99] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 13 ms 14 ms 11 ms 10.109.192.1 3 17 ms 13 ms 15 ms gig8-0-2.rochnybtn-rtr01.nyroc.rr.com [24.93.0.2 17] 4 57 ms 27 ms 23 ms ge-6-0-0.albynywav-rtr03.nyroc.rr.com [24.92.224 .122] 5 28 ms 25 ms 20 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74] 6 46 ms 50 ms 52 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28] 7 36 ms 36 ms 31 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165] 8 33 ms 29 ms 28 ms 66.109.9.66 9 37 ms 42 ms 31 ms 216.239.48.110 10 63 ms 46 ms 43 ms 72.14.238.136 11 43 ms 47 ms 54 ms 72.14.236.15 12 68 ms 49 ms 56 ms 216.239.49.226 13 59 ms 64 ms 55 ms jc-in-f99.google.com [64.233.187.99]
Trace complete. |
|
 azume
join:2007-01-03 Rochester, NY | This is getting ridiculous how it's from 6pm EST to 1am EST or so. all day long it's fine until then :\ |
|
  jcleve
@rr.com
| haha, I e-mailed RR's alleged tech support a second tracert last night. Their response?
"Dear Jim,
Thank you for contacting Time Warner Cable Road Runner E-mail Support.
As per your response, I understand that you are experiencing slow connectivity issue from last 2 weeks and the tracert result shows that it has more than 300ms in Road Runner network.
Jim, I would suggest that reset the modem and then check if you have any issue with the connection and perform the tracert again and if you still have the issue. In this regard, you will need to contact our concerned department, since they are specifically trained to resolve such issues. I will provide you the contacts details.
RESET CABLE MODEM
To ensure the information the modem is providing to your computer is accurate, its memory must be reset. If you have a router connected to your cable modem, you must disconnect the router to verify it is not the cause of or a contributor to the problem. After disconnecting the router and unplugging its power the modem must be reset. Do this by unplugging the modem's power cable from the wall socket for two minutes; when the power is plugged back in and the "Cable" or "Online" light stops lashing and remains on, turn on or restart the computer. This process synchronizes the information between our network, the cable modem, and your computer."
Yeah, resetting MY modem will do a lot of good when the problem is CLEARLY a node 30-40 miles from my home.
Why is TW's tech support so inept? You would think if multiple subscribers are complaining about the SAME problem, someone would be able to connect the dots.
And why is the national help desk unable to communicate effectively with local tech support? If the national help desk simply forwarded all the submitted tracerts to Level 3 support in Rochester, they could quickly identify and begin to resolve the issue.
Undoubtedly, if I call them, I'll have to go thru all that canned and totally ineffective horseshit of clearing the browser cache, resetting the modem, blah blah blah
I've seen these latency issues occur numerous times in the nearly 10 years I've had Roadrunner. Every time, the subscriber has to go through this silly dance with tech support to get the issue resolved. |
|
 themmeri
join:2008-07-08 Rochester, NY | reply to azume I Know they are having alot of issues down by the lake right now.Power outages ect. But that was since last night. Air conditioners sucking power from servers? LOL |
|
  Stray Bullet Dangerous? Premium join:2004-04-03 Rochester, NY
| reply to jcleve said by jcleve :
Now, how could someone with even the slightest knowledge of the internet think this problem is in any way "local" to my machine? The logjam is CLEARLY at this ip - 24.93.3.119
Yeah every time this happens & I call.... It has something to do with my machine behind a router... Even though I sent them a tracert & it obviously shows it is one of the routers in their network.
I think it is funny the responses I receive when they ask me to connect my computer directly into the cable modem & I tell them I will not do so as it may compromise security.
Anyways It cleared up about 1:30 am.  -- Kill With The Best... Or Die Like The Rest... Critical Damage Incorporated...Visit Us Here! |
|
  jcleve
@rr.com
| The high latency is starting already - 4:11 PM.
1 * * 10 ms 10.108.64.1 2 10 ms 10 ms 9 ms pos0-2.rochnystf-rtr01.nyroc.rr.com [24.93.2.85]
3 103 ms 102 ms 100 ms srp7-0.rochnymth-rtr03.nyroc.rr.com [24.93.3.119
4 121 ms 116 ms 130 ms ge-7-3-0.syrcnycsr-rtr03.nyroc.rr.com [24.92.224 10]
TW's "tech support" is laughable. The issue is clearly NOT with the individual subscribers computers, and directly related to their own network.
This problem began a couple weeks ago - there was a service outage of everything - digital phone, digital cable, Roadrunner, for 2 or 3 hours during the day. Ever since then, this latency problem has started cropping up. It might have something to do with their repairs.
I will call them tonight, though, when it's worse. They've been informed by numerous Rochester area users of this problem and done squat. So it's time they got taken to task, and a formal complaint filed.
There used to be a Rochester.Roadrunner.Feedback news group - and one of the level 3 techs would read the page. But now of course TW has discontinued News Group service, so even that avenue is non-existent. Now we're forced to call people that read from scripts, and can't think outside the box.
|
|
  Mazakman
join:2001-06-24 Webster, NY
·RoadRunner Cable
·FrontierNet Intern..
·AT&T CallVantage
| Just did this tracert from here in West Webster...
Tracing route to www.yahoo-ht3.akadns.net [69.147.76.15] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.x.x 2 9 ms 8 ms 7 ms 10.109.48.1 3 14 ms 7 ms 8 ms gig3-0.rochnywbs-rtr01.nyroc.rr.com [24.93.2.117 ] 4 9 ms 9 ms 9 ms srp5-0.rochnymth-rtr03.nyroc.rr.com [24.93.3.161 ] 5 18 ms 16 ms 18 ms ge-7-3-0.syrcnycsr-rtr03.nyroc.rr.com [24.92.224 .10] 6 34 ms 36 ms 38 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72] 7 34 ms 33 ms 39 ms ae-0-0.cr0.chi30.tbone.rr.com [66.109.6.21] 8 45 ms 45 ms 48 ms ae-4-0.cr0.nyc20.tbone.rr.com [66.109.6.24] 9 46 ms 43 ms 43 ms ae-0-0.cr0.nyc30.tbone.rr.com [66.109.6.26] 10 50 ms 53 ms 51 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28] 11 51 ms 52 ms 51 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.167] 12 53 ms 67 ms 53 ms 66.109.9.163 13 54 ms 108 ms 57 ms ae1-p170.msr2.re1.yahoo.com [216.115.108.29] 14 52 ms 57 ms 55 ms ge-1-44.bas-a2.re3.yahoo.com [66.196.112.207] 15 52 ms 49 ms 57 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
Trace complete. |
|
  Stray Bullet Dangerous? Premium join:2004-04-03 Rochester, NY
| reply to azume yeah it is not as bad now but my ping is still going crazy jumping around from 30 to 120 ping in game...
Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Stray>tracert 208.167.245.46
Tracing route to 208.167.245.46.choopa.net [208.167.245.46] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.critical-damage.com [192.168.1.1] 2 12 ms 9 ms 9 ms 10.241.0.1 3 9 ms 11 ms 13 ms gig4-2.rochnygts-rtr01.nyroc.rr.com [24.93.4.149] 4 38 ms 42 ms 48 ms srp7-0.rochnymth-rtr03.nyroc.rr.com [24.93.3.119] 5 54 ms 53 ms 54 ms ge-7-3-0.syrcnycsr-rtr03.nyroc.rr.com [24.92.224.10] 6 60 ms 62 ms 64 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72] 7 68 ms 69 ms 67 ms ae-0-0.cr0.chi30.tbone.rr.com [66.109.6.21] 8 67 ms 78 ms 62 ms ae-4-0.cr0.nyc20.tbone.rr.com [66.109.6.24] 9 87 ms 89 ms 94 ms ae-0-0.pr0.nyc30.tbone.rr.com [66.109.6.159] 10 57 ms 47 ms 66 ms tge4-2.ar1.ewr1.us.nlayer.net [69.31.94.57] 11 70 ms 68 ms 69 ms as20473.vl103.ar1.ewr1.us.nlayer.net [69.31.95.90] 12 67 ms 72 ms 73 ms p-tge1-4-cr2.ewr2.Choopa.net [64.237.32.46] 13 82 ms 90 ms 87 ms 208.167.245.46.choopa.net [208.167.245.46]
Trace complete.
C:\Documents and Settings\Stray> -- Kill With The Best... Or Die Like The Rest... Critical Damage Incorporated...Visit Us Here! |
|
  Mazakman
join:2001-06-24 Webster, NY
·RoadRunner Cable
·FrontierNet Intern..
·AT&T CallVantage
| Just to compare...
Tracing route to 208.167.245.46.choopa.net [208.167.245.46] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.x.x 2 9 ms 8 ms 8 ms 10.109.48.1 3 8 ms 14 ms 7 ms gig3-0.rochnywbs-rtr01.nyroc.rr.com [24.93.2.117 ] 4 9 ms 9 ms 9 ms srp5-0.rochnymth-rtr03.nyroc.rr.com [24.93.3.161 ] 5 18 ms 17 ms 17 ms ge-7-3-0.syrcnycsr-rtr03.nyroc.rr.com [24.92.224 .10] 6 37 ms 34 ms 35 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72] 7 36 ms 39 ms 38 ms ae-0-0.cr0.chi30.tbone.rr.com [66.109.6.21] 8 46 ms 46 ms 47 ms ae-4-0.cr0.nyc20.tbone.rr.com [66.109.6.24] 9 48 ms 50 ms 48 ms ae-0-0.pr0.nyc30.tbone.rr.com [66.109.6.159] 10 102 ms 130 ms 50 ms tge4-2.ar1.ewr1.us.nlayer.net [69.31.94.57] 11 48 ms 44 ms 54 ms as20473.vl103.ar1.ewr1.us.nlayer.net [69.31.95.9 0] 12 46 ms 47 ms 50 ms p-tge1-4-cr2.ewr2.Choopa.net [64.237.32.46] 13 47 ms 47 ms 48 ms 208.167.245.46.choopa.net [208.167.245.46]
Trace complete. |
|
 azume
join:2007-01-03 Rochester, NY | reply to azume Still crappy at this hour. 7pm EST or so things just started to rise in the latency dept.  |
|