Latency doubled since yesterday due to different route

Here is the route I’m currently on…

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

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 183 183 0 0 2 0
No response from host - 100 36 0 0 0 0 0
24-155-250-193.dyn.grandenetworks. net - 0 183 183 7 11 48 8
ae6.61.core01.gf01.dllstx.grandecom. net - 0 183 183 19 23 59 21
eqix-da1.blizzard. com - 0 183 183 20 28 95 27
ae1-br02-eqda6.as57976. net - 0 183 183 78 88 181 88
et-0-0-2-br02-swlv10.as57976. net - 0 183 183 82 89 178 83
137.221.65.122 - 0 171 171 84 655 1542 193
No response from host - 100 36 0 0 0 0 0
et-0-0-0-pe01-eqch2.as57976. net - 0 183 183 82 85 154 83
24.105.62.129 - 0 183 183 83 86 92 84
________________________________________________ ______ ______ ______ ______ ______ ______

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

And here is the route I was on for quite a while…

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

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 301 301 0 0 1 0
No response from host - 100 60 0 0 0 0 0
24-155-250-193.dyn.grandenetworks. net - 0 301 301 5 10 38 7
ae6.61.core01.gf01.dllstx.grandecom. net - 0 301 301 16 24 52 22
eqix-da1.blizzard. com - 0 301 301 21 26 54 31
ae1-br01-eqda6.as57976. net - 0 301 301 37 47 58 45
No response from host - 100 60 0 0 0 0 0
et-0-0-0-pe04-eqch2.as57976. net - 0 301 301 36 45 104 51
chi-eqch2-ia-bons-04.as57976. net - 0 301 301 38 44 77 46
24.105.62.129 - 0 301 301 38 43 78 41
________________________________________________ ______ ______ ______ ______ ______ ______

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

I’ve bolded the two nodes that seemed to of changed for the route as everything before is the same. Also seems to be where the jump in ms is coming from.

Yeah, looks like Equinix has an issue happening. You may want to open a ticket and let Blizzard know since they have a relationship with that routing peer, but I don’t think they control it.

Yes, looks to be that way. Seems it is resolved now as I’m back to my 40 or so ms.