If COX really wants to Address the issue, they would treat this as a priority, as there may be an outage that they are not aware of on there servers. They need to get information over to there Network Engineers as on my end, we can hop back to their servers let alone ping it.
tracert -d 93.182.1.143
Tracing route to 93.182.1.143 over a maximum of 30 hops
1 3 ms 1 ms 1 ms 192.168.0.1
2 10 ms 9 ms 8 ms 10.126.120.1
3 11 ms 9 ms 8 ms 100.125.184.44
4 10 ms 11 ms 10 ms 100.122.125.86
5 23 ms 22 ms 22 ms 68.1.5.134
6 22 ms 21 ms 21 ms 62.115.14.38
7 * * * Request timed out.
8 43 ms 44 ms 42 ms 62.115.116.215
9 57 ms 56 ms 55 ms 62.115.125.129
10 57 ms 56 ms 55 ms 62.115.136.200
11 * * * Request timed out.
12 140 ms 141 ms 139 ms 62.115.139.172
13 160 ms 159 ms 160 ms 62.115.141.23
14 159 ms 157 ms 158 ms 62.115.142.177
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * *
PS C:\Users\RicoGamingPAD> ping www.cox.net -t
Pinging www.cox.net [98.182.1.143] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 98.182.1.143:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Control-C
PS C:\Users\RicoGamingPAD> ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=28ms TTL=59
Reply from 8.8.8.8: bytes=32 time=22ms TTL=59
Reply from 8.8.8.8: bytes=32 time=22ms TTL=59
Reply from 8.8.8.8: bytes=32 time=22ms TTL=59
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 28ms, Average = 23ms