The hop between 213.140.36.86 and 213.140.36.83, which is TELEFONICA GLOBAL SOLUTIONS SL in Brazil is very suspect, as that is a pretty big ping change and packet loss for being the same network node.
That is a sign of a hardware defect or load imbalance issue on their end.
The next jump in ping and higher packet loss is the jump to and within ntt.net, which is the NA network that SE's server is attached too.
So, likely it's the Brazil network's hardware that are triggering the latency and packet loss, of which then is added upon making the jump from Brazil to the US.
These are things that neither SE nor you can fix directly, it's up to those in-the-middle ISPs and networks to fix on their end.
The reason why VPNs can
sometimes fix issues like these are in that they
may direct the network traffic via different in-the-middle ISPs that
may have better hardware and load balance, so that bad or overloaded nodes are skipped, resulting in a better connection.
If you want to know more about your Ping Plotter numbers:
- The first two hops are your PC to the Router
- Hop 3 is the modem, with 4 and 5 being the connection from the modem to the local trunk nodes to your ISP
- Hop 6 is the ISP, WIN EMPRESAS S.A.C. in Peru
- Hop 7 is the jump from Peru to Brazil's TELEFONICA GLOBAL SOLUTIONS SL, with 8 and 9 one of their network nodes (these two IPs are on the same network switch device) and it is likely an exit node for hop 10
- Hop 10 is an exit node of Brazil's TELEFONICA GLOBAL SOLUTIONS SL to trans-cable from there to Miami Florida, USA
- Hop 12 ~ 15 are nnt.net hops from Miami to Los Angles California, USA
- Hop 16 ~ 18 are nnt.net Sacramento California nodes, that exit to Square Enix server which is hop 19