dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
55991
share rss forum feed


Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23
Reviews:
·Verizon Online DSL
·Frontier Communi..

3 edits

1 recommendation

[Internet] For anyone seeing speed issues...

Hello guys. I figured I'd help get to the bottom of what these slow speed issues might be as I have been doing in other threads. At the moment I'm still piecing together what may be wrong, however I need anyone who is seeing slower than normal speeds to please perform what I'm asking below. I've seen some funny things happen with speeds when the edge routers are configured in an odd way (as in, they don't match your speed profile for your line) and knowing the transition, it's always possible Frontier has been messing with them.

***PLEASE NOTE: If your line has been found to be out-of-sync, you do not need to run this test***

1: Run a trace route to a site such as google.com and locate the first hop outside of your network. If you are behind a router or a modem which serves up addresses such as 192.168.1.1, Hop 2 should be your ISP's network. You can also tell where the ISP's network first begins by looking at the latency. Any latency above 1 millisecond on an Ethernet network will generally indicate that the data has left your internal network.

2: Once you have found the first hop onto your ISP's network, take note of the IP address. Using a ping program (such as command prompt in Windows or the "Ping" command in Linux-based systems), ping that IP address continuously and observe the latency (In Windows, you can use -t to tell it to continuously ping that address. An example of how this would be entered into command prompt would be ping 10.15.3.1 -t ). For the most part, a DSL connection running under FastPath with no load should maintain a consistent latency of 16ms or less, ideally 10ms or less. For Interleaved connections with no load, the latency should be consistently at or around 26ms. Also, a DSL connection should also never drop packets to the first hop when idle. Please take note of the latency you see while the pinging is taking place. Leave the program pinging this hop and proceed to the next step.

3: Locate a large file to download on a server close to you. It must be a consistent server that is not prone to dips in speed. A file you may try can be found at »cachefly.cachefly.net/100mb.test . Please note that you do not need to download the entire file. We just need to let it run until we can gather some additional data.

4: Once the file download has begun and is up to as high of a speed as it will go (may take a few seconds to hit top speed), go back to the program that is pinging the first hop to the ISP and observe the latency. Keep an eye on the speed of your download as well to make sure it remains consistent at the speed it landed at. Please take note of the latency now as it is downloading, and if you are seeing any packet loss (or failed pings) while it is downloading.

5: Stop the download and end the program that is pinging the first hop to the ISP, and post up a couple of samples in this topic of what latency you saw while the connection was idle, and what the latency was while you were downloading and the top speed the download hit as well as if any pings failed. Please also provide what package you are paying for.

I'm hoping this will help us discover something something wrong.


poo pookie

join:2010-08-09

Ok I think you went beyond the geek in me.

1. How Do I do a trace route?

2. How do I use the command prompt to ping an address continously?

I think I understand how to do the rest of the things, but may ask more questions if I screw it up somehow.



grobinette
Southeast of disorder
Premium,Mod
join:2001-01-27
Springfield, VA
kudos:1

This should help.

»Site FAQ »How do I run a traceroute and post the results in the forums?

»Malaysian TMnet Streamyx DSL »What is PING and how do I do it?


poo pookie

join:2010-08-09
reply to Smith6612

Thanks for the info grobinette

Please note my phone line has not been repaired yet, but I did want to do this to see if there is any difference after the line is fixed.

I hope I did it correct.

ok here is my trace route stats

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms Idle stats

Reply from 10.34.54.1: bytes=32 time=56ms TTL=126
Reply from 10.34.54.1: bytes=32 time=55ms TTL=126
Reply from 10.34.54.1: bytes=32 time=54ms TTL=126
Reply from 10.34.54.1: bytes=32 time=57ms TTL=126
Reply from 10.34.54.1: bytes=32 time=56ms TTL=126
Reply from 10.34.54.1: bytes=32 time=54ms TTL=126
Reply from 10.34.54.1: bytes=32 time=53ms TTL=126
Reply from 10.34.54.1: bytes=32 time=56ms TTL=126
Reply from 10.34.54.1: bytes=32 time=55ms TTL=126
Reply from 10.34.54.1: bytes=32 time=54ms TTL=126
Reply from 10.34.54.1: bytes=32 time=53ms TTL=126
Reply from 10.34.54.1: bytes=32 time=56ms TTL=126
Reply from 10.34.54.1: bytes=32 time=55ms TTL=126
Reply from 10.34.54.1: bytes=32 time=54ms TTL=126
Reply from 10.34.54.1: bytes=32 time=57ms TTL=126

Stats from when I was downloading

Reply from 10.34.54.1: bytes=32 time=817ms TTL=126
Reply from 10.34.54.1: bytes=32 time=792ms TTL=126
Reply from 10.34.54.1: bytes=32 time=803ms TTL=126
Reply from 10.34.54.1: bytes=32 time=814ms TTL=126
Reply from 10.34.54.1: bytes=32 time=824ms TTL=126
Reply from 10.34.54.1: bytes=32 time=811ms TTL=126
Reply from 10.34.54.1: bytes=32 time=818ms TTL=126
Reply from 10.34.54.1: bytes=32 time=793ms TTL=126
Reply from 10.34.54.1: bytes=32 time=800ms TTL=126
Reply from 10.34.54.1: bytes=32 time=810ms TTL=126
Reply from 10.34.54.1: bytes=32 time=821ms TTL=126
Reply from 10.34.54.1: bytes=32 time=832ms TTL=126
Reply from 10.34.54.1: bytes=32 time=803ms TTL=126
Reply from 10.34.54.1: bytes=32 time=814ms TTL=126
Reply from 10.34.54.1: bytes=32 time=824ms TTL=126
Reply from 10.34.54.1: bytes=32 time=795ms TTL=126
Reply from 10.34.54.1: bytes=32 time=806ms TTL=126
Reply from 10.34.54.1: bytes=32 time=816ms TTL=126
Reply from 10.34.54.1: bytes=32 time=827ms TTL=126
Reply from 10.34.54.1: bytes=32 time=838ms TTL=126


poo pookie

join:2010-08-09

gah really need an edit post option here

my trace route didn't paste correctly

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dslrouter.westell.com [192.168.1.1]
2 53 ms 55 ms 51 ms 10.34.54.1
3 52 ms 55 ms 51 ms so-1-2-2-0.CHI01-CORE-RTR1.verizon-gni.net [108.
57.128.8]
4 54 ms 55 ms 55 ms as0-0.CHI01-BB-RTR1.verizon-gni.net [130.81.20.5
6]
5 52 ms 55 ms 55 ms 0.ge-6-3-0.XL3.CHI13.ALTER.NET [152.63.65.129]
6 56 ms 55 ms 55 ms TenGigE0-6-1-0.GW2.CHI13.ALTER.NET [152.63.65.13
3]
7 52 ms 55 ms 55 ms teliasonera-gw.customer.alter.net [157.130.107.1
22]
8 76 ms 79 ms 75 ms nyk-bb2-link.telia.net [80.91.246.165]
9 80 ms 79 ms 79 ms nyk-b3-link.telia.net [80.91.248.174]
10 76 ms 79 ms 79 ms netaccess-tic-133837-nyk-b3.c.telia.net [213.248
.99.90]
11 84 ms 87 ms 83 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
12 79 ms 79 ms 79 ms 0.e1-1.tbr1.oct.nac.net [209.123.10.17]
13 79 ms 79 ms 83 ms vlan804.esd1.oct.nac.net [209.123.10.2]
14 82 ms 83 ms 79 ms www.dslreports.com [209.123.109.175]

Trace complete.


poo pookie

join:2010-08-09
reply to Smith6612

oops forgot to post what I am paying for Well I was and have been paying for 3 mb for two years. But since the rotten people dropped my speed on me I have no idea what I am paying for I haven't gotten a bill yet since they screwed with it.

They keep telling me they dropped it to 1.5, but the field tech told me they dropped it to 1 and when I look at what I am connected at it is 100.00 Mbps


gozer
Premium
join:2010-08-09
Rochester, NY

1 edit
reply to Smith6612

Hello I wanted to do something like this to test peoples dsl and many people had a hard time understanding how to do this.
so this may help, I know this works for xp not sure about vista and win7.
have them copy this and past in the run box.

cmd /k tracert -d -h 5 yahoo.com >> c:\traceip.txt
it will run and create and write the trace of first 5 hops to a file in c:\traceip.txt

they can then just edit this line and run it from the run box too and get a txt file they can copy to past thier results here

cmd /k ping -n 50 -w 1000 xxx.xxx.xxx.xxx >> c:\pinghop1.txt

One other thing that may interest everyone. I havew had same trouble with frontiernet and this, and the first hop and its allmost imposible to get support to do anything about it. They say we dont garanty latency/timing.
But it realy hurts people that game when you get lots of jitter,
and in my opinion this shouldnt happen so close to home.
means thier not doing thier job and providing people with what I consider to be a stable dsl line. so Im looking forward to seeing some of peoples results on this problem.


chutzler

join:2010-08-14
Martinsburg, WV
reply to Smith6612

--------TRACEROUTE---------

traceroute to www.l.google.com (72.14.204.103), 64 hops max, 52 byte packets
1 gateway (10.10.10.1) 4.274 ms 3.996 ms 5.292 ms
2 10.8.7.1 (10.8.7.1) 9.860 ms 12.441 ms 9.906 ms
3 184.19.255.24 (184.19.255.24) 20.666 ms 24.187 ms 25.084 ms
4 so-5-0-1-0.lcc1-res-bb-rtr1-re1.verizon-gni.net (108.57.128.218) 34.098 ms 37.108 ms 33.767 ms
5 0.ge-7-0-0.xl3.iad8.alter.net (152.63.34.201) 38.609 ms
0.so-6-1-0.xl3.iad8.alter.net (152.63.36.233) 35.274 ms 34.297 ms
6 0.so-3-2-0.xl3.nyc4.alter.net (152.63.0.182) 47.279 ms 44.444 ms 45.976 ms
7 tengige0-6-0-0.gw8.nyc4.alter.net (152.63.22.41) 48.020 ms
tengige0-4-1-0.gw8.nyc4.alter.net (152.63.21.69) 45.687 ms 45.001 ms
8 google-gw.customer.alter.net (152.179.72.62) 46.196 ms 48.890 ms 41.085 ms
9 209.85.252.215 (209.85.252.215) 44.434 ms 44.171 ms 44.926 ms
10 209.85.249.11 (209.85.249.11) 47.573 ms
216.239.46.215 (216.239.46.215) 68.901 ms 67.927 ms
11 209.85.248.222 (209.85.248.222) 69.546 ms
66.249.94.46 (66.249.94.46) 46.416 ms
66.249.94.54 (66.249.94.54) 49.611 ms
12 66.249.94.54 (66.249.94.54) 71.168 ms
66.249.94.46 (66.249.94.46) 71.636 ms
iad04s01-in-f103.1e100.net (72.14.204.103) 44.289 ms

-----------------End Traceroute------------------

--------------ping first hop---------------

64 bytes from 10.8.7.1: icmp_seq=34 ttl=126 time=14.941 ms
64 bytes from 10.8.7.1: icmp_seq=35 ttl=126 time=12.113 ms
64 bytes from 10.8.7.1: icmp_seq=36 ttl=126 time=13.977 ms
64 bytes from 10.8.7.1: icmp_seq=37 ttl=126 time=13.143 ms
64 bytes from 10.8.7.1: icmp_seq=38 ttl=126 time=13.443 ms
64 bytes from 10.8.7.1: icmp_seq=39 ttl=126 time=14.121 ms
64 bytes from 10.8.7.1: icmp_seq=40 ttl=126 time=12.614 ms
64 bytes from 10.8.7.1: icmp_seq=41 ttl=126 time=12.124 ms
64 bytes from 10.8.7.1: icmp_seq=42 ttl=126 time=12.872 ms
64 bytes from 10.8.7.1: icmp_seq=43 ttl=126 time=11.141 ms
64 bytes from 10.8.7.1: icmp_seq=44 ttl=126 time=13.025 ms
64 bytes from 10.8.7.1: icmp_seq=45 ttl=126 time=14.496 ms
64 bytes from 10.8.7.1: icmp_seq=46 ttl=126 time=11.660 ms
64 bytes from 10.8.7.1: icmp_seq=47 ttl=126 time=15.299 ms
64 bytes from 10.8.7.1: icmp_seq=48 ttl=126 time=10.529 ms
64 bytes from 10.8.7.1: icmp_seq=49 ttl=126 time=10.351 ms
64 bytes from 10.8.7.1: icmp_seq=50 ttl=126 time=15.414 ms
64 bytes from 10.8.7.1: icmp_seq=51 ttl=126 time=15.101 ms
64 bytes from 10.8.7.1: icmp_seq=52 ttl=126 time=14.469 ms
-----------END UNLOADED PING DATA------------

---------PING WHILE DOWNLOADING--------------

PING 10.8.7.1 (10.8.7.1): 56 data bytes
64 bytes from 10.8.7.1: icmp_seq=0 ttl=126 time=11.549 ms
Request timeout for icmp_seq 1
64 bytes from 10.8.7.1: icmp_seq=2 ttl=126 time=13.514 ms
64 bytes from 10.8.7.1: icmp_seq=3 ttl=126 time=18.396 ms
64 bytes from 10.8.7.1: icmp_seq=4 ttl=126 time=13.528 ms
64 bytes from 10.8.7.1: icmp_seq=5 ttl=126 time=12.429 ms
64 bytes from 10.8.7.1: icmp_seq=6 ttl=126 time=13.016 ms
64 bytes from 10.8.7.1: icmp_seq=7 ttl=126 time=12.250 ms
64 bytes from 10.8.7.1: icmp_seq=8 ttl=126 time=34.263 ms
64 bytes from 10.8.7.1: icmp_seq=9 ttl=126 time=13.367 ms
64 bytes from 10.8.7.1: icmp_seq=10 ttl=126 time=23.184 ms
64 bytes from 10.8.7.1: icmp_seq=11 ttl=126 time=38.961 ms
64 bytes from 10.8.7.1: icmp_seq=12 ttl=126 time=20.152 ms
64 bytes from 10.8.7.1: icmp_seq=13 ttl=126 time=22.325 ms
64 bytes from 10.8.7.1: icmp_seq=14 ttl=126 time=34.852 ms
64 bytes from 10.8.7.1: icmp_seq=15 ttl=126 time=11.131 ms
64 bytes from 10.8.7.1: icmp_seq=16 ttl=126 time=29.495 ms
64 bytes from 10.8.7.1: icmp_seq=17 ttl=126 time=35.166 ms
64 bytes from 10.8.7.1: icmp_seq=18 ttl=126 time=11.237 ms
64 bytes from 10.8.7.1: icmp_seq=19 ttl=126 time=12.367 ms
64 bytes from 10.8.7.1: icmp_seq=20 ttl=126 time=23.636 ms
64 bytes from 10.8.7.1: icmp_seq=21 ttl=126 time=24.847 ms
64 bytes from 10.8.7.1: icmp_seq=22 ttl=126 time=10.360 ms
64 bytes from 10.8.7.1: icmp_seq=23 ttl=126 time=15.982 ms
64 bytes from 10.8.7.1: icmp_seq=24 ttl=126 time=28.155 ms
64 bytes from 10.8.7.1: icmp_seq=25 ttl=126 time=27.300 ms
64 bytes from 10.8.7.1: icmp_seq=26 ttl=126 time=15.403 ms
64 bytes from 10.8.7.1: icmp_seq=27 ttl=126 time=27.331 ms
64 bytes from 10.8.7.1: icmp_seq=28 ttl=126 time=53.616 ms
64 bytes from 10.8.7.1: icmp_seq=29 ttl=126 time=12.540 ms
64 bytes from 10.8.7.1: icmp_seq=30 ttl=126 time=33.273 ms
64 bytes from 10.8.7.1: icmp_seq=31 ttl=126 time=20.586 ms
64 bytes from 10.8.7.1: icmp_seq=32 ttl=126 time=36.512 ms
64 bytes from 10.8.7.1: icmp_seq=33 ttl=126 time=13.602 ms
64 bytes from 10.8.7.1: icmp_seq=34 ttl=126 time=32.361 ms
64 bytes from 10.8.7.1: icmp_seq=35 ttl=126 time=30.889 ms
64 bytes from 10.8.7.1: icmp_seq=36 ttl=126 time=27.956 ms
64 bytes from 10.8.7.1: icmp_seq=37 ttl=126 time=12.499 ms
64 bytes from 10.8.7.1: icmp_seq=38 ttl=126 time=23.969 ms
64 bytes from 10.8.7.1: icmp_seq=39 ttl=126 time=39.683 ms
64 bytes from 10.8.7.1: icmp_seq=40 ttl=126 time=21.959 ms
64 bytes from 10.8.7.1: icmp_seq=41 ttl=126 time=12.942 ms
Request timeout for icmp_seq 42
64 bytes from 10.8.7.1: icmp_seq=43 ttl=126 time=21.299 ms
64 bytes from 10.8.7.1: icmp_seq=44 ttl=126 time=34.599 ms
64 bytes from 10.8.7.1: icmp_seq=45 ttl=126 time=12.184 ms
64 bytes from 10.8.7.1: icmp_seq=46 ttl=126 time=17.306 ms
64 bytes from 10.8.7.1: icmp_seq=47 ttl=126 time=31.656 ms
64 bytes from 10.8.7.1: icmp_seq=48 ttl=126 time=13.870 ms
64 bytes from 10.8.7.1: icmp_seq=49 ttl=126 time=31.440 ms
64 bytes from 10.8.7.1: icmp_seq=50 ttl=126 time=21.410 ms
64 bytes from 10.8.7.1: icmp_seq=51 ttl=126 time=29.154 ms
Request timeout for icmp_seq 52
64 bytes from 10.8.7.1: icmp_seq=53 ttl=126 time=19.512 ms
64 bytes from 10.8.7.1: icmp_seq=54 ttl=126 time=31.748 ms
64 bytes from 10.8.7.1: icmp_seq=55 ttl=126 time=33.155 ms
64 bytes from 10.8.7.1: icmp_seq=56 ttl=126 time=10.237 ms
64 bytes from 10.8.7.1: icmp_seq=57 ttl=126 time=27.298 ms
64 bytes from 10.8.7.1: icmp_seq=58 ttl=126 time=50.405 ms
64 bytes from 10.8.7.1: icmp_seq=59 ttl=126 time=26.053 ms
64 bytes from 10.8.7.1: icmp_seq=60 ttl=126 time=28.813 ms
64 bytes from 10.8.7.1: icmp_seq=61 ttl=126 time=34.916 ms
64 bytes from 10.8.7.1: icmp_seq=62 ttl=126 time=13.592 ms
64 bytes from 10.8.7.1: icmp_seq=63 ttl=126 time=25.210 ms
64 bytes from 10.8.7.1: icmp_seq=64 ttl=126 time=34.654 ms
64 bytes from 10.8.7.1: icmp_seq=65 ttl=126 time=14.036 ms
64 bytes from 10.8.7.1: icmp_seq=66 ttl=126 time=28.894 ms
64 bytes from 10.8.7.1: icmp_seq=67 ttl=126 time=35.596 ms
64 bytes from 10.8.7.1: icmp_seq=68 ttl=126 time=14.536 ms
64 bytes from 10.8.7.1: icmp_seq=69 ttl=126 time=20.002 ms
64 bytes from 10.8.7.1: icmp_seq=70 ttl=126 time=12.676 ms
64 bytes from 10.8.7.1: icmp_seq=71 ttl=126 time=13.414 ms
64 bytes from 10.8.7.1: icmp_seq=72 ttl=126 time=28.274 ms
64 bytes from 10.8.7.1: icmp_seq=73 ttl=126 time=16.476 ms
64 bytes from 10.8.7.1: icmp_seq=74 ttl=126 time=58.863 ms
64 bytes from 10.8.7.1: icmp_seq=75 ttl=126 time=31.649 ms
64 bytes from 10.8.7.1: icmp_seq=76 ttl=126 time=13.869 ms
64 bytes from 10.8.7.1: icmp_seq=77 ttl=126 time=26.052 ms
64 bytes from 10.8.7.1: icmp_seq=78 ttl=126 time=31.527 ms
64 bytes from 10.8.7.1: icmp_seq=79 ttl=126 time=10.753 ms
64 bytes from 10.8.7.1: icmp_seq=80 ttl=126 time=23.382 ms
64 bytes from 10.8.7.1: icmp_seq=81 ttl=126 time=29.113 ms
64 bytes from 10.8.7.1: icmp_seq=82 ttl=126 time=36.436 ms
64 bytes from 10.8.7.1: icmp_seq=83 ttl=126 time=17.958 ms
64 bytes from 10.8.7.1: icmp_seq=84 ttl=126 time=11.956 ms
64 bytes from 10.8.7.1: icmp_seq=85 ttl=126 time=20.098 ms
64 bytes from 10.8.7.1: icmp_seq=86 ttl=126 time=27.169 ms
64 bytes from 10.8.7.1: icmp_seq=87 ttl=126 time=40.694 ms
64 bytes from 10.8.7.1: icmp_seq=88 ttl=126 time=12.739 ms
64 bytes from 10.8.7.1: icmp_seq=89 ttl=126 time=11.140 ms
64 bytes from 10.8.7.1: icmp_seq=90 ttl=126 time=14.540 ms
64 bytes from 10.8.7.1: icmp_seq=91 ttl=126 time=14.262 ms
64 bytes from 10.8.7.1: icmp_seq=92 ttl=126 time=14.230 ms
6

-------------------END PING WHILE DOWNLOADING---------

It can be noted that the download speed never really stabilized. I was all over the place between 90kbps and 220kbps


gozer
Premium
join:2010-08-09
Rochester, NY

Hi chutzler this is your first hop thats public use the 3rd one
184.19.255.24


wasvznowftr

join:2010-07-13
00000
reply to Smith6612

why on earth does chutzler have a 5 ms ping to his router?


gozer
Premium
join:2010-08-09
Rochester, NY

heheh idk but yes it should be 1ms



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23
Reviews:
·Verizon Online DSL
·Frontier Communi..

1 edit
reply to gozer

In Verizon Territory, they tend to use Private, Non-routable addresses on the customer side when hitting the edge router. Generally, it doesn't have an RDNS so 10.8.7.1 is the ISP's router/his first hop outside of his network, whereas a Reverse Trace route reveals an IP address the edge router is really holding. Frontier is different in this case where the edge router IP presented in one's trace route is one that can be reached from the Internet.

Chutzler might be on not too good of a wireless link, hence his latency however that is awfully high latency to the router though. That should be at 1ms over Wireless or less than 1ms on Ethernet. Chutzler, see if you can correct that. If you are on Ethernet, check the duplex and give your router a reboot. Also, can you perform a line quality test from this site's tools section if you haven't done so? It sounds and looks as if you're on one of Verizon's Juniper ERX routers and are behind a particular Lucent switch that doesn't play nicely with the Junipers.


chutzler

join:2010-08-14
Martinsburg, WV

I am indeed on a wireless connection, with less than great signal strength, I can perform it again from a wired machine if need be.


poo pookie

join:2010-08-09
reply to Smith6612

Nothing more can be done to my line for the speed issue. So the stats I posted are it.

Did I do it correctly? I am not sure if I pinged the right hop and my post is so unorganized (I really screwed up on the copy and paste thing )



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23
Reviews:
·Verizon Online DSL
·Frontier Communi..

1 edit

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.


chutzler

join:2010-08-14
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 (72.14.204.103), 30 hops max, 60 byte packets
1 gateway.home.thfn.org (10.10.10.1) 0.545 ms 0.814 ms 1.117 ms
2 10.8.7.1 (10.8.7.1) 9.353 ms 10.745 ms 12.186 ms
3 184.19.255.24 (184.19.255.24) 25.662 ms 26.605 ms 28.047 ms
4 so-5-0-1-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net (108.57.128.218) 43.170 ms 44.212 ms 46.055 ms
5 0.so-1-2-0.XL3.IAD8.ALTER.NET (152.63.37.117) 48.396 ms 0.so-6-1-0.XL3.IAD8.ALTER.NET (152.63.36.233) 49.285 ms 0.ge-7-0-0.XL3.IAD8.ALTER.NET (152.63.34.201) 55.171 ms
6 0.so-3-2-0.XL3.NYC4.ALTER.NET (152.63.0.182) 61.604 ms 63.300 ms 63.366 ms
7 TenGigE0-4-4-0.GW8.NYC4.ALTER.NET (152.63.18.202) 65.101 ms TenGigE0-6-2-0.GW8.NYC4.ALTER.NET (152.63.21.117) 40.423 ms TenGigE0-4-1-0.GW8.NYC4.ALTER.NET (152.63.21.69) 44.299 ms
8 google-gw.customer.alter.net (152.179.72.62) 61.148 ms 62.531 ms 64.188 ms
9 209.85.252.215 (209.85.252.215) 48.404 ms 67.371 ms 67.452 ms
10 209.85.249.11 (209.85.249.11) 52.084 ms 54.524 ms 57.466 ms
11 66.249.94.54 (66.249.94.54) 60.956 ms 66.249.94.46 (66.249.94.46) 57.541 ms 70.830 ms
12 iad04s01-in-f103.1e100.net (72.14.204.103) 62.576 ms 62.668 ms 43.314 ms
-------------------End traceroute---------------------

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

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

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



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23
Reviews:
·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.


chutzler

join:2010-08-14
Martinsburg, WV

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

»174.34.146.20/myspeed/db/report?id=189857



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23
Reviews:
·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.

»174.34.146.20/myspeed/db/report?id=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.

»174.34.146.20/myspeed/db/report?id=189902

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


Billy B

join:2006-03-22
Robbinsville, NC
reply to Smith6612

Hello Smith6612. This is Billy B who you recently helped directly with my DSL connection problems and for which I again thank you.

In return for that help I have tried to follow your instructions on the above issue and want to post as follows:

I am ex-Verizon / now Frontier in western NC. I am signed up for the 3 MB / 768 Speed Package and thanks to your help and my newly installed "home run" I have been correctly in sync for 4 full days as follows from my Westell 7500.

Transceiver Revision A2pB020b3.d20h
Vendor ID Code 4D54
Line Mode ADSL2
Data Path FAST

Transceiver Information Down Stream Path Up Stream Path
DSL Speed (Kbits/Sec) 3358 862
Margin (dB) 10.6 13.1
Line Attenuation (dB) 46.5 27.2
Transmit Power (dBm) 0.0 12.8

I ran a Speedtest "early" / before 6AM every morning this week and acheived speeds of 2.87 MB DL and 0.72 UL with a Ping of 57 / 58 each time.

I just ran a Speedtest again at 5.45 PM Fri. Evening and only achieved 1.23 MB DL / 0.72 UL with a Ping of 70.

Following that I ran a continuous ping to 10.37.1.1 with "no load" and then started the 100 MB DL that you provided in your link. Here are the Ping results with the "load" starting just before the first "Request Timed Out" During the 100 MB DL my speed varied between 100 and 200.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Pinging 10.37.1.1 with 32 bytes of data:
Reply from 10.37.1.1: bytes=32 time=71ms TTL=126
Reply from 10.37.1.1: bytes=32 time=103ms TTL=126
Reply from 10.37.1.1: bytes=32 time=77ms TTL=126
Reply from 10.37.1.1: bytes=32 time=73ms TTL=126
Reply from 10.37.1.1: bytes=32 time=89ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=103ms TTL=126
Reply from 10.37.1.1: bytes=32 time=100ms TTL=126
Reply from 10.37.1.1: bytes=32 time=68ms TTL=126
Reply from 10.37.1.1: bytes=32 time=104ms TTL=126
Reply from 10.37.1.1: bytes=32 time=83ms TTL=126
Reply from 10.37.1.1: bytes=32 time=73ms TTL=126
Reply from 10.37.1.1: bytes=32 time=83ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=74ms TTL=126
Reply from 10.37.1.1: bytes=32 time=56ms TTL=126
Reply from 10.37.1.1: bytes=32 time=104ms TTL=126
Reply from 10.37.1.1: bytes=32 time=66ms TTL=126
Reply from 10.37.1.1: bytes=32 time=75ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=94ms TTL=126
Reply from 10.37.1.1: bytes=32 time=145ms TTL=126
Reply from 10.37.1.1: bytes=32 time=155ms TTL=126
Reply from 10.37.1.1: bytes=32 time=79ms TTL=126
Request timed out.
Reply from 10.37.1.1: bytes=32 time=77ms TTL=126
Reply from 10.37.1.1: bytes=32 time=92ms TTL=126
Reply from 10.37.1.1: bytes=32 time=104ms TTL=126
Reply from 10.37.1.1: bytes=32 time=135ms TTL=126
Reply from 10.37.1.1: bytes=32 time=89ms TTL=126
Reply from 10.37.1.1: bytes=32 time=73ms TTL=126
Reply from 10.37.1.1: bytes=32 time=105ms TTL=126
Reply from 10.37.1.1: bytes=32 time=198ms TTL=126
Reply from 10.37.1.1: bytes=32 time=83ms TTL=126
Reply from 10.37.1.1: bytes=32 time=99ms TTL=126
Reply from 10.37.1.1: bytes=32 time=77ms TTL=126
Reply from 10.37.1.1: bytes=32 time=56ms TTL=126
Reply from 10.37.1.1: bytes=32 time=95ms TTL=126
Reply from 10.37.1.1: bytes=32 time=72ms TTL=126
Reply from 10.37.1.1: bytes=32 time=90ms TTL=126
Reply from 10.37.1.1: bytes=32 time=59ms TTL=126
Request timed out.
Reply from 10.37.1.1: bytes=32 time=68ms TTL=126
Reply from 10.37.1.1: bytes=32 time=103ms TTL=126
Reply from 10.37.1.1: bytes=32 time=110ms TTL=126
Reply from 10.37.1.1: bytes=32 time=91ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=92ms TTL=126
Reply from 10.37.1.1: bytes=32 time=63ms TTL=126
Reply from 10.37.1.1: bytes=32 time=90ms TTL=126
Reply from 10.37.1.1: bytes=32 time=82ms TTL=126
Reply from 10.37.1.1: bytes=32 time=107ms TTL=126
Reply from 10.37.1.1: bytes=32 time=90ms TTL=126
Reply from 10.37.1.1: bytes=32 time=69ms TTL=126
Reply from 10.37.1.1: bytes=32 time=107ms TTL=126
Reply from 10.37.1.1: bytes=32 time=101ms TTL=126
Reply from 10.37.1.1: bytes=32 time=60ms TTL=126
Reply from 10.37.1.1: bytes=32 time=110ms TTL=126
Reply from 10.37.1.1: bytes=32 time=91ms TTL=126
Reply from 10.37.1.1: bytes=32 time=61ms TTL=126
Reply from 10.37.1.1: bytes=32 time=103ms TTL=126
Reply from 10.37.1.1: bytes=32 time=111ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=85ms TTL=126
Reply from 10.37.1.1: bytes=32 time=57ms TTL=126
Reply from 10.37.1.1: bytes=32 time=106ms TTL=126
Reply from 10.37.1.1: bytes=32 time=91ms TTL=126
Reply from 10.37.1.1: bytes=32 time=70ms TTL=126
Reply from 10.37.1.1: bytes=32 time=112ms TTL=126
Reply from 10.37.1.1: bytes=32 time=82ms TTL=126
Reply from 10.37.1.1: bytes=32 time=66ms TTL=126
Reply from 10.37.1.1: bytes=32 time=73ms TTL=126
Reply from 10.37.1.1: bytes=32 time=104ms TTL=126
Reply from 10.37.1.1: bytes=32 time=83ms TTL=126
Reply from 10.37.1.1: bytes=32 time=66ms TTL=126
Request timed out.
Reply from 10.37.1.1: bytes=32 time=86ms TTL=126
Reply from 10.37.1.1: bytes=32 time=61ms TTL=126
Request timed out.
Reply from 10.37.1.1: bytes=32 time=84ms TTL=126
Reply from 10.37.1.1: bytes=32 time=72ms TTL=126
Reply from 10.37.1.1: bytes=32 time=82ms TTL=126
Reply from 10.37.1.1: bytes=32 time=97ms TTL=126
Reply from 10.37.1.1: bytes=32 time=64ms TTL=126
Reply from 10.37.1.1: bytes=32 time=64ms TTL=126
Reply from 10.37.1.1: bytes=32 time=75ms TTL=126
Reply from 10.37.1.1: bytes=32 time=112ms TTL=126
Reply from 10.37.1.1: bytes=32 time=87ms TTL=126
Reply from 10.37.1.1: bytes=32 time=61ms TTL=126
Reply from 10.37.1.1: bytes=32 time=85ms TTL=126
Reply from 10.37.1.1: bytes=32 time=107ms TTL=126
Reply from 10.37.1.1: bytes=32 time=100ms TTL=126
Reply from 10.37.1.1: bytes=32 time=77ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=108ms TTL=126
Reply from 10.37.1.1: bytes=32 time=81ms TTL=126
Reply from 10.37.1.1: bytes=32 time=68ms TTL=126
Reply from 10.37.1.1: bytes=32 time=82ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=69ms TTL=126
Reply from 10.37.1.1: bytes=32 time=80ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=110ms TTL=126
Reply from 10.37.1.1: bytes=32 time=79ms TTL=126
Reply from 10.37.1.1: bytes=32 time=70ms TTL=126
Reply from 10.37.1.1: bytes=32 time=71ms TTL=126
Reply from 10.37.1.1: bytes=32 time=104ms TTL=126
Reply from 10.37.1.1: bytes=32 time=93ms TTL=126
Reply from 10.37.1.1: bytes=32 time=95ms TTL=126
Reply from 10.37.1.1: bytes=32 time=66ms TTL=126
Reply from 10.37.1.1: bytes=32 time=99ms TTL=126
Reply from 10.37.1.1: bytes=32 time=100ms TTL=126
Reply from 10.37.1.1: bytes=32 time=104ms TTL=126
Reply from 10.37.1.1: bytes=32 time=90ms TTL=126
Reply from 10.37.1.1: bytes=32 time=69ms TTL=126
Reply from 10.37.1.1: bytes=32 time=107ms TTL=126
Reply from 10.37.1.1: bytes=32 time=106ms TTL=126
Reply from 10.37.1.1: bytes=32 time=82ms TTL=126
Reply from 10.37.1.1: bytes=32 time=75ms TTL=126
Reply from 10.37.1.1: bytes=32 time=64ms TTL=126
Reply from 10.37.1.1: bytes=32 time=80ms TTL=126
Reply from 10.37.1.1: bytes=32 time=107ms TTL=126
Reply from 10.37.1.1: bytes=32 time=78ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=74ms TTL=126
Reply from 10.37.1.1: bytes=32 time=99ms TTL=126
Reply from 10.37.1.1: bytes=32 time=87ms TTL=126
Reply from 10.37.1.1: bytes=32 time=85ms TTL=126
Reply from 10.37.1.1: bytes=32 time=78ms TTL=126
Reply from 10.37.1.1: bytes=32 time=64ms TTL=126
Reply from 10.37.1.1: bytes=32 time=79ms TTL=126
Reply from 10.37.1.1: bytes=32 time=58ms TTL=126
Reply from 10.37.1.1: bytes=32 time=99ms TTL=126
Reply from 10.37.1.1: bytes=32 time=94ms TTL=126
Reply from 10.37.1.1: bytes=32 time=66ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=102ms TTL=126
Reply from 10.37.1.1: bytes=32 time=99ms TTL=126
Reply from 10.37.1.1: bytes=32 time=89ms TTL=126
Reply from 10.37.1.1: bytes=32 time=80ms TTL=126
Reply from 10.37.1.1: bytes=32 time=78ms TTL=126
Reply from 10.37.1.1: bytes=32 time=60ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=102ms TTL=126
Reply from 10.37.1.1: bytes=32 time=99ms TTL=126
Reply from 10.37.1.1: bytes=32 time=85ms TTL=126
Reply from 10.37.1.1: bytes=32 time=76ms TTL=126
Reply from 10.37.1.1: bytes=32 time=92ms TTL=126
Reply from 10.37.1.1: bytes=32 time=108ms TTL=126
Reply from 10.37.1.1: bytes=32 time=59ms TTL=126
Reply from 10.37.1.1: bytes=32 time=92ms TTL=126
Reply from 10.37.1.1: bytes=32 time=110ms TTL=126
Reply from 10.37.1.1: bytes=32 time=81ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=81ms TTL=126
Reply from 10.37.1.1: bytes=32 time=56ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=90ms TTL=126
Reply from 10.37.1.1: bytes=32 time=63ms TTL=126
Reply from 10.37.1.1: bytes=32 time=95ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=95ms TTL=126
Reply from 10.37.1.1: bytes=32 time=76ms TTL=126
Reply from 10.37.1.1: bytes=32 time=66ms TTL=126
Reply from 10.37.1.1: bytes=32 time=100ms TTL=126
Reply from 10.37.1.1: bytes=32 time=90ms TTL=126
Reply from 10.37.1.1: bytes=32 time=78ms TTL=126
Reply from 10.37.1.1: bytes=32 time=79ms TTL=126
Reply from 10.37.1.1: bytes=32 time=93ms TTL=126
Reply from 10.37.1.1: bytes=32 time=89ms TTL=126
Reply from 10.37.1.1: bytes=32 time=72ms TTL=126
Reply from 10.37.1.1: bytes=32 time=57ms TTL=126
Reply from 10.37.1.1: bytes=32 time=103ms TTL=126
Reply from 10.37.1.1: bytes=32 time=71ms TTL=126
Reply from 10.37.1.1: bytes=32 time=59ms TTL=126
Reply from 10.37.1.1: bytes=32 time=75ms TTL=126
Reply from 10.37.1.1: bytes=32 time=100ms TTL=126
Reply from 10.37.1.1: bytes=32 time=89ms TTL=126
Reply from 10.37.1.1: bytes=32 time=56ms TTL=126
Reply from 10.37.1.1: bytes=32 time=100ms TTL=126
Reply from 10.37.1.1: bytes=32 time=90ms TTL=126
Reply from 10.37.1.1: bytes=32 time=58ms TTL=126
Reply from 10.37.1.1: bytes=32 time=82ms TTL=126
Reply from 10.37.1.1: bytes=32 time=87ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=106ms TTL=126
Reply from 10.37.1.1: bytes=32 time=68ms TTL=126
Reply from 10.37.1.1: bytes=32 time=104ms TTL=126
Reply from 10.37.1.1: bytes=32 time=80ms TTL=126
Reply from 10.37.1.1: bytes=32 time=67ms TTL=126
Reply from 10.37.1.1: bytes=32 time=103ms TTL=126
Reply from 10.37.1.1: bytes=32 time=79ms TTL=126
Reply from 10.37.1.1: bytes=32 time=67ms TTL=126
Reply from 10.37.1.1: bytes=32 time=79ms TTL=126
Reply from 10.37.1.1: bytes=32 time=76ms TTL=126
Reply from 10.37.1.1: bytes=32 time=75ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=85ms TTL=126
Reply from 10.37.1.1: bytes=32 time=96ms TTL=126
Reply from 10.37.1.1: bytes=32 time=72ms TTL=126
Reply from 10.37.1.1: bytes=32 time=60ms TTL=126
Reply from 10.37.1.1: bytes=32 time=96ms TTL=126
Reply from 10.37.1.1: bytes=32 time=100ms TTL=126
Reply from 10.37.1.1: bytes=32 time=94ms TTL=126
Reply from 10.37.1.1: bytes=32 time=98ms TTL=126
Reply from 10.37.1.1: bytes=32 time=64ms TTL=126
Reply from 10.37.1.1: bytes=32 time=60ms TTL=126
Reply from 10.37.1.1: bytes=32 time=84ms TTL=126
Reply from 10.37.1.1: bytes=32 time=85ms TTL=126
Reply from 10.37.1.1: bytes=32 time=80ms TTL=126
Reply from 10.37.1.1: bytes=32 time=85ms TTL=126
Reply from 10.37.1.1: bytes=32 time=82ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=101ms TTL=126
Reply from 10.37.1.1: bytes=32 time=58ms TTL=126

Ping statistics for 10.37.1.1:
Packets: Sent = 218, Received = 214, Lost = 4 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 198ms, Average = 84ms
Control-C

I hope this information helps and look forward to your observations in due course.


Billy B

join:2006-03-22
Robbinsville, NC
reply to Smith6612


Good Morning Smith6612. Here is the same Ping Test
results performed at 6.15 AM. this morning under "no load" conditions. I achieved the usual 2.88 DL / 0.72 UL Speeds at Speedtest. net.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

ping 10.37.1.1 -t

Pinging 10.37.1.1 with 32 bytes of data:
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=56ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=55ms TTL=126
eply from 10.37.1.1: bytes=32 time=54ms TTL=126

ing statistics for 10.37.1.1:
Packets: Sent = 39, Received = 39, Lost = 0 (0% loss),
pproximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 56ms, Average = 54ms
ontrol-C



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23

Looks like you are seeing congestion during the evening/night too, besides unusually high first hop counts. I hope Frontier gets that fixed and also lowers that first hop count, as it's not something I'd consider ideal for broadband at all.


Billy B

join:2006-03-22
Robbinsville, NC
reply to Smith6612

Good Morning Smith6612.
Just a quick follow-up posting with the results from my latest & repeat ping test performed at 8AM this morning.
Clearly my initial ping "without load" was around 55MS and then changed to the 170 / 180 MS range while downloading the 100 MB file before returning to "normal"

Significantly for me and evidence that your theory about congestion being my local problem is that yesterday the kids all returned to school and my speedtest results showed my normal 2.87 DL speed all day and into the evening.
Thanks for everything, I really do appreciate the help and education. Billy B.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Pinging 10.37.1.1 with 32 bytes of data:
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=176ms TTL=126
Reply from 10.37.1.1: bytes=32 time=178ms TTL=126
Reply from 10.37.1.1: bytes=32 time=181ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=181ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=174ms TTL=126
Reply from 10.37.1.1: bytes=32 time=176ms TTL=126
Reply from 10.37.1.1: bytes=32 time=178ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=174ms TTL=126
Reply from 10.37.1.1: bytes=32 time=185ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=176ms TTL=126
Reply from 10.37.1.1: bytes=32 time=184ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=182ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=178ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=174ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=181ms TTL=126
Reply from 10.37.1.1: bytes=32 time=174ms TTL=126
Reply from 10.37.1.1: bytes=32 time=176ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=173ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=181ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=182ms TTL=126
Reply from 10.37.1.1: bytes=32 time=176ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=182ms TTL=126
Reply from 10.37.1.1: bytes=32 time=176ms TTL=126
Reply from 10.37.1.1: bytes=32 time=178ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=181ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=179ms TTL=126
Reply from 10.37.1.1: bytes=32 time=181ms TTL=126
Reply from 10.37.1.1: bytes=32 time=175ms TTL=126
Reply from 10.37.1.1: bytes=32 time=177ms TTL=126
Reply from 10.37.1.1: bytes=32 time=178ms TTL=126
Reply from 10.37.1.1: bytes=32 time=180ms TTL=126
Reply from 10.37.1.1: bytes=32 time=174ms TTL=126
Reply from 10.37.1.1: bytes=32 time=176ms TTL=126
Reply from 10.37.1.1: bytes=32 time=178ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=57ms TTL=126
Reply from 10.37.1.1: bytes=32 time=60ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=56ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=55ms TTL=126
Reply from 10.37.1.1: bytes=32 time=54ms TTL=126

Ping statistics for 10.37.1.1:
Packets: Sent = 103, Received = 103, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 185ms, Average = 137ms
Control-C
^C



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23
Reviews:
·Verizon Online DSL
·Frontier Communi..

Your first hop latency is still rather high for a FastPath line, but I'm glad to hear the speed has returned. I'm hoping Frontier is bringing in more bandwidth and figuring out the best way to route things however. A high speed line doesn't mean anything if first hop latency is higher than 15ms on FastPath.


Kemeko

join:2010-05-03
reply to Smith6612

Do you want me to do another test? I'm still dreading to call there again i know i should've the first day after they replaced the modem and it didn't work right, but i also think it's useless sometimes too heh.



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23

Up to you if you wish to run another one.


Billy B

join:2006-03-22
Robbinsville, NC
reply to Smith6612

Good Morning Smith6612 and thanks for your imput once again but which prompts another Q.
I have always had a ping of about 55MS to my first hop and a DL Speed of 2.88 during the 4 1/2 years that I have had Vz / Frontier DSL. Does the fact that I am located 2.2 miles down "copper" from a Remote Terminal and another 4 miles along a FIOS cable to the DSLAM in our local town play into that ping stat? Thanks in advance.


chutzler

join:2010-08-14
Martinsburg, WV
reply to Smith6612

Unfortunately I solved my problem the hard way, comcast installer was here yesterday. While I loved my directv, I had to go with a bundled service with CC to get a decent price. Though Frontier was nice enough to credit me for my problems....I really hope they get their act together, but as I use my connection for work (VPN) I don't have the luxury of waiting for them to figure it out


jhamps10

join:2006-01-06
Flora, IL

I wish I was in a comcast, or any other cable company who gives a damn's service area right about now too. This is worse than Cable internet in 1998!



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:23
Reviews:
·Verizon Online DSL
·Frontier Communi..

2 edits
reply to Billy B

Click for full size
Pings
The latency shouldn't be that for such a route. I'm going over 2 miles of copper to an RT that is Fiber Fed. From there, the Optical cable is running anywhere between 4-8 miles in length to the central office, and this is the kind of latency I get. I'm on FastPath with a 1Mbps connection. The latency is bumped up an extra millisecond or less since that connection is running through two routers on my end (Double NAT). I'm connected via Ethernet as this is my gaming PC.