Quote Originally Posted by Gilaverde View Post
8:51 PM AZ time, 90006 disconnect. Dropping packets. Its just as bad as ever.
My first post I mistype the IP but here is my update

Ping statistics for 204.2.229.9:
Packets: Sent = 20, Received = 15, Lost = 5 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 51ms, Average = 46ms

tracert 204.2.229.9

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.0.1
3 8 ms 9 ms 9 ms 10.49.208.1
4 10 ms 10 ms 11 ms 100.127.74.22
5 23 ms 9 ms 9 ms 70.169.74.152
6 22 ms 22 ms 22 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
7 21 ms 23 ms 20 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
8 45 ms 44 ms 44 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
9 36 ms 36 ms 37 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
10 * * * Request timed out.
11 42 ms 42 ms 44 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 54 ms 51 ms 48 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
13 48 ms 48 ms * xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
14 48 ms 50 ms * 204.2.229.242
15 * 46 ms 47 ms 204.2.229.9

Trace complete.

With google IP
ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=21ms TTL=57
Reply from 8.8.8.8: bytes=32 time=47ms TTL=57
Reply from 8.8.8.8: bytes=32 time=21ms TTL=57
Reply from 8.8.8.8: bytes=32 time=47ms TTL=57

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 47ms, Average = 34ms
I reported this issue to cox again and provided all the info you guys have been posting. Told them that there are a lot of people in Arizona experiencing the same issue. They are going to open an investigation based on reports that were actually given to them. So if you haven't contacted cox to report the issue, please do.