It’s been like this for almost 3 months. When i change zone or use a portal while doing dailes etc. there is this lag ms looks fine but i can’t do any action. I can see and write on chats. I can see guildies achivments etc. but i can’t log out or use anything.I tried to wait for few times to see if it turn back to normal but after 20 minutes wait nothing and i have to alt+f4. When i relog it seems fine for a while and then it happens again. It always happens in open zones. It wont happen in instances or battle grounds. I tried clean install no addons. I tried things in “World of Warcraft Latency Problems” many more things nothing works. I even tried vpn and it worked but there is too much “normal lag” with vpn. It’s not much playable like that.
If the problem disappears while using a VPN that usually does mean that your “regular” connection route has some trouble, or that the router has incorrect settings regarding data type prioritization/QoS (which VPNs as a byproduct of their function often circumvent)
The symptoms you described would also be a possible effect of data packets being lost on said regular route, so having a look at that (via a tool like WinMTR) would be a good first step… but if that is not it then having a chat with your ISP company will likely be required.
Thanks for the quick reply.
Here is WinMTR
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|---|
| 192.168.1.1 | 0 | 462 | 462 | 0 | 0 | 1 | 0 |
| host-213-14-0-225.reverse.superonline. | 0 | 462 | 462 | 2 | 6 | 12 | 3 |
| 10.36.250.85 | 0 | 462 | 462 | 1 | 2 | 5 | 3 |
| 10.34.255.157 | 0 | 462 | 462 | 1 | 1 | 5 | 2 |
| 10.40.197.201 | 0 | 462 | 462 | 1 | 1 | 5 | 2 |
| 10.40.197.210 | 0 | 462 | 462 | 2 | 3 | 36 | 3 |
| 10.40.141.57 | 0 | 462 | 462 | 8 | 9 | 27 | 10 |
| 10.40.141.54 | 0 | 462 | 462 | 8 | 9 | 40 | 12 |
| 10.36.6.142 | 0 | 462 | 462 | 8 | 9 | 32 | 10 |
| if-ae-12-80.tcore2.fnm-frankfurt.as6453. | 0 | 462 | 462 | 53 | 53 | 58 | 54 |
| if-ae-30-2.tcore1.pvu-paris.as6453. | 0 | 462 | 462 | 50 | 52 | 88 | 55 |
| No response from host | 100 | 93 | 0 | 0 | 0 | 0 | 0 |
| ae-2-3211.edge7.Paris1.Level3. | 0 | 462 | 462 | 53 | 57 | 85 | 54 |
| BLIZZARD-EN.edge7.Paris1.Level3. | 0 | 462 | 462 | 53 | 57 | 130 | 54 |
| ae1-br02-eqpa4.as57976. | 1 | 458 | 457 | 53 | 62 | 1925 | 1925 |
| et-0-0-3-br02-eqam1.as57976. | 0 | 462 | 462 | 55 | 59 | 157 | 62 |
| et-0-0-67-pe02-eqam1.as57976. | 0 | 462 | 462 | 55 | 59 | 130 | 58 |
| 137.221.66.47 | 0 | 462 | 462 | 55 | 56 | 62 | 56 |
| 185.60.112.157 | 0 | 462 | 462 | 56 | 56 | 62 | 57 |
Here is Pathping
and here is pathping
Tracing route to 185.60.112.157 over a maximum of 30 hops
0 asd [192.168.1.4]
1 192.168.1.1
2 host-213-14-0-225.reverse.superonline. [213.14.0.225]
3 10.36.250.85
4 10.34.255.157
5 10.40.197.201
6 10.40.197.210
7 10.40.141.57
8 10.40.141.54
9 10.36.6.142
10 if-ae-12-80.tcore2.fnm-frankfurt.as6453. [195.219.156.134]
11 if-ae-30-2.tcore1.pvu-paris.as6453.t [80.231.153.89]
12 80.231.153.66
13 ae-2-3211.edge7.Paris1.Level3. [4.69.133.238]
14 BLIZZARD-EN.edge7.Paris1.Level3.t [213.19.199.110]
15 ae1-br02-eqpa4.as57976. [137.221.77.35]
16 et-0-0-3-br02-eqam1.as57976.t [137.221.65.93]
17 et-0-0-67-pe02-eqam1.as57976. [137.221.78.73]
18 137.221.66.47
19 185.60.112.157
Computing statistics for 475 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 asd [192.168.1.4]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 2ms 0/ 100 = 0% 0/ 100 = 0% host-213-14-0-225.reverse.superonline. [213.14.0.225]
0/ 100 = 0% |
3 — 100/ 100 =100% 100/ 100 =100% 10.36.250.85
0/ 100 = 0% |
4 — 100/ 100 =100% 100/ 100 =100% 10.34.255.157
0/ 100 = 0% |
5 — 100/ 100 =100% 100/ 100 =100% 10.40.197.201
0/ 100 = 0% |
6 — 100/ 100 =100% 100/ 100 =100% 10.40.197.210
0/ 100 = 0% |
7 — 100/ 100 =100% 100/ 100 =100% 10.40.141.57
0/ 100 = 0% |
8 — 100/ 100 =100% 100/ 100 =100% 10.40.141.54
0/ 100 = 0% |
9 — 100/ 100 =100% 100/ 100 =100% 10.36.6.142
0/ 100 = 0% |
10 47ms 1/ 100 = 1% 1/ 100 = 1% if-ae-12-80.tcore2.fnm-frankfurt.as6453. [195.219.156.134]
0/ 100 = 0% |
11 52ms 0/ 100 = 0% 0/ 100 = 0% if-ae-30-2.tcore1.pvu-paris.as6453. [80.231.153.89]
0/ 100 = 0% |
12 53ms 0/ 100 = 0% 0/ 100 = 0% 80.231.153.66
0/ 100 = 0% |
13 57ms 0/ 100 = 0% 0/ 100 = 0% ae-2-3211.edge7.Paris1.Level3.[4.69.133.238]
0/ 100 = 0% |
14 60ms 0/ 100 = 0% 0/ 100 = 0% BLIZZARD-EN.edge7.Paris1.Level3. [213.19.199.110]
0/ 100 = 0% |
15 61ms 0/ 100 = 0% 0/ 100 = 0% ae1-br02-eqpa4.as57976. [137.221.77.35]
0/ 100 = 0% |
16 62ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-3-br02-eqam1.as57976.[137.221.65.93]
0/ 100 = 0% |
17 69ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-67-pe02-eqam1.as57976. [137.221.78.73]
0/ 100 = 0% |
18 — 100/ 100 =100% 100/ 100 =100% 137.221.66.47
0/ 100 = 0% |
19 57ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157
Trace complete.
The WinMTR- and pathping-logs actually look pretty decent, nothing in them would indicate any undue delays or losses (ae1-br02-eqpa4.as57976.net is a firewall that deliberately discards/delays packets used in network tests, so the results on that line can be ignored).
That implies the problem may indeed be in the way the router handles data traffic for the game, so assuming the device was provided by your ISP you’ll want to have them check its settings. In some cases you may also be able to just factory reset the device via an option in its menu, but I’d probably hold off on doing that as a last resort as it may need quite some effort to get the device set up again afterwards. 
Alright check it with ISP. Thanks Veadsarias.
Still its a strange lag.