I’ve wasted a lot of hours on this dang problem (6+ hours).

My web host tracked it down and said the problem is with Cox.

Anyone else seeing Cox acting wonky?

Anyone know a human being at Cox I can contact?

Below is the email from the support desk at my webhost, pair.com.

====================

When we perform a traceroute back in your direction, it appears that there is an issue with asynchronous routing between Level3 and Cox. What the amounts to is that packets are not taking the same route in both directions or even necessarily each time in one direction, resulting in packets either getting eventually lost or being transmitted in a fashion that causes the connection to time and/or error out.

This is something that we would suggest bringing to the attention of your provider, Cox, because they will need to work with their upstream provider, which is Level3, to resolve this. You can forward on our traceroute, which I will paste below, to aid them in tracking down the issue.

Traceroute:

traceroute to 68.14.246.9 (68.14.246.9), 64 hops max, 40 byte packets
1 gw09.pair.net (209.68.1.188) 0.429 ms 0.609 ms 1.029 ms
2 192.168.1.8 (192.168.1.8) 9.480 ms 1.409 ms 0.451 ms
3 ge-6-3-187.car1.Philadelphia1.Level3.net (4.78.152.97) 20.470 ms 20.728 ms 20.983 ms
4 ae-11-11.car2.Philadelphia1.Level3.net (4.69.133.166) 20.944 ms 20.742 ms 20.936 ms
5 ae-6-6.ebr1.NewYork1.Level3.net (4.69.133.170) 22.481 ms 23.232 ms 22.484 ms
6 ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 34.962 ms
ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 35.291 ms
ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 22.551 ms
7 ae-3-89.edge1.NewYork1.Level3.net (4.68.16.142) 22.758 ms
ae-1-69.edge1.NewYork1.Level3.net (4.68.16.14) 22.830 ms
ae-3-89.edge1.NewYork1.Level3.net (4.68.16.142) 23.130 ms
8 COX-COMMUNI.edge1.NewYork1.Level3.net (4.71.186.26) 34.210 ms 33.799 ms 33.948 ms
9 chnddsrj02-ge710.0.rd.ph.cox.net (68.1.0.169) 87.935 ms
chnddsrj01-ge710.0.rd.ph.cox.net (68.1.0.165) 87.691 ms
chnddsrj02-ge710.0.rd.ph.cox.net (68.1.0.169) 87.765 ms 10 ssctsysc01-te-9-2.ph.ph.cox.net (70.169.72.95) 89.579 ms 89.739 ms 89.913 ms
11 ip68-2-4-10.ph.ph.cox.net (68.2.4.10) 89.394 ms 90.116 ms 90.454 ms

Short ping flood showing packet loss:

# ping -f -c 1000 68.2.4.10
PING 68.2.4.10 (68.2.4.10): 56 data bytes …………………………….
— 68.2.4.10 ping statistics —
1000 packets transmitted, 968 packets received, 3.2% packet loss round-trip min/avg/max/stddev = 93.955/95.685/105.928/0.609 ms

====================