Wily_Wizard wrote: »If you look at the stats on all your traceroutes, you can see you are fine every time until you get to 200.223.46.138, which is
xe-6-0-1.0-nyc-us-rotb-j02.telemar.net.br [200.223.46.138]
This seems to be an ISP issue in Brazil. Do you have another ISP you can try?
It looks like if you can find an ISP that connects directly to Fortaleza, Brazil or Rio de Janeiro, Brazil for a gateway, then you would have the best chance of improving your latency(ping), at least with Level 3 carriers.
http://maps.level3.com/default/#.Vqd8nWfSkUF (zoom in on Brazil)
Here's a list of ISP's
https://en.wikipedia.org/wiki/List_of_internet_service_providers_in_Brazil
Looks like later this year more fiber will be added and ping times may improve a lot if you use one of these ISPs'
https://en.wikipedia.org/wiki/Monet_(submarine_cable)
Calculando estat¡sticas para 2 segundos...
Origem aqui Este n¢/V¡nculo
Perdido/Enviado Perdido/Enviado
Salto RTT = Pct = Pct Endere‡o
0 192.168.1.4
1 0ms 0/ 1 = 0% 0/ 1 = 0% 192.168.1.1
2 16ms 0/ 1 = 0% 0/ 1 = 0% 201.10.196.82
3 28ms 0/ 1 = 0% 0/ 1 = 0% 200.199.193.137
4 45ms 0/ 1 = 0% 0/ 1 = 0% 200.199.193.157
5 48ms 0/ 1 = 0% 0/ 1 = 0% 201.10.198.112
6 --- 1/ 1 =100% 1/ 1 =100% 200.223.46.221
7 165ms 0/ 1 = 0% 0/ 1 = 0% 100.122.17.55
8 389ms 0/ 1 = 0% 0/ 1 = 0% 200.223.46.138
9 390ms 0/ 1 = 0% 0/ 1 = 0% 152.179.29.253
10 --- 1/ 1 =100% 0/ 1 = 0% 140.222.231.203
Rastreamento conclu¡do.
pathing: launcher.bethesda.net