@proxos666
I've already posted traces from UOTrace (tool suggested by EA support) in my previous replies in this thread. But if you prefer traces from pingplotter I'll add it today evening. Can you please tell me how much time pingplotter trace should run to get better trace results?
The UOtrace didn't show any issue unfortunately.
Pingplotter it is important its graphing when the issue appears in-game, its a real time status record but if you sneeze it may not pick up an issue if the issue occurs 1 second after the trace occurs, hence why need to be 100% graphing is occurring when the issue occurs.
if after a while we cannot get anything to appear in the graphs it gets more difficult, however you saying evening prime time is usually when net congestion could occur but again the pingplot should show if this is occurring
Pingplotter from today:
In game: ping between 96ms - 110000ms and disconnect
Upd: images for lag issue in game
Your best way forward is to show that ping plot to your ISP
That packet loss and errors that start to appear after 10.10.70.1 and continues to the server IP is likely what is causing you trouble
that 10.10.70.1 is a private network space and is upstream from your ISP the issue is likely across that link between whoever owns that hop6 and into the telia backbone
I can only comment on what i see in the pingplot, any packet loss will affect real time applications as seen, web browsing etc will remain unaffected.
This is a good link close to what you have displayed , that article mentions 2% when in reality any packet loss will have an affect if it carries through to the final destination.
Maybe try www.wtfast.com free trial just to test with, and see if there is any change to what occurs, it will also provide a comparison on the condition of the original route
