Skelgarer,
I don’t want to be argumentative here, but compiling the WinMTRs run to 137.221.105.2 shows better results, not worse (unless we’re considering packet loss of 0.0011%-0.0018% as an automatic fail, which surely we’re not doing?): https://pastebin.com/UbkuJ0c3
The forums are not a commonly used medium. I’m not sure what n is expected before a systemic issue is considered, but would like to approach from a different angle. I’ve compiled all of the issue reports that indicate identical symptoms and do not have a character associated with Moon Guard in any way:
1-2: Disconnected 2 to 5 times an hour
3: Constant DCs
4: Disconnecting every 15-20 minutes (post 1)
This gives 28 reports from Moon Guard and 5 from off-server, for 85% of the issue reports coming from this server.
Update: 40 reports from MG and 4 from off-server (one reported resolved by a battle.net patch), for 91% of issue reports coming from this server.
In the most charitable read, an RP-related addon could be considered to cause this issue. However, of the 5 off-server reporting the issue, they are: US-Kel’thuzad, US-Terenas, US-Frostmourne, US-Stormrage, and an unknown WoW Classic server, none of which are RP servers. Additionally, the disconnects have been observed by both myself and others to occur at the character select screen (4 reports), before addons are loaded.
I have run multiple pcaps (available upon request but will not be uploaded to this forum for obvious reasons) and can reliably identify TCP retransmits occurring from local to 137.221.97.120 immediately before each disconnect. However, connectionless protocols such as ICMP (local → 137.221.97.120) or UDP (137.221.97.120 → local) continue working at this time. This explains why this issue is not reliably reproduced in WinMTR, and suggests that a TCP socket is shutting. This IP is not implicated in connecting to any other server that I have tested.
Marcrel: Your thread was excluded from scope as your issue symptoms are completely different.
Edit for clarity: 137.221.97.120 is denying ICMP. However, the route to 137.221.97.120 remains strong when this issue occurs. As stated before, UDP traffic to and from 137.221.97.120 continues functioning when this issue occurs.
Second edit: Corrected a miscount in issue reports.