Packet loss in north Phoenix, AZ

i too have seen a 3% packet loss which has been affecting my upload speed which is what i need. my upload speed has been dropping from the usual 30 mbps to 5 mbps to .74 kbps over the last week. 

Greetings Chris!

Thank you for answering. So far I've had yet another tech (total of 3). House is free of noise. Still getting the noise from the tap out to the house. So far we have filed two maintenance requests.

I thought we had finally fixed the issue last night at around 7:15pm AZ time because I had a perfect connection until I went to sleep. Today, however, the problem is back with a vengeance: according to my ping software, we are at about 6% packet loss to three different servers. 

I called the tech 1 team again and they identified an 8% loss regardless of how many ping tests they did. We have another tech coming tomorrow.

What do you think may be happening and what can I do to get things back to being perfect?

PS I copied ping tests and tracerts for you, all ran from Command Prompt

Tracing route to cox.com [68.99.123.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 8 ms 7 ms 10.114.32.1
3 7 ms 7 ms 7 ms 100.127.64.58
4 8 ms 9 ms 8 ms wsip-70-166-189-130.ph.ph.cox.net [70.166.189.13
0]
5 56 ms 56 ms 53 ms dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
6 68 ms 54 ms 57 ms 68.1.15.234
7 62 ms 53 ms 53 ms 68.99.123.4
8 57 ms * 56 ms ww2.cox.com [68.99.123.161]

Trace complete.

Ping statistics for 68.99.123.161:
Packets: Sent = 292, Received = 280, Lost = 12 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 75ms, Average = 54ms

Tracing route to bungie.net [104.20.29.30]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 6 ms * 10.114.32.1
3 * * 11 ms 100.127.64.56
4 8 ms 16 ms 10 ms wsip-70-166-189-128.ph.ph.cox.net [70.166.189.12
8]
5 11 ms 8 ms 9 ms 68.1.0.187
6 14 ms 9 ms 9 ms 162.158.140.253
7 8 ms 9 ms 7 ms 104.20.29.30

Trace complete.

Ping statistics for 104.20.29.30:
Packets: Sent = 257, Received = 243, Lost = 14 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 29ms, Average = 10ms

Tracing route to google.com [216.58.217.206]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 7 ms 7 ms 10.114.32.1
3 9 ms 13 ms 8 ms 100.127.64.56
4 9 ms 9 ms 9 ms wsip-70-166-189-128.ph.ph.cox.net [70.166.189.12
8]
5 25 ms 23 ms 27 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
6 21 ms 21 ms 21 ms 72.14.215.221
7 20 ms 21 ms 22 ms 216.239.51.33
8 21 ms 22 ms 21 ms 216.239.51.55
9 20 ms 28 ms 19 ms lax17s05-in-f14.1e100.net [216.58.217.206]

Trace complete.

Ping statistics for 216.58.193.206:
Packets: Sent = 301, Received = 291, Lost = 10 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 43ms, Average = 21ms

Interesting. I just replied to Chris with some tests I just ran in the Windows Command Prompt (ping and tracert). Want to post yours to see if you are having a similar issue?

Let me know if you need help with the tests. I also use PingTracer, a free tool that graphs pings so you can visually identify them if you want to give that a try.

@ChrisL The tech just left the house. Very knowledgeable. Unfortunately, the packet loss symptoms disappeared a couple of minutes before he arrived, and throughout the hour he was here, we could not reproduce them. =( On the bright side, I have no issues right now but not sure how long it will last. 

Ironically, as I am typing this, I just began losing packets again. Not sure what to do now.

ChrisL said:
@ZeroXG

Pings are OK for detecting that there may be a problem but won't tell you anything useful about the problem. You could try a utility called pingplotter and see if it catches anything.