It is extremely unlikely that it is a player ISP issue.
The issue lies in florida somewhere. When doing something like traceroute you get something along the lines of this:
|
Source code
|
1
2
3
4
5
6
7
8
9
10
11
|
1 <1 ms <1 ms <1 ms local
2 7 ms 4 ms 3 ms 10.32.63.120
3 6 ms 6 ms 6 ms G0-10-3-2.NYCMNY-LCR-21.verizon-gni.net [130.81.105.234]
4 27 ms 51 ms 56 ms 130.81.151.228
5 7 ms 7 ms 9 ms 0.xe-11-2-0.BR2.NYC4.ALTER.NET [152.63.20.221]
6 7 ms 7 ms 7 ms 204.255.168.190
7 37 ms 37 ms 37 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net [64.212.16.166]
8 49 ms 50 ms 50 ms border1.po1.bbnet1.mia007.pnap.net [69.25.0.18]
9 79 ms 80 ms 76 ms vaultnet-7.border2.mia007.pnap.net [69.25.48.142]
10 78 ms 80 ms 75 ms po1-car3.vaultnetworks.com [206.253.168.142]
11 98 ms 94 ms 97 ms ROM-US-WORLD1 [206.253.173.50]
|
The first item is your own local connections, every point after that is a major network switch that data has to route through. The last entry is of course the actual RoM server. (or the target of what you tracerouted) The entry right before that is the datacenter connection. If that "po1-car3.vaultnetworks.com" is the issue, then it is the datacenter's problem.
The issue has been happening across the servers for months however it isn't a ping issue, it is dropped packets. Somewhere in the routing of the internet between georgia and florida is getting between 2-6% packet loss. Certain regions will experience this due to routing, east coast being very predominant.
You can check for yourself with pingtest.net and find that you will have 0 packet loss to nearby states, 0% packet loss to states on the opposite coast, 0% ping loss to georgia. When I've experienced connection issues/lag there was significant ping loss to the florida orlando/tampa servers. Otherwise it shows normal (0%)