mwf
join:2000-11-26
Granite Quarry, NC | reply to The Limit
Re: Post your speedtest between 8pm-12am here  |
|
|
|
| reply to The Limit
Test done at 9:48 P.M. CST
Anyone have any information as to why the service is so bad between 8pm and 12am? |
|
 WindstreamPremium,VIP
join:2009-03-31
Twinsburg, OH
kudos:33 | It could be, and probably is an over-utilization issue on the equipment you are drawing your signal from. Basically that means there is too many people on the equipment and not enough bandwidth to go around. Feel free to send us a PM or post your phone number in » Windstream Direct so that we can confirm.
Aaron
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com |
|
Reviews:
 ·Windstream
| Not to bust on ya too hard, Aaron, because I appreciate what y'all do on this forum, but another way to phrase that same issue would be "oversold".
The way you said it makes it sound to me like too many spoiled brat kids are clamoring for the new brand of candy at the snack bar. To my way of thinking, the candy store should stock the counter and open enough registers to handle the demand before they put out the "for sale" sign. |
|
shealysePremium
join:2004-04-15
Lexington, SC Reviews:
·Windstream
 ·RoadRunner Cable
 ·VoicePulse
·ViaTalk
| reply to The Limit
Windstream 12mb/768k at 9:33pm | | 
Time Warner 50mb/5mb at 9:33pm | |
|
|
| reply to The Limit
typical speed during the "prime time" (8p-12 MN) on a 3mbps subscription... at approx. 9:15 PM CDT THURS June 14, 2012...
(rural Arkansas: "no help coming your way, soon...")
ha... i'm in the lower 2% of broadband speed in U.S.
regards,
Pablo |
|
 The LimitPremium
join:2007-09-25
Greensboro, NC
kudos:2
·Windstream
| reply to The Limit
Keep them coming guys, I've been away for the last couple of days, which is the reason why I haven't posted. I'll keep you updated on my speed tests at home.
I average 1.5 megabits down/.5 megabits up during the hours of 8pm-12am from data gathered so far.
--
"We will evaluate these integrals rigorously if we can, and non-rigorously if we must".
---Victor Moll, invited talk, Tom Osler Fest (April 17, 2010) |
|
jin
join:2012-01-15
Hazard, KY Reviews:
·Windstream
| reply to LostInWoods
said by LostInWoods:Not to bust on ya too hard, Aaron, because I appreciate what y'all do on this forum, but another way to phrase that same issue would be "oversold".
The way you said it makes it sound to me like too many spoiled brat kids are clamoring for the new brand of candy at the snack bar. To my way of thinking, the candy store should stock the counter and open enough registers to handle the demand before they put out the "for sale" sign.
agreed |
|
Reviews:
·Time Warner Cable
·Windstream
·Windstream
| 
New speed from TWC all's good so far I guess only time will tell if the speeds hold up. But I'm happy to say Windstream no longer is my provider a 2 year wait and no end in sight was enough for me. |
|
| reply to The Limit
3mbps "performance" at about 9:15 PM CDT (Sat 6/16/12)
|
|
| reply to The Limit
this is just to demo that things work well during non-peak times:
this is approx 7 AM CDT (the next A.M. from prior test, above)
Sun 6/17/12...
regards,
Pablo |
|
| reply to The Limit
|
|
Reviews:
·Windstream
|  tested just now 10:43 pm in georgia.. they tell me they are gonna replace the DSLAM for our area, but it is on back order... i am less than 3000 feet from the DSLAM, and its like this after 7 pm every day for the past 7 months... |
|
Reviews:
·Windstream
1 edit | »www.speedtest.net/result/2018452067.png finally got speedtest to load.. 10:48 pm in georgia.. i am supposed to get 6 meg
»www.speedtest.net/result/2020870353.png here is my morning test |
|
 BobecNo StoogePremium
join:2001-01-04
Jefferson, GA
·Windstream
| reply to The Limit
Getting the same result in Speakeasy and in the speed test tools of DSLR.
Same speed regardless of time of day.
--
Just because you are a character doesn't mean that you have character.... |
|
| reply to The Limit
I pay for 6m service. I can't complain now. I had a lengthy period of time where my speeds were incredibly low, but repairs were made to the town. No issues since. Still hoping we can get 12m here someday soon.
|
|
Reviews:
·Windstream
| this is my 6 meg service .. absolutely lovely
|
|
| reply to The Limit
Look at the burn. |
|
| reply to The Limit
Best yet. |
|
1 edit | reply to The Limit
Well my service has went further down hill since last post. these are speeds at 12 AM 
Also was told other day in direct due to line quality test showing 85% packet loss,which may be off, but also had a ping plotting program running that day which had 67% loss, and then later that day ping test had 17% loss. Well I was told I wasn't having loss or I would not be able to get online. Funny my modem currently has 200k CRC errors for the last day and about 1 million dropped packets on the WAN side. Then I also ran a quick less than a minute ping -t to google tonight since no change since other day, it shows packet loss. Last chat about fixing the issue I was told they would re-evaluate the issues at the end of the year. SNR on my modem is 45 and atten is 30. Just had the home built and Cat5 cable run for the phones/modem, NID filter at the junction into the house, but I'm being told its my equip.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Raven>ping www.google.com -t
Pinging www.l.google.com [173.194.37.82] with 32 bytes of data:
Reply from 173.194.37.82: bytes=32 time=257ms TTL=56
Reply from 173.194.37.82: bytes=32 time=203ms TTL=56
Reply from 173.194.37.82: bytes=32 time=221ms TTL=56
Reply from 173.194.37.82: bytes=32 time=258ms TTL=56
Reply from 173.194.37.82: bytes=32 time=154ms TTL=56
Reply from 173.194.37.82: bytes=32 time=135ms TTL=56
Reply from 173.194.37.82: bytes=32 time=198ms TTL=56
Reply from 173.194.37.82: bytes=32 time=182ms TTL=56
Reply from 173.194.37.82: bytes=32 time=229ms TTL=56
Reply from 173.194.37.82: bytes=32 time=181ms TTL=56
Reply from 173.194.37.82: bytes=32 time=208ms TTL=56
Reply from 173.194.37.82: bytes=32 time=178ms TTL=56
Reply from 173.194.37.82: bytes=32 time=227ms TTL=56
Reply from 173.194.37.82: bytes=32 time=242ms TTL=56
Reply from 173.194.37.82: bytes=32 time=118ms TTL=56
Reply from 173.194.37.82: bytes=32 time=217ms TTL=56
Reply from 173.194.37.82: bytes=32 time=137ms TTL=56
Reply from 173.194.37.82: bytes=32 time=174ms TTL=56
Reply from 173.194.37.82: bytes=32 time=243ms TTL=56
Reply from 173.194.37.82: bytes=32 time=202ms TTL=56
Reply from 173.194.37.82: bytes=32 time=107ms TTL=56
Reply from 173.194.37.82: bytes=32 time=103ms TTL=56
Reply from 173.194.37.82: bytes=32 time=157ms TTL=56
Reply from 173.194.37.82: bytes=32 time=200ms TTL=56
Reply from 173.194.37.82: bytes=32 time=393ms TTL=56
Reply from 173.194.37.82: bytes=32 time=416ms TTL=56
Reply from 173.194.37.82: bytes=32 time=295ms TTL=56
Reply from 173.194.37.82: bytes=32 time=243ms TTL=56
Reply from 173.194.37.82: bytes=32 time=266ms TTL=56
Request timed out.
Reply from 173.194.37.82: bytes=32 time=181ms TTL=56
Reply from 173.194.37.82: bytes=32 time=238ms TTL=56
Reply from 173.194.37.82: bytes=32 time=173ms TTL=56
Reply from 173.194.37.82: bytes=32 time=229ms TTL=56
Reply from 173.194.37.82: bytes=32 time=122ms TTL=56
Reply from 173.194.37.82: bytes=32 time=204ms TTL=56
Reply from 173.194.37.82: bytes=32 time=256ms TTL=56
Reply from 173.194.37.82: bytes=32 time=170ms TTL=56
Reply from 173.194.37.82: bytes=32 time=138ms TTL=56
Reply from 173.194.37.82: bytes=32 time=235ms TTL=56
Reply from 173.194.37.82: bytes=32 time=228ms TTL=56
Reply from 173.194.37.82: bytes=32 time=241ms TTL=56
Reply from 173.194.37.82: bytes=32 time=160ms TTL=56
Reply from 173.194.37.82: bytes=32 time=221ms TTL=56
Request timed out.
Request timed out.
Reply from 173.194.37.82: bytes=32 time=119ms TTL=56
Reply from 173.194.37.82: bytes=32 time=184ms TTL=56
Reply from 173.194.37.82: bytes=32 time=219ms TTL=56
Reply from 173.194.37.82: bytes=32 time=214ms TTL=56
Reply from 173.194.37.82: bytes=32 time=187ms TTL=56
Reply from 173.194.37.82: bytes=32 time=151ms TTL=56
Reply from 173.194.37.82: bytes=32 time=255ms TTL=56
Reply from 173.194.37.82: bytes=32 time=178ms TTL=56
Reply from 173.194.37.82: bytes=32 time=155ms TTL=56
Reply from 173.194.37.82: bytes=32 time=207ms TTL=56
Ping statistics for 173.194.37.82:
Packets: Sent = 56, Received = 53, Lost = 3 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 103ms, Maximum = 416ms, Average = 203ms
Control-C
^C |
|
