[Data Center USA] Ping increased. Report your changes here.

[Malzian]

So maybe the problem isn't your internet but your connection to it. I use an Ethernet cable to connect to my modem it cost me less than 20 bucks and it fixed similar issues I had been having with overwatch and dark souls back when I was using wireless.

I'm not an expert but maybe you guys should do some research about your own gear before you cry fowl.

This is a red herring and not implicity true. The biggest component of your ping does not generally come from your connection to the router and is usually somewhere in transit between your Router and the destination. For instance, I am on a FiOS connection connected to my router with a cable. Running a traceroute I get this:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 7 ms 7 ms lo0-100.NWRKNJ-VFTTP-304.verizon-gni.net [108.53.177.1]
3 9 ms 12 ms 12 ms B3304.NWRKNJ-LCR-22.verizon-gni.net [100.41.139.224]
4 * * * Request timed out.
5 * * * Request timed out.
6 9 ms 9 ms 10 ms 0.et-11-1-0.BR2.NYC4.ALTER.NET [140.222.239.35]
7 10 ms 12 ms 12 ms NTT.customer.alter.net [152.179.49.38]
8 11 ms 15 ms 14 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
9 100 ms 90 ms 89 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
10 88 ms 90 ms 89 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
11 91 ms 92 ms 92 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
12 98 ms 94 ms 97 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 96 ms 97 ms 96 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
14 97 ms 94 ms 96 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 94 ms 95 ms 96 ms 204.2.229.234
16 95 ms 96 ms 94 ms 204.2.229.9

(Yes, I know there are 2 bad hops there, nothing I can do about that.)

Notice hop 9? That's an INTERNAL connection on NTT's network (not mine) that shoots my ping up from a nice, low 15ms Max up to the 90s (maxing at 100). Now I am not going to sit here and complain that my connection is ruined (it is slower than it was, but not ruined), but you need to be aware that the vast majority of issues like this are generally not within your own network.