Ping spikes could use help

I've been having terrible ping spikes for the past week on Washington DC server. I ran WinMTR this is the result
http://imgur.com/a/cU2w4

"

Eternalgameplayer wrote:

I've been having terrible ping spikes for the past week on Washington DC server. I ran WinMTR this is the result
http://imgur.com/a/cU2w4

You cut off vital information in that WinMTR report. Please run a WinMTR trace route, then copy and paste the results here. Guide: https://www.pathofexile.com/forum/view-thread/1377789/page/1.

Also, according to what you have there in that screen cap, it looks like you're experiencing packet loss and ridiculously high lag from your ISP and/or router. But I doubt that report is showing correct information since you cut off vital WinMTR version information at the bottom. Please re-test and include the latest *full* report.

https://pastebin.com/zgjx9hii Here is an updated pastbin with the correct gateway

Second hop is where your issues start. Packet loss that is carrying forward = bad.

Try restarting your router and modem. Turn them off and unplug them for a minute or so. Plug 'em back in and re-run a trace. If the packet loss goes away, great, if it stays, not so.

If the packet loss doesn't go away, you'll need to contact your ISP. Tell them you are getting packet loss that is affecting your ability to do what you want to online and make certain they see the MTR's, as that is the proof that they will need to see that something is borked.

As Dune mentioned, work with your ISP.

http://geoiplookup.net/ip/96.120.21.65
It looks like you have Comcast/Xfinity in the Houston area. This hope is probably your local neighborhood box with network equipment inside. Given that the season is changing, the temperatures could be affecting the attenuation of that broadband, coaxial-based connection. If the attenuation goes too far out of spec, it can be forced to reset the connection every so often to correct itself. Usually the upstream is to blame for this, as the downstream is much more tolerant of changes to attenuation. So absolutely contact Comcast with this issue.

But if this Houston area IP is correct, why are you connecting to the DC servers? If it's not correct, then no worries. But at least we know it's Comcast/Xfinity that owns that IP range, so that explains the possibly causes of that local box issue.