HE Peering Issue

I have been in contact with some admins from NFO servers recently as well as a few months back in October.

I sent them a few trace-routes from my IP address to one of the servers they Host for Battlefield 4 because of some unusually high latency I was getting. Long story short the issue came back recently and they referred to it as a HE Peering Issue that they are attempting to route around so that I can still get reasonable latency. For the most part they have been successful but they wanted me to inform Cox of these issues.

I'm not exactly sure what information will be beneficial for the Cox technicians so I am posting here so that they can tell me who to inform and what information they need.

Here is a summary of one of the responses the NFO admins gave me in an email:

"Previously, Cox was overloading its connection to Level3 in Phoenix, so I had to force our system to avoid using Level3 to reach Cox. That rule is still in place.

Tonight, Cox was overloading its connections to HE, Tata, and some other providers in Chicago, and that was causing high latencies."

Hopefully that makes sense to somebody and I can post more information if necessary. I still have some old trace-route logs from when the problems were occurring that I can post as well.