dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed

North Tonawanda, NY
·Verizon Online DSL
·Frontier Communi..

1 edit
reply to poo pookie

Re: [Internet] For anyone seeing speed issues...

You did it correctly poo pookie. By the way there is an edit button next to the "Qreply" button on this forum, just in case you didn't see it.

Chutzler, if you can perform the same steps on a wired connection for us to see if things are any better. Also, grab a line quality test if possible too for us.


Martinsburg, WV
Here's a link to my line quality test from a few nights ago...
»/linequality/2 ··· /2667503

Here's the stats from a wired (linux) PC

----------Traceroute to google-------------

traceroute to www.google.com (, 30 hops max, 60 byte packets
1 gateway.home.thfn.org ( 0.545 ms 0.814 ms 1.117 ms
2 ( 9.353 ms 10.745 ms 12.186 ms
3 ( 25.662 ms 26.605 ms 28.047 ms
4 so-5-0-1-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net ( 43.170 ms 44.212 ms 46.055 ms
5 0.so-1-2-0.XL3.IAD8.ALTER.NET ( 48.396 ms 0.so-6-1-0.XL3.IAD8.ALTER.NET ( 49.285 ms 0.ge-7-0-0.XL3.IAD8.ALTER.NET ( 55.171 ms
6 0.so-3-2-0.XL3.NYC4.ALTER.NET ( 61.604 ms 63.300 ms 63.366 ms
7 TenGigE0-4-4-0.GW8.NYC4.ALTER.NET ( 65.101 ms TenGigE0-6-2-0.GW8.NYC4.ALTER.NET ( 40.423 ms TenGigE0-4-1-0.GW8.NYC4.ALTER.NET ( 44.299 ms
8 google-gw.customer.alter.net ( 61.148 ms 62.531 ms 64.188 ms
9 ( 48.404 ms 67.371 ms 67.452 ms
10 ( 52.084 ms 54.524 ms 57.466 ms
11 ( 60.956 ms ( 57.541 ms 70.830 ms
12 iad04s01-in-f103.1e100.net ( 62.576 ms 62.668 ms 43.314 ms
-------------------End traceroute---------------------

-----------------ping results without download-------------

PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=126 time=8.75 ms
64 bytes from icmp_seq=2 ttl=126 time=9.63 ms
64 bytes from icmp_seq=3 ttl=126 time=8.78 ms
64 bytes from icmp_seq=4 ttl=126 time=8.90 ms
64 bytes from icmp_seq=5 ttl=126 time=9.23 ms
64 bytes from icmp_seq=6 ttl=126 time=9.04 ms
64 bytes from icmp_seq=7 ttl=126 time=9.55 ms
64 bytes from icmp_seq=8 ttl=126 time=9.53 ms
64 bytes from icmp_seq=9 ttl=126 time=9.57 ms
64 bytes from icmp_seq=10 ttl=126 time=9.52 ms
64 bytes from icmp_seq=11 ttl=126 time=8.64 ms
64 bytes from icmp_seq=12 ttl=126 time=8.39 ms
64 bytes from icmp_seq=13 ttl=126 time=24.4 ms
64 bytes from icmp_seq=14 ttl=126 time=9.09 ms
64 bytes from icmp_seq=15 ttl=126 time=9.48 ms
64 bytes from icmp_seq=16 ttl=126 time=9.35 ms
64 bytes from icmp_seq=17 ttl=126 time=14.1 ms
64 bytes from icmp_seq=18 ttl=126 time=9.11 ms
64 bytes from icmp_seq=19 ttl=126 time=9.60 ms
64 bytes from icmp_seq=20 ttl=126 time=9.58 ms
64 bytes from icmp_seq=21 ttl=126 time=9.03 ms
64 bytes from icmp_seq=22 ttl=126 time=8.92 ms
64 bytes from icmp_seq=23 ttl=126 time=9.18 ms
64 bytes from icmp_seq=24 ttl=126 time=9.30 ms
64 bytes from icmp_seq=25 ttl=126 time=9.53 ms
64 bytes from icmp_seq=26 ttl=126 time=9.55 ms
64 bytes from icmp_seq=27 ttl=126 time=9.05 ms
64 bytes from icmp_seq=28 ttl=126 time=9.05 ms
64 bytes from icmp_seq=29 ttl=126 time=9.38 ms
------------------------end ping results-------------------------

---------------------ping results during download--------------
64 bytes from icmp_seq=100 ttl=126 time=9.84 ms
64 bytes from icmp_seq=101 ttl=126 time=9.28 ms
64 bytes from icmp_seq=102 ttl=126 time=9.36 ms
64 bytes from icmp_seq=103 ttl=126 time=55.4 ms
64 bytes from icmp_seq=105 ttl=126 time=9.21 ms
64 bytes from icmp_seq=106 ttl=126 time=9.07 ms
64 bytes from icmp_seq=108 ttl=126 time=8.37 ms
64 bytes from icmp_seq=109 ttl=126 time=17.9 ms
64 bytes from icmp_seq=110 ttl=126 time=8.66 ms
64 bytes from icmp_seq=111 ttl=126 time=9.32 ms
64 bytes from icmp_seq=112 ttl=126 time=22.6 ms
64 bytes from icmp_seq=113 ttl=126 time=22.2 ms
64 bytes from icmp_seq=114 ttl=126 time=27.9 ms
64 bytes from icmp_seq=115 ttl=126 time=9.02 ms
64 bytes from icmp_seq=116 ttl=126 time=14.2 ms
64 bytes from icmp_seq=117 ttl=126 time=27.5 ms
64 bytes from icmp_seq=118 ttl=126 time=9.47 ms
64 bytes from icmp_seq=119 ttl=126 time=16.7 ms
64 bytes from icmp_seq=120 ttl=126 time=10.9 ms
64 bytes from icmp_seq=121 ttl=126 time=35.6 ms
64 bytes from icmp_seq=122 ttl=126 time=9.28 ms
64 bytes from icmp_seq=123 ttl=126 time=9.42 ms
64 bytes from icmp_seq=124 ttl=126 time=22.2 ms
64 bytes from icmp_seq=125 ttl=126 time=22.1 ms
64 bytes from icmp_seq=126 ttl=126 time=26.8 ms
64 bytes from icmp_seq=127 ttl=126 time=9.07 ms
64 bytes from icmp_seq=128 ttl=126 time=32.0 ms
64 bytes from icmp_seq=129 ttl=126 time=9.19 ms
64 bytes from icmp_seq=130 ttl=126 time=21.5 ms
64 bytes from icmp_seq=131 ttl=126 time=8.47 ms
64 bytes from icmp_seq=132 ttl=126 time=8.74 ms
64 bytes from icmp_seq=133 ttl=126 time=18.0 ms
64 bytes from icmp_seq=134 ttl=126 time=28.5 ms
64 bytes from icmp_seq=136 ttl=126 time=9.25 ms
64 bytes from icmp_seq=137 ttl=126 time=8.76 ms
64 bytes from icmp_seq=138 ttl=126 time=8.99 ms
64 bytes from icmp_seq=139 ttl=126 time=9.36 ms
64 bytes from icmp_seq=140 ttl=126 time=18.7 ms
64 bytes from icmp_seq=141 ttl=126 time=18.0 ms
64 bytes from icmp_seq=142 ttl=126 time=33.2 ms
64 bytes from icmp_seq=143 ttl=126 time=26.0 ms
64 bytes from icmp_seq=144 ttl=126 time=23.4 ms
64 bytes from icmp_seq=145 ttl=126 time=19.7 ms
64 bytes from icmp_seq=146 ttl=126 time=8.81 ms
64 bytes from icmp_seq=147 ttl=126 time=31.1 ms
64 bytes from icmp_seq=148 ttl=126 time=9.53 ms
64 bytes from icmp_seq=149 ttl=126 time=8.84 ms
64 bytes from icmp_seq=150 ttl=126 time=12.3 ms
64 bytes from icmp_seq=151 ttl=126 time=24.8 ms
64 bytes from icmp_seq=152 ttl=126 time=20.9 ms
64 bytes from icmp_seq=153 ttl=126 time=8.82 ms
64 bytes from icmp_seq=154 ttl=126 time=29.0 ms
64 bytes from icmp_seq=155 ttl=126 time=8.55 ms
64 bytes from icmp_seq=156 ttl=126 time=26.6 ms
64 bytes from icmp_seq=157 ttl=126 time=8.83 ms
64 bytes from icmp_seq=158 ttl=126 time=10.3 ms
64 bytes from icmp_seq=159 ttl=126 time=11.2 ms
64 bytes from icmp_seq=160 ttl=126 time=29.4 ms
64 bytes from icmp_seq=161 ttl=126 time=13.0 ms
64 bytes from icmp_seq=162 ttl=126 time=22.2 ms
64 bytes from icmp_seq=163 ttl=126 time=32.4 ms
64 bytes from icmp_seq=164 ttl=126 time=51.0 ms
64 bytes from icmp_seq=165 ttl=126 time=57.6 ms
64 bytes from icmp_seq=166 ttl=126 time=36.2 ms
64 bytes from icmp_seq=168 ttl=126 time=11.8 ms
64 bytes from icmp_seq=169 ttl=126 time=35.8 ms
64 bytes from icmp_seq=170 ttl=126 time=33.6 ms
----------------------end ping results-----------------------------

Again, the download speed never really stabilizes, it constantly varies between 90k and 220k/sec...Watching the two run together closely shows a correlation between the higher pings and the slowdown, ie. when the ping drops the download speeds up, when the ping goes up, the download slows down.

Also, I did get a call back from Frontier support today, they did say that they would be looking into it over the next couple of days to try and get to the bottom of it......Hopefully they do, as I really can't tolerate this (the wife acceptance factor has plummeted recently as everytime she tries to watch a netflix movie it stutters like crazy.....wifey no happy, me no happy - She makes sure of it lol)

North Tonawanda, NY
·Verizon Online DSL
·Frontier Communi..

4 edits
Your connection to the network is much improved . The DSL line is pinging normally to the network when idle (with a spike here and there which could be from anything at the moment), however the varied speeds and latency at almost idle speeds looks very much like a Juniper ERX being mixed in with a Lucent switch creating an incompatibility, a problem we see a lot at the Verizon DSL forums. Without an RDNS showing for the edge router in your line quality test, it's hard to tell what is the issue. The varied latency the trace route is showing may or may not be normal however, but Gig-E links can run at 10ms latency when fully loaded so that makes it more difficult to troubleshoot without seeing the data from the links themselves.

Can you try running this test below from Ethernet and post up the results you get from it? It's UDP-based so if it is an issue with a Juniper ERX and a Lucent switch, this test will bypass it. If it shows poor results, a link is definitely congested past the DSLAM and edge router (but from edge router to backbone router may be congested). Java is needed.

»www.ispgeeks.com/wild/modules.ph ··· cityTest

If it proves to be a congestion issue, best of luck on getting it resolved.


Martinsburg, WV
Here's the test result from that site. Thanks again for your insight into this.

» ··· d=189857

North Tonawanda, NY
·Verizon Online DSL
·Frontier Communi..
Rather interesting results you got there, but definitely not something I've seen as normal for a DSL connection. You're getting the full amount of bandwidth coming into your line when UDP packets are used at least, though what I find off is how bumping the size up to a rate higher than your connection could sustain threw it off. Here's a test from my 1Mbps Verizon line to compare.

» ··· d=189889

Here's a test from a Verizon Business connection that should be at 1.5Mbps, but is only running slightly above 1Mbps due to that "optimization" nonsense. I ran this over a VNC connection so the results are slightly skewed.

» ··· d=189902

For now until we find out what is going on, I would have to leave it with congestion at the moment.