Still having ping issues


#1

I’ve tried posting this in multiple threads but I haven’t gotten any help yet. I’m located in Southern California and I normally have around 30 ping. Every time I get on now, I get around 200, and somehow less on Asia servers.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.254 - 0 294 294 1 2 35 2
8.37.119.1 - 0 294 294 2 4 52 5
4.16.28.13 - 0 294 294 10 12 50 12
No response from host - 100 59 0 0 0 0 0
ae-24-0.ebr3.SanJose5.Level3 .net - 0 294 294 23 25 63 26
ae-26-26.ebr3.SanJose1.Level3 .net - 0 294 294 22 24 50 25
ae-1-3.edge1 .SanJose2 .Level3 .net - 0 294 294 24 25 68 25
4.59.0.226 - 0 294 294 23 25 68 25
94.142.98.21 - 0 294 294 100 102 143 102
94.142.122.30 - 0 294 294 193 195 224 194
176.52.252.175 - 0 294 294 195 198 242 196
No response from host - 100 59 0 0 0 0 0
186-148-22-133. static. mundo .movistar.cl - 0 294 294 194 196 229 195
186-148-22-134. static. mundo. movistar.cl - 0 294 294 194 196 216 197
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
No response from host - 100 59 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Preformatted text

Edit: Blizzard did something and they fixed it :slight_smile:


#2

They are still in the information-gathering stage of resolving this issue. Follow this thread for further communication: