massive lag/ping spikes (blinking character) on some area

so, i got massive lag when i enter some new area. For example: when i enter blood aqueduct i get massive lag/ping spikes, but if i create a new instance the lag is gone. It happens very often, i have to create new instance every time i got the lag. Please fix this thank you...

here's my pastebin for my WinMTR: https://pastebin.com/Df0amCfS
Last bumped on Nov 12, 2019, 10:19:45 AM
"
so, i got massive lag when i enter some new area. For example: when i enter blood aqueduct i get massive lag/ping spikes, but if i create a new instance the lag is gone. It happens very often, i have to create new instance every time i got the lag. Please fix this thank you...

here's my pastebin for my WinMTR: https://pastebin.com/Df0amCfS


GGG needs more information before they can "fix" anything.
This is what you need to do -->

1. When you have a good instance without lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

2. When you have a bad instance with lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

Please post the results here and clearly states witch IP is the good and witch IP is the bad.

Also please confirm that you are creating a new instance for the same area when you have the lag problem?
"
HanSoloDK wrote:
"
so, i got massive lag when i enter some new area. For example: when i enter blood aqueduct i get massive lag/ping spikes, but if i create a new instance the lag is gone. It happens very often, i have to create new instance every time i got the lag. Please fix this thank you...

here's my pastebin for my WinMTR: https://pastebin.com/Df0amCfS


GGG needs more information before they can "fix" anything.
This is what you need to do -->

1. When you have a good instance without lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

2. When you have a bad instance with lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

Please post the results here and clearly states witch IP is the good and witch IP is the bad.

Also please confirm that you are creating a new instance for the same area when you have the lag problem?



yes, i create instance for the same area. I'll update later.
cool, because I think there is a chance that your LAG instances are created on other gateway then the good instances.

What gateway are you using to login because I know some om them have dual ISP / hosting?
"
HanSoloDK wrote:
cool, because I think there is a chance that your LAG instances are created on other gateway then the good instances.

What gateway are you using to login because I know some om them have dual ISP / hosting?


i use singapore
"
"
HanSoloDK wrote:
cool, because I think there is a chance that your LAG instances are created on other gateway then the good instances.

What gateway are you using to login because I know some om them have dual ISP / hosting?


i use singapore


Singapore and Japan are both borked, for me anyway, and have been for a couple days solid. Sitting in town or hideout is fine, and most story zone instances seem to be fine (the few I've tried for testing anyway). Maps are absolutely unplayable due to constant and massive lag spikes.

These two gateways have had sporadic but ongoing issues since Legion launch. GGG is aware of it, and from what I understand they've made efforts to resolve the issues. But after nearly half a year, I'm quickly approaching the point of just giving up entirely and moving on to other games permanently.
I have a pretty good sense of humor. I'm not German.
"
HanSoloDK wrote:
"
so, i got massive lag when i enter some new area. For example: when i enter blood aqueduct i get massive lag/ping spikes, but if i create a new instance the lag is gone. It happens very often, i have to create new instance every time i got the lag. Please fix this thank you...

here's my pastebin for my WinMTR: https://pastebin.com/Df0amCfS


GGG needs more information before they can "fix" anything.
This is what you need to do -->

1. When you have a good instance without lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

2. When you have a bad instance with lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

Please post the results here and clearly states witch IP is the good and witch IP is the bad.

Also please confirm that you are creating a new instance for the same area when you have the lag problem?



hi, sorry for the late report. I've done making the report.

here's the result:

- Bad instance: IP= 216.12.203.90
winMTR = https://pastebin.com/YFvnxAwF



- Good instance: IP = 172.107.213.182
winMTR = https://pastebin.com/4n61xF14

"
"
HanSoloDK wrote:
"
so, i got massive lag when i enter some new area. For example: when i enter blood aqueduct i get massive lag/ping spikes, but if i create a new instance the lag is gone. It happens very often, i have to create new instance every time i got the lag. Please fix this thank you...

here's my pastebin for my WinMTR: https://pastebin.com/Df0amCfS


GGG needs more information before they can "fix" anything.
This is what you need to do -->

1. When you have a good instance without lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

2. When you have a bad instance with lag, please open the client.txt file and find the INSTANCE IP for that instance. Document it and run a WinMTR report against it.

Please post the results here and clearly states witch IP is the good and witch IP is the bad.

Also please confirm that you are creating a new instance for the same area when you have the lag problem?



hi, sorry for the late report. I've done making the report.

here's the result:

- Bad instance: IP= 216.12.203.90
winMTR = https://pastebin.com/YFvnxAwF



- Good instance: IP = 172.107.213.182
winMTR = https://pastebin.com/4n61xF14




here's another (the worst i've got today)

IP : 216.12.203.91
Pastebin/winMTR : https://pastebin.com/gidiWWN1
Screenshot : https://ibb.co/LNj8R0c
I know that in Singapore there are 2 differant ISP used by GGG.
It looks like the 216.12.203.X scope belongs to the 1 ISP and the other scope belongs to the other one.

Sadly as far as I know, there is no way to isolate the "bad" ISP and only use the good one...

But I think this is the answer to your problems.
"
HanSoloDK wrote:
I know that in Singapore there are 2 differant ISP used by GGG.
It looks like the 216.12.203.X scope belongs to the 1 ISP and the other scope belongs to the other one.

Sadly as far as I know, there is no way to isolate the "bad" ISP and only use the good one...

But I think this is the answer to your problems.



oh okay if it's so. It's just annoying that you have to recreate a new map (wasted 1 alche or probably more) whenever you got the lags. I hope GGG find a way to make it better anytime soon. Anyway, thanks for the answer, really informative. Have good day to you :D

Report Forum Post

Report Account:

Report Type

Additional Info