reno Posted September 2, 2005 CID Share Posted September 2, 2005 Every night now my pings are getting worse and worse, My downloads seem to be okay. Pinging testmy.net [67.18.179.85] with 32 bytes of data: Reply from 67.18.179.85: bytes=32 time=193ms TTL=40 Reply from 67.18.179.85: bytes=32 time=158ms TTL=40 Reply from 67.18.179.85: bytes=32 time=175ms TTL=40 Reply from 67.18.179.85: bytes=32 time=183ms TTL=40 Ping statistics for 67.18.179.85: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 158ms, Maximum = 193ms, Average = 177ms They go up and down all night, during the day though they are fine.. Pinging google.com [216.239.57.99]with 32 bytes of data: Reply from 216.239.57.99: bytes=32 time=224ms TTL=239 Reply from 216.239.57.99: bytes=32 time=239ms TTL=239 Reply from 216.239.57.99: bytes=32 time=234ms TTL=239 Reply from 216.239.57.99: bytes=32 time=212ms TTL=239 Ping statistics for 216.239.57.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 212ms, Maximum = 239ms, Average = 227ms Pinging yahoo.com [216.109.112.135] with 32 bytes of data: Reply from 216.109.112.135: bytes=32 time=142ms TTL=49 Reply from 216.109.112.135: bytes=32 time=165ms TTL=49 Reply from 216.109.112.135: bytes=32 time=131ms TTL=49 Reply from 216.109.112.135: bytes=32 time=157ms TTL=49 Ping statistics for 216.109.112.135: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 131ms, Maximum = 165ms, Average = 148ms And the techs say everything is fine. tracert to yahoo.com Tracing route to yahoo.com [216.109.112.135] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms SVEASOFT [192.168.1.1] 2 15 ms 7 ms 7 ms 10.114.144.1 3 8 ms 8 ms 7 ms fas4-3.bnghnycrn-rtr01.nyroc.rr.com [24.94.34.65 ] 4 17 ms 13 ms 17 ms pos1-2.bnghnyplz-rtr03.nyroc.rr.com [24.94.34.13 ] 5 165 ms 166 ms 163 ms srp8-0.bnghnyplz-rtr02.nyroc.rr.com [24.94.32.90 ] 6 162 ms 155 ms 162 ms son0-0-2.albynywav-rtr03.nyroc.rr.com [24.92.224 .162] 7 155 ms 151 ms 147 ms pop1-alb-P6-0.atdn.net [66.185.133.225] 8 155 ms 147 ms 145 ms bb1-alb-P0-0.atdn.net [66.185.148.96] 9 174 ms 169 ms 162 ms bb2-nye-P3-0.atdn.net [66.185.152.71] 10 153 ms 148 ms 151 ms pop1-nye-P1-0.atdn.net [66.185.151.51] 11 164 ms 167 ms 179 ms DTAG.atdn.net [66.185.137.206] 12 195 ms 201 ms 203 ms 62.154.14.134 13 320 ms 323 ms 316 ms 62.159.124.242 14 236 ms 233 ms 238 ms vlan221-msr2.dcn.yahoo.com [216.115.96.167] 15 248 ms 238 ms 245 ms ge3-1.bas2-m.dcn.yahoo.com [216.109.120.146] 16 227 ms 223 ms 239 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135] To testmy.net Tracing route to testmy.net [67.18.179.85] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms SVEASOFT [192.168.1.1] 2 7 ms 8 ms 7 ms 10.114.144.1 3 9 ms 6 ms 6 ms fas4-3.bnghnycrn-rtr01.nyroc.rr.com [24.94.34.65 ] 4 166 ms 167 ms 166 ms pos0-0.bnghnycpe-rtr04.nyroc.rr.com [24.94.32.29 ] 5 168 ms 173 ms 164 ms srp8-0.bnghnyplz-rtr02.nyroc.rr.com [24.94.32.90 ] 6 178 ms 176 ms 178 ms son0-0-2.albynywav-rtr03.nyroc.rr.com [24.92.224 .162] 7 186 ms 194 ms 191 ms pop1-alb-P7-0.atdn.net [66.185.133.229] 8 205 ms 200 ms 185 ms bb1-alb-P0-0.atdn.net [66.185.148.96] 9 176 ms 180 ms 183 ms bb2-nye-P3-0.atdn.net [66.185.152.71] 10 190 ms 190 ms 185 ms pop1-nye-P1-0.atdn.net [66.185.151.51] 11 184 ms 184 ms 184 ms GlobalCrossing.atdn.net [66.185.151.62] 12 256 ms 283 ms 242 ms so1-0-0-2488m.ar1.dal2.gblx.net [67.17.73.34] 13 235 ms 230 ms 233 ms The-Planet.ge-4-3-0.ar1.DAL2.gblx.net [64.210.10 4.58] 14 239 ms 231 ms 229 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30] 15 215 ms 210 ms 217 ms dist-vlan-42.dsr2-2.dllstx4.theplanet.com [70.85 .127.91] 16 232 ms 228 ms 228 ms gig1-0-2.tp-car9-1.dllstx4.theplanet.com [67.18. 116.85] 17 225 ms 231 ms 218 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Quote Link to comment Share on other sites More sharing options...
xs1 Posted September 8, 2005 CID Share Posted September 8, 2005 Mines doin teh same Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and Settings.s1>tracert mindspring.com Tracing route to mindspring.com [207.69.189.26] over a maximum of 30 hops: 1 32 ms 100 ms 133 ms 192.168.1.1 2 94 ms 84 ms 2666 ms 10.126.144.1 3 * 1443 ms * atm5-0-744.tampflerl-rtr2.tampabay.rr.com [24.92.7.46] 4 * 343 ms * pos6-0-OC-192.tampflerl-rtr4.tampabay.rr.com [65.32.8.137] 5 Quote Link to comment Share on other sites More sharing options...
JustinOhioRR Posted September 8, 2005 CID Share Posted September 8, 2005 I have to say..........my rr seems to be shitty lately too.......i have tweaked my new setup and i can only download about 1.5 mbps.....not right.... i dont know what the problem is, but we are moving and i need internet, i think they may lose a customer if this keeps up.... Quote Link to comment Share on other sites More sharing options...
reno Posted September 13, 2005 Author CID Share Posted September 13, 2005 Wow this is just insanly retarted. Road Runner is all messed up.. Pinging yahoo.com [66.94.234.13] with 32 bytes of data: Reply from 66.94.234.13: bytes=32 time=635ms TTL=46 Reply from 66.94.234.13: bytes=32 time=648ms TTL=47 Reply from 66.94.234.13: bytes=32 time=639ms TTL=47 Reply from 66.94.234.13: bytes=32 time=614ms TTL=46 Ping statistics for 66.94.234.13: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 614ms, Maximum = 648ms, Average = 634ms Tracing route to yahoo.com [66.94.234.13] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms SVEASOFT [192.168.1.1] 2 9 ms 7 ms 5 ms 10.114.144.1 3 7 ms 7 ms 7 ms fas4-3.bnghnycrn-rtr01.nyroc.rr.com [24.94.34.65 ] 4 15 ms 14 ms 13 ms pos1-2.bnghnyplz-rtr03.nyroc.rr.com [24.94.34.13 ] 5 541 ms 532 ms 544 ms srp8-0.bnghnyplz-rtr02.nyroc.rr.com [24.94.32.90 ] 6 556 ms 573 ms 571 ms son0-0-2.albynywav-rtr03.nyroc.rr.com [24.92.224 .162] 7 540 ms 522 ms 526 ms pop1-alb-P7-0.atdn.net [66.185.133.229] 8 528 ms 534 ms 528 ms bb2-alb-P1-0.atdn.net [66.185.133.238] 9 558 ms 554 ms 554 ms bb1-new-P5-0.atdn.net [66.185.152.194] 10 566 ms 574 ms 528 ms bb1-ash-P13-0.atdn.net [66.185.152.48] 11 545 ms 559 ms 536 ms pop3-ash-P0-0.atdn.net [66.185.148.209] 12 507 ms 530 ms 514 ms if-10-0.core1.AEQ-Ashburn.teleglobe.net [63.243. 149.97] 13 492 ms 515 ms 518 ms ix-14-2.core1.AEQ-Ashburn.teleglobe.net [63.243. 149.110] 14 569 ms 558 ms 553 ms so-3-1-0.pat1.pao.yahoo.com [216.115.101.128] 15 605 ms 618 ms 610 ms ge-1-0-3.msr1.scd.yahoo.com [66.218.82.197] 16 625 ms 603 ms 577 ms UNKNOWN-66-218-82-217.yahoo.com [66.218.82.217] 17 554 ms 557 ms 569 ms w2.rc.vip.scd.yahoo.com [66.94.234.13] Trace complete. ________________________________________________________________________________________- Pinging testmy.net [67.18.179.85] with 32 bytes of data: Reply from 67.18.179.85: bytes=32 time=578ms TTL=40 Reply from 67.18.179.85: bytes=32 time=603ms TTL=40 Reply from 67.18.179.85: bytes=32 time=603ms TTL=40 Reply from 67.18.179.85: bytes=32 time=596ms TTL=40 Ping statistics for 67.18.179.85: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 578ms, Maximum = 603ms, Average = 595ms Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted September 13, 2005 CID Share Posted September 13, 2005 That node on the fifth hop is messed. Try disconnecting the power to your modem (and router if you use one) for a few minutes then power back up to see if you can find a better CMTS node to join. How long has this been happening reno? Sometimes a node will go down in NYC and the traffic has to be routed between the ones remaining and speeds will drop a lot. Quote Link to comment Share on other sites More sharing options...
reno Posted September 13, 2005 Author CID Share Posted September 13, 2005 Well from what I heard they are upgrading a node and the speeds are gonig to be back for a few weeks. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.