Smith,
These were completed on 1:00pm 11/11/12. (Connection is not bad at this time)
Please let me know your thoughts. I hope there is help for me yet because I am more that frustrated with Frontier. Over 4 years have I suffered with their so call high speed internet. With no hope in sight.
Set at 2624/640 but I believe my area is provisioned for 1mbps.
Normal Run
C:\Windows\system32>ping -t 74.42.149.41
Pinging 74.42.149.41 with 32 bytes of data:
Reply from 74.42.149.41: bytes=32 time=91ms TTL=62
Reply from 74.42.149.41: bytes=32 time=71ms TTL=62
Reply from 74.42.149.41: bytes=32 time=42ms TTL=62
Reply from 74.42.149.41: bytes=32 time=19ms TTL=62
Reply from 74.42.149.41: bytes=32 time=20ms TTL=62
Reply from 74.42.149.41: bytes=32 time=33ms TTL=62
Reply from 74.42.149.41: bytes=32 time=36ms TTL=62
Reply from 74.42.149.41: bytes=32 time=35ms TTL=62
Reply from 74.42.149.41: bytes=32 time=22ms TTL=62
Reply from 74.42.149.41: bytes=32 time=18ms TTL=62
Reply from 74.42.149.41: bytes=32 time=42ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=21ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=20ms TTL=62
Reply from 74.42.149.41: bytes=32 time=17ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=19ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=29ms TTL=62
Ping statistics for 74.42.149.41:
Packets: Sent = 23, Received = 23, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 91ms, Average = 28ms
Control-C
^C
Load Run
C:\Windows\system32>ping -t 74.42.149.41
Pinging 74.42.149.41 with 32 bytes of data:
Reply from 74.42.149.41: bytes=32 time=441ms TTL=62
Reply from 74.42.149.41: ┌────────────────────────────┐
Reply from 74.42.149.41: │Enter char to copy up to: │
Reply from 74.42.149.41: └────────────────────────────┘
Reply from 74.42.149.41: bytes=32 time=462ms TTL=62
Reply from 74.42.149.41: bytes=32 time=479ms TTL=62
Reply from 74.42.149.41: bytes=32 time=465ms TTL=62
Reply from 74.42.149.41: bytes=32 time=398ms TTL=62
Reply from 74.42.149.41: bytes=32 time=396ms TTL=62
Reply from 74.42.149.41: bytes=32 time=444ms TTL=62
Reply from 74.42.149.41: bytes=32 time=392ms TTL=62
Reply from 74.42.149.41: bytes=32 time=386ms TTL=62
Reply from 74.42.149.41: bytes=32 time=400ms TTL=62
Reply from 74.42.149.41: bytes=32 time=395ms TTL=62
Reply from 74.42.149.41: bytes=32 time=426ms TTL=62
Reply from 74.42.149.41: bytes=32 time=425ms TTL=62
Reply from 74.42.149.41: bytes=32 time=390ms TTL=62
Reply from 74.42.149.41: bytes=32 time=368ms TTL=62
Reply from 74.42.149.41: bytes=32 time=463ms TTL=62
Reply from 74.42.149.41: bytes=32 time=373ms TTL=62
Reply from 74.42.149.41: bytes=32 time=372ms TTL=62
Ping statistics for 74.42.149.41:
Packets: Sent = 21, Received = 21, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 368ms, Maximum = 479ms, Average = 418ms
»
/testhistory/1694608/8addb 
