dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
71

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger

Premium Member

[Troubles] Re: I'm about to lose it


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 402 ms 446 ms 436 ms h1.8.189.173.dynamic.ip.windstream.net [173.189.
8.1]
3 347 ms 416 ms 517 ms h234.28.189.173.static.ip.windstream.net [173.18
9.28.234]
4 431 ms 319 ms 283 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 191 ms 290 ms 383 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 545 ms 576 ms 321 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 219 ms 252 ms 262 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 317 ms 167 ms 131 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 439 ms 467 ms 600 ms h13.72.102.166.static.ip.windstream.net [166.102
.72.13]
10 128 ms 49 ms 49 ms 64.233.174.2
11 378 ms 380 ms 353 ms 66.249.94.22
12 243 ms 273 ms 309 ms 72.14.239.127
13 * * * Request timed out.
14 103 ms 64 ms 38 ms gh-in-f147.1e100.net [74.125.130.147]

Trace complete.

Just got home.. oh look.. time to do nothing online once again.
Bodybagger

Bodybagger

Premium Member

Bodybagger

Bodybagger

Premium Member

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 156 ms 119 ms 115 ms h1.196.21.98.dynamic.ip.windstream.net [98.21.19
6.1]
3 178 ms 251 ms 287 ms h234.28.189.173.static.ip.windstream.net [173.18
9.28.234]
4 402 ms 540 ms * h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 426 ms 443 ms 527 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 575 ms 490 ms 293 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 197 ms 244 ms 226 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 275 ms 304 ms 268 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 261 ms 317 ms 343 ms 72.14.219.192
10 304 ms 336 ms 335 ms 72.14.239.100
11 398 ms 406 ms 518 ms 66.249.94.20
12 471 ms 470 ms 465 ms 72.14.239.131
13 * * * Request timed out.
14 315 ms 399 ms 199 ms gh-in-f147.1e100.net [74.125.130.147]

Trace complete.

Pretty much the entire weekend once again. Giving it until the ETR date of Dec 31st then I'm looking for legal action.
Bodybagger

Bodybagger

Premium Member


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

1 1 ms 1 ms 1 ms CISCO17033 [192.168.1.1]
2 423 ms 413 ms 450 ms h1.196.21.98.dynamic.ip.windstream.net [98.21.19
6.1]
3 418 ms 428 ms 426 ms h238.28.189.173.static.ip.windstream.net [173.18
9.28.238]
4 475 ms 505 ms 454 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 583 ms 455 ms 259 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 466 ms 438 ms 373 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 115 ms 126 ms 169 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 70 ms 51 ms 96 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 211 ms 319 ms 308 ms 72.14.219.192
10 227 ms 211 ms 262 ms 64.233.174.2
11 527 ms 386 ms 388 ms 66.249.94.6
12 596 ms 408 ms 387 ms 209.85.240.82
13 421 ms 428 ms 480 ms 72.14.237.218
14 478 ms 464 ms 541 ms 216.239.47.54
15 525 ms 451 ms 464 ms dfw06s03-in-f20.1e100.net [74.125.227.20]

Trace complete.

Cheers to your shitty ass internet Windstream.
Bodybagger

Bodybagger

Premium Member


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 240 ms 171 ms 107 ms h1.8.189.173.dynamic.ip.windstream.net [173.189.
8.1]
3 330 ms 348 ms 386 ms h234.28.189.173.static.ip.windstream.net [173.18
9.28.234]
4 560 ms 587 ms 569 ms h71.207.190.173.static.ip.windstream.net [173.19
0.207.71]
5 225 ms 291 ms 330 ms h20.21.213.151.static.ip.windstream.net [151.213
.21.20]
6 440 ms 443 ms 477 ms h66.28.189.173.static.ip.windstream.net [173.189
.28.66]
7 341 ms 309 ms 342 ms h106.254.213.151.static.ip.windstream.net [151.2
13.254.106]
8 548 ms 567 ms 579 ms h9.254.213.151.static.ip.windstream.net [151.213
.254.9]
9 102 ms 85 ms 70 ms h13.72.102.166.static.ip.windstream.net [166.102
.72.13]
10 421 ms 452 ms 486 ms 64.233.174.2
11 577 ms 495 ms 431 ms 66.249.94.6
12 385 ms 372 ms 331 ms 72.14.239.131
13 * * * Request timed out.
14 32 ms 31 ms 31 ms gh-in-f105.1e100.net [74.125.130.105]

Trace complete.

3:15pm 12-23-12
Bodybagger

Bodybagger

Premium Member

4 more days til the ETR and still pretty damn terrible...
malianx
join:2012-11-24
Clarendon, TX

malianx

Member

The estimated repair date for you heh

I've been given ten dates in the last month, some of which ranging to July 2013

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger

Premium Member

They've actually stuck by this one for the past 3 months. As in, it hasn't changed from calling t1 or t2. The local techs on the other hand have given ~June 2013 dates. I cannot begin to list the dates for repairs that we've been given for the past 3 years dealing with this garbage. It's really sad that damn 4g LTE service gives a steady 35/15 while being hardwired on DSL we usually don't even see 2/0.6! If the data cap BS wasn't totally useless we would've switched to Verizon 4g (Home Fusion) long ago.

Anyway, we were told from a local tech that the contractor still has the fiber they just finished up with.. it won't be released until the 1st of the year. I love how t1 and t2 can tell me our ETR is Dec 31st when the contractors aren't releasing the lines until the 1st. Windstream loves to make up ETR dates just to shut the customer up. Then when the date arrives and the DSL is still shittastic, they give you another one so you will shut up again. It's not the t2 or t1 CS reps' fault. It's all corperate. All they do is look over a list of notes and have no earthly idea wtf is going on in anybody's area.
borisbadenov
join:2005-12-05
Barbourville, KY

borisbadenov

Member

speaking to a field tech in my area i was told that they had till 2014 to have repairs completed that was the deal when they took the money and it would probably take that long for us even though i have been given 2 different dates as well

Windstream
Premium Member
join:2009-03-31
Twinsburg, OH

Windstream to Bodybagger

Premium Member

to Bodybagger
Bodybagger- Larissa just sent you (and your brother) some really good news in the Direct Forum. Before you ask . . .yes it is confirmed!

Aaron
Specialist II

Piggie
Just A Pig With A Computer
Premium Member
join:2005-11-23
Orange Springs, FL

Piggie

Premium Member

So why hide good news in a private forum? Maybe I should ask about my area again since I never got an answer, yet I can see new fiber in the ground (when it was installed) and many new cabinets on the road side, including where my copper ends currently giving me my SDSL (slow DSL).

Why not share it? Part of the secret society of Windstream management?

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger to Windstream

Premium Member

to Windstream
Lol.. cmon man.. Well atleast the ETR dates are moving just a few weeks instead of 6+ months. =\

The way the tech described it was that the most utilized areas that had the worst problems were going to be completed first. I know that Cameron, SC is a much larger area (and where the money of this county lives) than our small area outside of Saint Matthews. I would've assumed that Cameron would've been the number 1 place to get up and running before anyone else around here. (I'm keeping a track on Cameron as well for people that do not post on forums)

When you guys say the engineer, are you referring to the local field engineer in charge of the project? I'm just hoping the information you guys are redirecting is coming from a legit source.
Bodybagger

Bodybagger to Piggie

Premium Member

to Piggie
Piggie, they usually like to keep the news relating to certain people/areas relevant to the person/area that have the issue. Basically my ETR date was moved again. But only a few weeks compared to the normal 3-6 months away.

BTW there are only 2 techs that work the forum. Aaron just fills in when he has the time anymore and we thank him for that. And of course, my issues are irrelevant to anyone else outside of Saint Matthews, SC. They may be the same exact issues, over sold equipment and not enough backhaul, but each area is different.

I'm not sticking up for Windstream in any way, shape or form... but I will stick up for these techs in here. Just look at how much they have on their plates just in the forum alone.

Windstream
Premium Member
join:2009-03-31
Twinsburg, OH

Windstream

Premium Member

Bodybagger- The new date that Larissa provided is pretty much set in stone to get you and your brother moved to the new equipment. That should eliminate your latency issues. Of course we can not promise that there wont be some bugs with the new equipment while people are getting moved to it after you. But Larissa and I both checked, and reconfirmed that you guys will get moved to the new equipment. I am very confident based on the info that we were given that Saint Mathews will not be over-utilized in the very near future.
Regarding working in the forums, Pat and Larissa both are in the Direct/Secure forums full time. I will be in the Public forums at least couple hours a day for the foreseeable future. Have a good New Year BodyBagger.

Aaron
Specialist II

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger

Premium Member

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

Windstream
Premium Member
join:2009-03-31
Twinsburg, OH

Windstream

Premium Member

You too Boss.

Piggie
Just A Pig With A Computer
Premium Member
join:2005-11-23
Orange Springs, FL

Piggie

Premium Member

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.

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger

Premium Member

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

Piggie
Just A Pig With A Computer
Premium Member
join:2005-11-23
Orange Springs, FL

Piggie

Premium Member

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.

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger

Premium Member


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.
Bodybagger

Bodybagger

Premium Member


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.
Bodybagger

Bodybagger

Premium Member



Blazing speeds!
Bodybagger

Bodybagger

Premium Member

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.
Bodybagger

Bodybagger

Premium Member


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...
Bodybagger

Bodybagger

Premium Member


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...

Windstream
Premium Member
join:2009-03-31
Twinsburg, OH

Windstream

Premium Member

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

Aaron
Specialist II

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger

Premium Member


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

Windstream
Premium Member
join:2009-03-31
Twinsburg, OH

Windstream

Premium Member

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

Bodybagger
Premium Member
join:2010-03-30
Saint Matthews, SC

Bodybagger

Premium Member

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

Bodybagger

Premium Member


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