dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
594
share rss forum feed

m12345s

join:2010-10-13
Bolivar, MO

Normal Latency?

Hi, I just got Windstream DSL back in february, I was in a stimulus area and windstream put in a DSLAM and ran fiber to get us hooked up. Anyway, I qualified for 12 meg, while the speed is always consistent and never really dropped below 12, I have noticed since day 1 that my latency seems a bit high for DSL, my average is around 50-80, I kind of expected pings in the 20s or 30s especially with all new equipment and fiber, and the fact that I'm only about a mile from the new DSLAM. Is there any settings either me or Windstream could change to bring it down a bit? Defenitely isn't an over subscription issue since it's very rural and im on all new equipment.


jerminy11

join:2011-12-27
Texarkana, AR



jerminy11

join:2011-12-27
Texarkana, AR

50 to 80 is a little high..... This equipment is not new and this area is loaded with windstream customers and I still get this



Windstream
Premium,VIP
join:2009-03-31
Twinsburg, OH
kudos:38
reply to m12345s

We apologize that you are having problems with your service. If you would like us to investigate, please send us a PM with the phone number your DSL service is under or visit us at our Direct Support Forum »Windstream Direct. We'll take a look and be in touch.
Patricia
Support Specialist II
Broadband Tier II
--
We're here to help! wci.broadbandhelp@windstream.com



Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA
reply to m12345s

50-80ms latency to where?

Give us a tracert or IP that you are using to determine this.


m12345s

join:2010-10-13
Bolivar, MO

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Michael>tracert google.com

Tracing route to google.com [74.125.29.101]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms MyRouter.Home [192.168.254.254]
2 8 ms 8 ms 8 ms h5.8.213.151.static.ip.windstream.net [151.213.8
.5]
3 8 ms 8 ms 8 ms h84.37.185.173.static.ip.windstream.net [173.185
.37.84]
4 20 ms 20 ms 21 ms h196.122.22.98.dynamic.ip.windstream.net [98.22.
122.196]
5 38 ms 36 ms 37 ms h34.240.186.173.static.ip.windstream.net [173.18
6.240.34]
6 38 ms 38 ms 38 ms h173.137.28.71.static.ip.windstream.net [71.28.1
37.173]
7 37 ms 37 ms 48 ms 64.233.174.2
8 39 ms 38 ms 41 ms 66.249.94.22
9 45 ms 43 ms 45 ms 216.239.48.5
10 62 ms 43 ms 54 ms 72.14.234.67
11 * * * Request timed out.
12 45 ms 45 ms 44 ms qg-in-f101.1e100.net [74.125.29.101]

Trace complete.

C:\Users\Michael>

There is a tracert to google, I will take another one this afternoon.


m12345s

join:2010-10-13
Bolivar, MO
reply to m12345s

And here is another from about 7PM central time

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Michael>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.

C:\Users\Michael>tracert google.com

Tracing route to google.com [74.125.29.138]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms MyRouter.Home [192.168.254.254]
2 9 ms 8 ms 8 ms h5.8.213.151.static.ip.windstream.net [151.213.8
.5]
3 9 ms 14 ms 9 ms h86.37.185.173.static.ip.windstream.net [173.185
.37.86]
4 26 ms 26 ms 25 ms h128.171.39.162.static.ip.windstream.net [162.39
.171.128]
5 95 ms 92 ms 89 ms h34.240.186.173.static.ip.windstream.net [173.18
6.240.34]
6 41 ms 41 ms 40 ms h173.137.28.71.static.ip.windstream.net [71.28.1
37.173]
7 80 ms 80 ms 87 ms 64.233.174.2
8 41 ms 41 ms 44 ms 66.249.94.22
9 92 ms 96 ms 96 ms 216.239.48.5
10 175 ms 102 ms 100 ms 72.14.234.67
11 * * * Request timed out.
12 93 ms 45 ms 48 ms qg-in-f138.1e100.net [74.125.29.138]

Trace complete.

C:\Users\Michael>


m12345s

join:2010-10-13
Bolivar, MO
reply to m12345s

This is on the Sagemcom 1704N router on a wireless connection, ping is about the same wired.



Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA

Latency on Windstream's network looks fine, in the 2nd trace the latency jumps on google's part of the network.