Selected ISP Support → Windstream > I'm about to lose it

Re: I'm about to lose it

You too man and take it ez. Thanks for the updates and watch out for drunk drivers over the weekend!

You too Boss.

So I pushed it too far body bagger. Funny I was the first one called out on that but then I tend to push the edge on my posts.

Ok Merry christmas Arron, Bodybagger and all.

It's just after years of lies, refusing to fix problems when I worked at Orange Springs Restaurant & Grill and having to do an end run around CS to get it fixed. How am I supposed to feel?

Ok, I will start a new thread and ask what is my ETA.
--
| Speedstream 4200 Modem - 3m/384 plan | W98-W2KSP4-XPSP2 - All AMD | Buffalo WHR G54S with Tomato 1.18 | 3 downstream switches feeding 6 total clients (no wireless) | Including the Data port on the side of my neck |

Nah man I didn't call you out or anything. I was more explaining the situation. I work in IT as a help desk tech for the state and trust me, I know how this stuff gets. And believe me... I hate Windstream probably more than anyone can possibly imagine in this forum. lol.. I get highly pissed off a lot of times at this awful internet but I try my best not to bash these guys in here because I know how it is. By no means was I trying to call you out. I hope that this company gets everyone up and running how the shit should be ya know? No one should have to suffer through the problems we have experienced over the years.

And you haven't pushed the edge as much as some others have.. lol

I have worked help desk in IT but lucky I was dealing with a slightly more informed customer base. I worked in RF modems back in the 80's. I know how it gets. Lucky for me also, our owner didn't want us to lie or anything. His orders, if a customer becomes irate, let them rant a moment, then offer them a full refund upon returning the product. Sadly I think those type of owners are all gone.
--
| Speedstream 4200 Modem - 3m/384 plan | W98-W2KSP4-XPSP2 - All AMD | Buffalo WHR G54S with Tomato 1.18 | 3 downstream switches feeding 6 total clients (no wireless) | Including the Data port on the side of my neck |

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 302 ms 264 ms 320 ms h1.96.21.98.dynamic.ip.windstream.net [98.21.96.
1]
3 283 ms 308 ms 280 ms h232.28.189.173.static.ip.windstream.net [173.18
9.28.232]
4 356 ms 358 ms 385 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 427 ms 443 ms 406 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 * 427 ms 443 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 390 ms 352 ms 445 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 242 ms 249 ms 279 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 353 ms 305 ms 354 ms 72.14.219.192
10 365 ms 388 ms 410 ms 64.233.174.2
11 197 ms 232 ms 301 ms 66.249.94.6
12 255 ms 284 ms 349 ms 72.14.239.131
13 * * * Request timed out.
14 459 ms 379 ms 347 ms gh-in-f105.1e100.net [74.125.130.105]

Trace complete.

Unusable all day. GF is trying to work and taking 10+ minutes to load one 5 minute job. Anything else online... forget it.

I'm hoping Aaron gives me good concrete news as well Bodybagger. Be sure to let us know how the transition to new equipment goes. I really hope I get to make the same jump too. These latency issues have been incredibly frustrating.

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 342 ms 283 ms 310 ms h1.116.17.98.dynamic.ip.windstream.net [98.17.11
6.1]
3 281 ms 280 ms 315 ms h234.28.189.173.static.ip.windstream.net [173.18
9.28.234]
4 435 ms 395 ms 430 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 532 ms * 322 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 399 ms 336 ms 259 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 396 ms 361 ms 376 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 529 ms 489 ms 482 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 293 ms 256 ms 304 ms 72.14.219.192
10 472 ms 442 ms 345 ms 64.233.174.2
11 313 ms 310 ms 292 ms 66.249.94.6
12 452 ms 496 ms 584 ms 209.85.248.53
13 * * * Request timed out.
14 184 ms 184 ms 164 ms ye-in-f103.1e100.net [74.125.140.103]

Trace complete.

Glorious Shitstream DSL service tonight.

Blazing speeds!

So they give me shit all day long until it's fixed now I suppose...



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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 326 ms 292 ms 322 ms h1.116.17.98.dynamic.ip.windstream.net [98.17.11
6.1]
3 347 ms 364 ms 356 ms h234.28.189.173.static.ip.windstream.net [173.18
9.28.234]
4 560 ms 542 ms 553 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 411 ms 452 ms 493 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 532 ms 532 ms 454 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 625 ms 574 ms 384 ms h108.222.39.162.dynamic.ip.windstream.net [162.3
9.222.108]
8 138 ms 113 ms 105 ms h186.47.187.173.static.ip.windstream.net [173.18
7.47.186]
9 325 ms 364 ms 429 ms 72.14.219.192
10 509 ms 546 ms 554 ms 72.14.239.100
11 509 ms 537 ms 434 ms 66.249.94.20
12 253 ms 268 ms 273 ms 209.85.248.31
13 * * * Request timed out.
14 454 ms 446 ms 487 ms ye-in-f147.1e100.net [74.125.140.147]

Trace complete.

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 305 ms 339 ms 356 ms h1.116.17.98.dynamic.ip.windstream.net [98.17.11
6.1]
3 461 ms 448 ms 501 ms h232.28.189.173.static.ip.windstream.net [173.18
9.28.232]
4 549 ms 423 ms 433 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 641 ms 683 ms * h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 570 ms 534 ms 522 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 607 ms 448 ms 342 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 481 ms 511 ms 595 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 698 ms 639 ms 607 ms 72.14.219.192
10 477 ms 498 ms 538 ms 64.233.174.2
11 614 ms 642 ms 609 ms 66.249.94.6
12 635 ms 624 ms * 72.14.239.131
13 * * * Request timed out.
14 639 ms 422 ms 474 ms gh-in-f106.1e100.net [74.125.130.106]

Trace complete.

1 more week til we get fixed eh? We'll see...

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 183 ms 251 ms 274 ms h1.116.17.98.dynamic.ip.windstream.net [98.17.11
6.1]
3 295 ms 242 ms 337 ms h234.28.189.173.static.ip.windstream.net [173.18
9.28.234]
4 115 ms 126 ms 104 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 29 ms 30 ms 29 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 234 ms 264 ms 184 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 291 ms 325 ms 285 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 87 ms 77 ms 74 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 38 ms 51 ms 62 ms h13.72.102.166.static.ip.windstream.net [166.102
.72.13]
10 35 ms 34 ms 34 ms 64.233.174.2
11 446 ms 444 ms 358 ms 66.249.94.6
12 34 ms 33 ms 33 ms 72.14.239.131
13 * * * Request timed out.
14 513 ms 535 ms 507 ms gh-in-f103.1e100.net [74.125.130.103]

Trace complete.

6 More days...

Only a few more days man. Larissa and I just verified (again) that everything is set to go.

Aaron
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 371 ms 435 ms 510 ms h1.116.17.98.dynamic.ip.windstream.net [98.17.11
6.1]
3 533 ms 499 ms 443 ms h232.28.189.173.static.ip.windstream.net [173.18
9.28.232]
4 534 ms 420 ms 419 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 471 ms 544 ms 372 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 390 ms 407 ms 410 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 418 ms 453 ms 415 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 441 ms 385 ms 417 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 447 ms 501 ms 438 ms 72.14.219.192
10 118 ms 47 ms 52 ms 64.233.174.2
11 34 ms 34 ms 34 ms 66.249.94.6
12 346 ms 294 ms 270 ms 72.14.239.131
13 * * * Request timed out.
14 35 ms 35 ms 34 ms gh-in-f106.1e100.net [74.125.130.106]

Trace complete.

5 more days. =p

Getting closer. The engineers are probably getting tired of Larissa checking with them everyday. In the mean time have a good weekend boss.

Aaron
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com

You too man.. I hope after the deadline is met things will be back in working order. *Fingers Crossed*

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 172 ms 193 ms 186 ms h1.116.17.98.dynamic.ip.windstream.net [98.17.11
6.1]
3 228 ms 216 ms 201 ms h238.28.189.173.static.ip.windstream.net [173.18
9.28.238]
4 339 ms 372 ms 358 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 237 ms 146 ms 147 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 465 ms 523 ms 529 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 34 ms 33 ms 35 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 235 ms 281 ms 339 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 69 ms 107 ms 156 ms h13.72.102.166.static.ip.windstream.net [166.102
.72.13]
10 278 ms 202 ms 143 ms 64.233.174.2
11 34 ms 35 ms 33 ms 66.249.94.6
12 38 ms 33 ms 32 ms 72.14.239.127
13 * * * Request timed out.
14 108 ms 94 ms 93 ms gh-in-f105.1e100.net [74.125.130.105]

Trace complete.

4 days left

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 503 ms 422 ms 300 ms h1.116.17.98.dynamic.ip.windstream.net [98.17.11
6.1]
3 364 ms 406 ms 443 ms h238.28.189.173.static.ip.windstream.net [173.18
9.28.238]
4 282 ms 312 ms 322 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 149 ms 234 ms 369 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 271 ms 311 ms 335 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 308 ms 387 ms 407 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 367 ms 353 ms 314 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 320 ms 284 ms 256 ms h13.72.102.166.static.ip.windstream.net [166.102
.72.13]
10 325 ms 312 ms 254 ms 64.233.174.2
11 266 ms 325 ms 327 ms 66.249.94.6
12 224 ms 186 ms 227 ms 209.85.254.247
13 * * * Request timed out.
14 464 ms 489 ms 430 ms gh-in-f105.1e100.net [74.125.130.105]

Trace complete.

3 more days. They better hope it is fixed...

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 533 ms 577 ms 456 ms h1.8.189.173.dynamic.ip.windstream.net [173.189.
8.1]
3 304 ms 282 ms 263 ms h234.28.189.173.static.ip.windstream.net [173.18
9.28.234]
4 84 ms 77 ms 83 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 188 ms 220 ms 246 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 173 ms 184 ms 209 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 219 ms 235 ms 220 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 241 ms 226 ms 225 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 271 ms 262 ms 277 ms h13.72.102.166.static.ip.windstream.net [166.102
.72.13]
10 176 ms 236 ms 146 ms 72.14.239.100
11 82 ms 74 ms 67 ms 66.249.94.24
12 513 ms 524 ms 471 ms 72.14.239.131
13 * * * Request timed out.
14 94 ms 95 ms 154 ms gh-in-f105.1e100.net [74.125.130.105]

2 more days. 9:30 in the morning and you can't do anything.

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 409 ms 416 ms 433 ms h1.8.189.173.dynamic.ip.windstream.net [173.189.
8.1]
3 321 ms 367 ms 312 ms h236.28.189.173.static.ip.windstream.net [173.18
9.28.236]
4 409 ms 438 ms 342 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 175 ms 177 ms 266 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 213 ms 153 ms 94 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 203 ms 138 ms 157 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 179 ms 199 ms 255 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 252 ms 199 ms 224 ms 72.14.219.192
10 290 ms 360 ms 363 ms 64.233.174.2
11 582 ms 584 ms 399 ms 66.249.94.22
12 132 ms 112 ms 119 ms 209.85.240.82
13 244 ms 238 ms 380 ms 72.14.237.218
14 202 ms 177 ms 202 ms 209.85.250.199
15 272 ms 242 ms 185 ms dfw06s07-in-f19.1e100.net [74.125.227.83]

Trace complete.

All day long... another waste of a day to do stuff online.

I feel your pain man. I left Hughes.net for Windstream 1) for a job, 2) because Windstream came available to me.

Right now, my latency and download speed are not as good as hughesnet. The only drawbacks for satellite are the cap the the huge price. I hope the windstreamdirect people can help me or at least acknowledge it. Support tells me to reboot my modem etc everytime. Dont they know that I do that 10-20 times a day just to see if it will help and it doesnt.

in the evenings i like to play fps's to relieve stress. that is not an option with latency over 1000ms

you are not alone bodybagger
--
XBOX Live Gamertag - Boc3phus

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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 * 440 ms 411 ms h1.8.189.173.dynamic.ip.windstream.net [173.189.
8.1]
3 455 ms 401 ms 452 ms h238.28.189.173.static.ip.windstream.net [173.18
9.28.238]
4 591 ms 542 ms 479 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 337 ms 273 ms 289 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 420 ms 344 ms 336 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 349 ms 361 ms 363 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 536 ms 585 ms 533 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 482 ms 364 ms 328 ms h13.72.102.166.static.ip.windstream.net [166.102
.72.13]
10 433 ms 566 ms 595 ms 64.233.174.2
11 563 ms * 513 ms 66.249.94.22
12 461 ms 517 ms 602 ms 209.85.254.249
13 * * * Request timed out.
14 * 524 ms 492 ms gh-in-f147.1e100.net [74.125.130.147]

Trace complete.

We tried to do some BGs in WoW just now.. the first one wasn't too bad at 300-400ms.. but just now we logged because we were over 1900ms. I gd hate Windstream so much.

Trying to play League of Legends here. Same boat. Canton, GA here.

WTF is Windstream doing? They have to know that this is unacceptable right?

same here i was playing LoL like 5 mins ago couldnt even see my champ move reconecting every 10 secs.. its got nothing but worse everyday i dont see how its legal to do this

In your terms of service they state "up to" X speed. They do not guarantee you will actually get that speed. They make sure to cover their asses with a play on words. Basically they can "sell" you 3,6,12 mbps and if they only give you one, they are free and clear. If you're stuck in a rural area with no other choice they know they've really got you over a barrel and can do whatever the hell they please.

At work now.. but yesterday the swap was completed. Our 3Mb line never dropped below 3Mb on multiple tests. Using WoW as a reference, ping times stayed steady ~45ms to an East Coast WoW server. On a good day of DSL working before we would see ~80ms constant.

Will keep an eye on how stuff goes over the next few days/weeks. Thanks to the Windstream techs on this forum for sticking with us here and pushing for these resolution dates.

Outstanding! Keep us updated!

Aaron & Larissa
CRC Data Tier II
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com

Congrats Bodybagger! I'm sure you are pumped for this. My ETR is for February so i'm hoping to update my post soon with good news as well...(fingers crossed). Keep us updated on how efficient your line stays.

Dan