Transfer Aborted, Instance not Found, Falling off fly path for ages diagnosis with MTR

Hello since start of expansion many of my friends been experiencing the following connection problems such as Transfer Aborted, Instance not found and falling off the worm during fly path destination usually between lands… , one inefficient solution we came up with was playing with a VPN but it results in high pings and disconnects. this has happened before for a period during 8.3 (for reference : Continuous Issue of being stuck on Loading Screens - #203 by Rockgodx-kazzak) and with providing meaningful and useful information to blizzard’s team we were able to fix the problem. hopefully we can do the same now by providing information regarding the problem and hopefully this problem can be fixed as well.

If you have similar connection problems such as us please consider providing more information from your end with heading to this link provided by blizzard so we can work this out : https://eu.battle.net/support/en/article/2778.
(some tips for getting better results: start the program and let it run while you are stuck or having problems and also its important to let it run for at least some time maybe around 1000 hops or 2000 so there is enough evidence to check which node is causing problem.)

here are the following MTR results while having problem of falling for about 5minutes straight during taking a fly path to another land:

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

Host - % Sent Recv Best Avrg Wrst Last
DSL.2750U - 32 449 307 0 0 9 0
172.18.190.17 - 1 1008 1006 6 44 1052 8
172.18.190.9 - 1 1011 1010 6 44 1052 7
172.18.205.237 - 1 1011 1010 7 45 1067 8
172.18.196.9 - 1 1011 1010 7 45 1078 20
172.18.196.94 - 0 1014 1014 8 50 1060 11
10.10.53.217 - 1 1011 1010 8 47 1063 10
10.21.212.20 - 1 1011 1010 9 46 1075 10
10.21.212.20 - 1 1011 1010 8 46 1080 10
193.251.154.103 - 1 1009 1008 79 118 1130 84
81.52.179.220 - 1 1006 1004 79 120 1132 80
137.221.80.35 - 0 1013 1013 89 127 1151 90
137.221.65.26 - 1 962 953 93 201 4268 329
137.221.77.81 - 0 1013 1013 88 127 1151 89
137.221.66.35 - 0 1013 1013 88 125 1153 89
185.60.114.159 - 0 1013 1013 88 125 1151 90
________________________________________________ ______ ______ ______ ______ ______ ______

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

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

Host - % Sent Recv Best Avrg Wrst Last
DSL.2750U - 31 455 314 0 0 6 0
172.18.190.17 - 0 1015 1015 6 44 1061 7
172.18.190.9 - 1 1011 1010 6 44 1060 6
172.18.205.209 - 1 1008 1006 7 44 1061 7
172.18.196.25 - 0 1015 1015 7 46 1057 7
172.18.199.46 - 1 1011 1010 6 51 1208 16
172.16.46.206 - 0 1015 1015 8 50 1057 9
10.10.53.225 - 1 1011 1010 8 46 1061 10
10.21.212.20 - 1 1011 1010 8 46 1079 11
10.21.212.20 - 1 1011 1010 8 47 1058 8
85.132.90.153 - 1 1007 1005 14 53 1077 14
No response from host - 100 204 0 0 0 0 0
81.27.252.218 - 0 1014 1014 57 96 1109 58
No response from host - 100 204 0 0 0 0 0
80.64.96.219 - 0 1013 1013 95 132 1156 97
80.81.195.26 - 0 1013 1013 86 127 1156 87
137.221.80.33 - 2 950 937 91 168 4789 94
137.221.65.29 - 4 763 737 92 596 4955 317
137.221.65.75 - 4 782 757 93 548 4917 318
137.221.78.49 - 1 1009 1008 91 130 1148 94
185.60.112.158 - 0 1013 1013 91 128 1155 93
________________________________________________ ______ ______ ______ ______ ______ ______

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

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

Host - % Sent Recv Best Avrg Wrst Last
DSL.2750U - 23 532 411 0 0 12 0
172.18.190.17 - 1 1011 1010 6 42 1053 7
172.18.190.9 - 1 1003 1000 6 44 1055 6
172.18.205.233 - 1 1011 1010 7 44 1070 9
172.18.196.17 - 1 1011 1010 7 46 1068 7
172.18.199.46 - 0 1015 1015 6 51 1110 7
172.16.46.206 - 1 1007 1005 8 50 1100 10
10.10.53.225 - 0 1015 1015 8 45 1061 10
10.21.212.10 - 1 1011 1010 8 46 1065 10
10.21.212.10 - 0 1015 1015 8 45 1062 9
85.132.90.161 - 1 1003 1000 20 51 1083 21
No response from host - 100 204 0 0 0 0 0
81.27.252.218 - 1 1010 1009 63 100 1110 63
No response from host - 100 204 0 0 0 0 0
80.64.96.219 - 1 1009 1008 101 135 1148 102
80.81.195.26 - 1 1009 1008 92 133 1174 93
137.221.80.33 - 2 943 927 97 166 3549 134
137.221.65.29 - 4 766 741 97 606 4895 820
137.221.65.75 - 4 780 753 0 540 4840 880
137.221.78.49 - 1 1009 1008 97 135 1147 99
137.221.66.43 - 0 1012 1012 97 133 1155 98
185.60.112.157 - 1 1009 1008 97 133 1152 98
________________________________________________ ______ ______ ______ ______ ______ ______

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

Funny thing is using a vpn fixes all the problem it’s 100% from their side not letting us connect with a certain ip

this problem is very similar to the one we had some time ago in 8.3, it probably could be a case of the fix they applied got reverted somehow when expansion released? I’m not sure, but if you look at my MTR results you can clearly see there are some nodes with extremely high ping around 4-5k which are very similar to the ones that caused problem before as well, France and Netherlands IPs owned by Blizzard (Blizzard’s Assets).

Yeah exactly like the 8.3 problem it took them months to fix it

yep hopefully if more people provide more information maybe it could be tracked and fixed again, playing with VPN with 300-400 ping on top of servers being laggy is a very unpleasant combo man.

For a paid service it’s pathetic that we have to provide info every few months because they can’t fix their servers

I understand your frustration but it seems this problem is affecting some range of IPs and not everyone, so it could be a case specific problem which needs information from those people affected by it to solve the problem. hopefully this one gets fixed sooner if more people provide information and help their team on tackling the problem.

Having this very exact problem, im getting out of arenas when queuing skirmishes, funny thing only happens on my main, on the rest Im not having this problem