jdub Posted January 2, 2006 CID Share Posted January 2, 2006 I'm getting anywhere from 1.9 to 2.5 down my upload sucks though last I checked 78kbps wow. I was getting 760 KBs up 2 day ago then something went wrong any suggestions? Tracing route to testmy.net [67.18.179.85] over a maximum of 30 hops: 1 23 ms 22 ms * L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 22 ms 22 ms 22 ms P3-2.LCR-01.STTLWA.verizon-gni.net [130.81.34.10 8] 3 44 ms 43 ms 43 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 44 ms 44 ms 44 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 * * * Request timed out. 6 86 ms * * ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109] 7 86 ms 87 ms 87 ms ae-13-55.car3.Dallas1.Level3.net [4.68.122.143] 8 87 ms * 87 ms 4.78.221.146 9 * 110 ms * vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 10 87 ms 87 ms 87 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83] 11 88 ms 87 ms 104 ms gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.6 9] 12 * 87 ms 88 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. C:DOCUME~1DAD> Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted January 2, 2006 CID Share Posted January 2, 2006 Hello, jdub, and welcome to the forum. Got some timeouts in the trace there, which would explain a speed loss. What are your ISP and advertised speeds? Are you connected to a router? Also, be sure to check out the sticky, found HERE. Quote Link to comment Share on other sites More sharing options...
jdub Posted January 2, 2006 Author CID Share Posted January 2, 2006 ISP is Verizon 3000/768 I use a Linksys BEFSR41 V.3 and I did use the cablenut tweek. Helped a little but not much. Quote Link to comment Share on other sites More sharing options...
Swimmer Posted January 2, 2006 CID Share Posted January 2, 2006 The network is looking kinda crappy from your end.. Looks like Level3 is having routing problems.. again. I would wait a little bit and see if anything clears up.. Level3 is known to do this when they are unhappy about a contract or FCC ruling. Also one other ISP was reporting an outage due to a failed fiber connection. Cogent appears to have a failed fiber connection in the Seattle area. <- this still has yet to be resolved it look like so they have routed to a different backbone.. Quote Link to comment Share on other sites More sharing options...
compuworm Posted January 2, 2006 CID Share Posted January 2, 2006 jdub, after applying the Cablenut/Vanburen tweak did you power cycle your modem and router? Thanks, compuworm Quote Link to comment Share on other sites More sharing options...
jdub Posted January 3, 2006 Author CID Share Posted January 3, 2006 Yes I did but it didn't make a difference, I've tried everything I can think of. How do you decipher the results from the tracert? Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted January 3, 2006 CID Share Posted January 3, 2006 Yes I did but it didn't make a difference, I've tried everything I can think of. How do you decipher the results from the tracert? a * indicates a timeout, meaning that the packet that was sent did not reach the destination before the TTL (time to live) expired. The traceroute shows the path of data from your hardware out through the network. It bypasses the software on your PC, so it shows the actual path of data over your connection. Your traceroute shows many timeouts, indicating that there is either a hardware or a network issue at hand. Quote Link to comment Share on other sites More sharing options...
jdub Posted January 3, 2006 Author CID Share Posted January 3, 2006 Here's another things seem to change constantly Microsoft® Windows DOS ©Copyright Microsoft Corp 1990-2001. C:DOCUME~1DAD>tracert www.testmy.net Tracing route to www.testmy.net [67.18.179.85] over a maximum of 30 hops: 1 22 ms 23 ms 23 ms L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 22 ms 21 ms 22 ms P3-2.LCR-01.STTLWA.verizon-gni.net [130.81.34.10 8] 3 43 ms 43 ms 43 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 * 44 ms 43 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 * 44 ms 44 ms so-3-2-0.bbr2.SanJose1.Level3.net [4.68.121.197] 6 168 ms 86 ms * as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245] 7 88 ms 87 ms 87 ms ae-13-55.car3.Dallas1.Level3.net [4.68.122.143] 8 87 ms * 87 ms 4.78.221.146 9 87 ms 87 ms 87 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 90 ms 87 ms 88 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. C:DOCUME~1DAD> Quote Link to comment Share on other sites More sharing options...
jdub Posted January 3, 2006 Author CID Share Posted January 3, 2006 Microsoft® Windows DOS ©Copyright Microsoft Corp 1990-2001. C:DOCUME~1DAD>tracert www.testmy.net Tracing route to www.testmy.net [67.18.179.85] over a maximum of 30 hops: 1 22 ms 23 ms 23 ms L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 22 ms 21 ms 22 ms P3-2.LCR-01.STTLWA.verizon-gni.net [130.81.34.10 8] 3 43 ms 43 ms 43 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 * 44 ms 43 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 * 44 ms 44 ms so-3-2-0.bbr2.SanJose1.Level3.net [4.68.121.197] 6 168 ms 86 ms * as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245] 7 88 ms 87 ms 87 ms ae-13-55.car3.Dallas1.Level3.net [4.68.122.143] 8 87 ms * 87 ms 4.78.221.146 9 87 ms 87 ms 87 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 90 ms 87 ms 88 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. C:DOCUME~1DAD>tracert www.testmy.net Tracing route to www.testmy.net [67.18.179.85] over a maximum of 30 hops: 1 23 ms 23 ms 23 ms L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 22 ms * 22 ms P3-2.LCR-01.STTLWA.verizon-gni.net [130.81.34.10 8] 3 43 ms 43 ms 43 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 43 ms 44 ms 43 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 43 ms 44 ms 44 ms so-3-2-0.bbr2.SanJose1.Level3.net [4.68.121.197] 6 121 ms 87 ms 86 ms ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109] 7 87 ms 87 ms 87 ms ae-13-53.car3.Dallas1.Level3.net [4.68.122.79] 8 87 ms 86 ms 87 ms 4.78.221.146 9 87 ms * 86 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 10 87 ms * 87 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83] 11 * 88 ms * gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.6 9] 12 88 ms 88 ms 88 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. C:DOCUME~1DAD> Quote Link to comment Share on other sites More sharing options...
jdub Posted January 3, 2006 Author CID Share Posted January 3, 2006 Microsoft® Windows DOS ©Copyright Microsoft Corp 1990-2001. C:DOCUME~1DAD>tracert www.testmy.net Tracing route to www.testmy.net [67.18.179.85] over a maximum of 30 hops: 1 22 ms 23 ms 23 ms L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 22 ms 21 ms 22 ms P3-2.LCR-01.STTLWA.verizon-gni.net [130.81.34.10 8] 3 43 ms 43 ms 43 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 * 44 ms 43 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 * 44 ms 44 ms so-3-2-0.bbr2.SanJose1.Level3.net [4.68.121.197] 6 168 ms 86 ms * as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245] 7 88 ms 87 ms 87 ms ae-13-55.car3.Dallas1.Level3.net [4.68.122.143] 8 87 ms * 87 ms 4.78.221.146 9 87 ms 87 ms 87 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 90 ms 87 ms 88 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. C:DOCUME~1DAD>tracert www.testmy.net Tracing route to www.testmy.net [67.18.179.85] over a maximum of 30 hops: 1 23 ms 23 ms 23 ms L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 22 ms * 22 ms P3-2.LCR-01.STTLWA.verizon-gni.net [130.81.34.10 8] 3 43 ms 43 ms 43 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 43 ms 44 ms 43 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 43 ms 44 ms 44 ms so-3-2-0.bbr2.SanJose1.Level3.net [4.68.121.197] 6 121 ms 87 ms 86 ms ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109] 7 87 ms 87 ms 87 ms ae-13-53.car3.Dallas1.Level3.net [4.68.122.79] 8 87 ms 86 ms 87 ms 4.78.221.146 9 87 ms * 86 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 10 87 ms * 87 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83] 11 * 88 ms * gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.6 9] 12 88 ms 88 ms 88 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. C:DOCUME~1DAD>tracert www.testmy.net Tracing route to www.testmy.net [67.18.179.85] over a maximum of 30 hops: 1 23 ms 22 ms 25 ms L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 22 ms 22 ms * P3-2.LCR-01.STTLWA.verizon-gni.net [130.81.34.10 8] 3 43 ms 43 ms 43 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 44 ms 43 ms 44 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 49 ms 43 ms 44 ms so-3-2-0.bbr2.SanJose1.Level3.net [4.68.121.197] 6 86 ms 86 ms * ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109] 7 87 ms 87 ms * ae-13-55.car3.Dallas1.Level3.net [4.68.122.143] 8 87 ms 87 ms 87 ms 4.78.221.146 9 86 ms 87 ms 87 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 10 * * 87 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83] 11 87 ms 87 ms 87 ms gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.6 9] 12 88 ms * * 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] 13 89 ms 87 ms 88 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. C:DOCUME~1DAD> Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted January 3, 2006 CID Share Posted January 3, 2006 Yeah, but they're consistantly bad. Quote Link to comment Share on other sites More sharing options...
jdub Posted January 4, 2006 Author CID Share Posted January 4, 2006 Well after trying another computer directly plugged to the modem and having the same results I called verizon yesterday. They finally wrote up a trouble ticket for the problem to have the techs take a look. When I got on my computer this morning no internet 3 green light on modem. I rebooted the router and modem. Wnet he check my speed and bam it was back to normal 2.6 down 760 up. Thank for the help guys I guess all the time I spent screwin around was a waste cause the network problem was on there end. Here's hte new tracert Microsoft® Windows DOS ©Copyright Microsoft Corp 1990-2001. C:DOCUME~1DAD>tracert testmy.net Tracing route to testmy.net [67.18.179.85] over a maximum of 30 hops: 1 23 ms 22 ms 22 ms L100.DSL-04.STTLWA.verizon-gni.net [71.113.17.1] 2 23 ms 22 ms 23 ms P3-2.LCR-02.STTLWA.verizon-gni.net [130.81.34.11 0] 3 43 ms 43 ms 44 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130. 81.17.133] 4 44 ms 44 ms 44 ms so-1-2-0-0.e2.SanJose1.Level3.net [4.79.238.5] 5 44 ms 44 ms 44 ms so-3-2-0.bbr2.SanJose1.Level3.net [4.68.121.197] 6 87 ms 87 ms 87 ms ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109] 7 87 ms 87 ms 87 ms ae-23-52.car3.Dallas1.Level3.net [4.68.122.47] 8 87 ms 87 ms 88 ms 4.78.221.146 9 87 ms 87 ms 87 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30] 10 87 ms 88 ms 87 ms vl42.dsr02.dllstx4.theplanet.com [70.85.127.91] 11 115 ms 89 ms 88 ms gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.8 5] 12 88 ms 88 ms 89 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted January 4, 2006 CID Share Posted January 4, 2006 Yes, that looks much better. 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.