OldPissy
join:2002-06-10
Carmichael, CA
| Re: Sacramento 95825 I Pay 50 bucks for this LAG Help Hey people just face it.. AT&T SUCKS DONKEY ?????!! They will never fix this crap until in our lifetimes. They lie, blow smoke up our as-! Mislead all the time & constantly pass the buck. Never ever will AT&T accept responsibility for the crappy services they give us. They to busy changing they're website and running adds on the home page. Not to mention expanding to other areas before fixing what they have here.. I have over 112 tickets going to tasc for the same crap since January 03...
Look at these & see why I have a tude. Like I don't have a damn reason.
PING 2 GATEWAY @ 1745HRS
H:\DOCS\ATT-SUCKS>ping 12.246.104.1
Pinging 12.246.104.1 with 32 bytes of data:
Reply from 12.246.104.1: bytes=32 time=1975ms TTL=255
Reply from 12.246.104.1: bytes=32 time=1793ms TTL=255
Reply from 12.246.104.1: bytes=32 time=1968ms TTL=255
Reply from 12.246.104.1: bytes=32 time=2843ms TTL=255
Ping statistics for 12.246.104.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1793ms, Maximum = 2843ms, Average = 2144ms
==============================
Ping statistics for 12.246.104.1:
Packets: Sent = 336, Received = 335, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 1561ms, Average = 510ms
Control-C
===================================
THIS IS AFTER THE NEW CMTS HERE
H:\DOCS\ATT-SUCKS>ping 10.185.0.1 -n 10
Pinging 10.185.0.1 with 32 bytes of data:
Reply from 10.185.0.1: bytes=32 time=423ms TTL=255
Reply from 10.185.0.1: bytes=32 time=267ms TTL=255
Reply from 10.185.0.1: bytes=32 time=373ms TTL=255
Reply from 10.185.0.1: bytes=32 time=335ms TTL=255
Reply from 10.185.0.1: bytes=32 time=195ms TTL=255
Reply from 10.185.0.1: bytes=32 time=327ms TTL=255
Reply from 10.185.0.1: bytes=32 time=378ms TTL=255
Reply from 10.185.0.1: bytes=32 time=253ms TTL=255
Reply from 10.185.0.1: bytes=32 time=377ms TTL=255
Reply from 10.185.0.1: bytes=32 time=319ms TTL=255
Ping statistics for 10.185.0.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 423ms, Average = 324ms
====================
TODAYS at the cmts
Pinging 10.185.0.1 with 32 bytes of data:
Reply from 10.185.0.1: bytes=32 time=153ms TTL=255
Reply from 10.185.0.1: bytes=32 time=304ms TTL=255
Reply from 10.185.0.1: bytes=32 time=253ms TTL=255
Reply from 10.185.0.1: bytes=32 time=252ms TTL=255
Reply from 10.185.0.1: bytes=32 time=246ms TTL=255
Reply from 10.185.0.1: bytes=32 time=197ms TTL=255
Reply from 10.185.0.1: bytes=32 time=244ms TTL=255
Reply from 10.185.0.1: bytes=32 time=243ms TTL=255
Reply from 10.185.0.1: bytes=32 time=473ms TTL=255
Reply from 10.185.0.1: bytes=32 time=342ms TTL=255
Ping statistics for 10.185.0.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 473ms, Average = 270ms
=======================================
TODAY AT MY GATEWAY
H:\DOCS\ATT-SUCKS>ping 12.246.125.1 -n 10
Pinging 12.246.125.1 with 32 bytes of data:
Reply from 12.246.125.1: bytes=32 time=455ms TTL=255
Reply from 12.246.125.1: bytes=32 time=420ms TTL=255
Reply from 12.246.125.1: bytes=32 time=232ms TTL=255
Reply from 12.246.125.1: bytes=32 time=272ms TTL=255
Reply from 12.246.125.1: bytes=32 time=204ms TTL=255
Reply from 12.246.125.1: bytes=32 time=367ms TTL=255
Reply from 12.246.125.1: bytes=32 time=232ms TTL=255
Reply from 12.246.125.1: bytes=32 time=147ms TTL=255
Reply from 12.246.125.1: bytes=32 time=523ms TTL=255
Reply from 12.246.125.1: bytes=32 time=379ms TTL=255
Ping statistics for 12.246.125.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 147ms, Maximum = 523ms, Average = 323ms
*************************************************
Go figure.. Some people get fixed & some get thrown to the curb.. I sure as hell wouldn't take anything AT&T says as a fact anymore. They don't even keep they're word.
Maybe if I use profanity enough they will do me a favor & close my account. I wouldn't doubt thats next since they cant or wont fix the crap.. |
