@dlakelan mentioned that he's been graphing MTR output from the OP, so it seems he does have it.
I need to jump in to Linux to run an MTR TCP trace.
WinMTR was a demo of what data it can provide.
Yes and no, ATM I am interested in figuring out the path to and from the game server, and for that purpose even a run-of-the-mill 3 sample-per-hop traceroute can help. Other than that I endorse both your proposals of longer and more varied mtr like:
5 minutes ICMP:
mtr -ezbw -c 300 213.179.218.36
5 minutes UDP:
mtr -ezbwu -c 300 213.179.218.36
5 minutes TCP
mtr -ezbwT -c 300 213.179.218.36
The OP just needs to run it.
You can teach someone to fish, or give them a fish.
His call.
I'm out.
Well, the "trick" with a VPN is to find one that is well connected with one's ISP, the VPN internal path is a secondary issue. So which VPN service did you use, and can you please post an mtr to/from that VPN service?
the current peering of my ISP is Zayo, and to extend all my routes by 1/3 compared to the old peering which was Cyberlink.. a traceroute on a specific IP reveals this.. in summary since this new peering contract made in October 2019 to increase my latency
For the speedtests Iasked for? Please with sqm disabled, as sqm does not seem to be the root cause so I want to see what your link delivers, and please humor me and also runn the dslreports speedtests in spite of me being its only "fan" (it comes with interesting additional data that might be helpful), but please follow the configuration instructions over here.
I believe there are 3 more people who are "fans", so you have a base. 
In the case of 213.179.218.36 it responds to neither ICMP, UDP, or TCP from my link...
From man mtr:
-u, --udp
Use UDP datagrams instead of ICMP ECHO.
-T, --tcp
Use TCP SYN packets instead of ICMP ECHO. PACKETSIZE is ignored, since SYN packets can not contain data.
Please read this for a primer how to interpret traceroute/mtr results. Intermittently high RTTs often have little diagnostic value by themselves, as infrastructure nodes are known to both rate-limit ICMP response generation as well de-priorize them, if however all hops periodically report higher RTTs and then fall back to something lower that might be actionable.
Saw the command line structure on another site and was going to use it on my Linux distro.
mtr -P 80 -T -w "ip address"
That's why I prefaced with "I'm not an expert".
Which is helpful, but for us here in the thread right now not so much.
No problem, you know what you are doing so WinMTR is fine, but to help the OP he needs to use the same as I do and I have no windows host available.
You and me, we seem to have a massive communication problem (probable me not being explicit enough), sorry, Yes, that was aimed at the OP, not you, traces from your access link will not resolve his issues (nor will traces from mine).
I knew that.
My comment was meant to indicate that OP seems to be hesitant to do much of anything regarding diagnostics and troubleshooting.
Just needs to run the commands you gave him so it can move forward.
Ah good point:
-P PORT, --port PORT
The target port number for TCP/SCTP/UDP traces.
but even adding -P 80 the final hop still does not respond for me:
user@1234-12345:~/SCRATCH$ mtr -ezbTw -c 10 -P 80 213.179.218.36
Start: 2022-01-17T11:53:37+0100
HOST: 1234-12345 Loss% Snt Last Avg Best Wrst StDev
1. AS??? _gateway (192.168.42.1) 0.0% 10 0.4 0.4 0.4 0.5 0.0
2. AS6805 loopback1.0004.acln.01.ham.de.net.telefonica.de (62.52.200.150) 0.0% 10 32.3 32.4 8.8 49.7 15.6
3. AS6805 bundle-ether30.0005.dbrx.01.ham.de.net.telefonica.de (62.53.12.24) 0.0% 10 9.5 9.3 9.0 9.7 0.2
AS6805 bundle-ether30.0006.dbrx.01.ham.de.net.telefonica.de (62.53.12.26)
4. AS6805 ae4-0.0002.corx.01.ham.de.net.telefonica.de (62.53.14.16) 0.0% 10 17.3 17.1 15.6 19.8 1.1
[MPLS: Lbl 16597 TC 0 S u TTL 1]
AS6805 ae5-0.0002.corx.01.ham.de.net.telefonica.de (62.53.14.26)
[MPLS: Lbl 16597 TC 0 S u TTL 1]
AS6805 ae4-0.0001.corx.06.ham.de.net.telefonica.de (62.53.14.230)
[MPLS: Lbl 16601 TC 0 S u TTL 1]
AS6805 ae5-0.0001.corx.06.ham.de.net.telefonica.de (62.53.14.232)
[MPLS: Lbl 16597 TC 0 S u TTL 1]
5. AS6805 ae7-0.0002.corx.02.dus.de.net.telefonica.de (62.53.0.17) 0.0% 10 16.1 17.8 16.0 20.2 1.3
[MPLS: Lbl 16597 TC 0 S u TTL 1]
AS6805 ae6-0.0001.corx.01.off.de.net.telefonica.de (62.53.0.35)
[MPLS: Lbl 16601 TC 0 S u TTL 1]
AS6805 ae7-0.0002.corx.01.dus.de.net.telefonica.de (62.53.0.1)
[MPLS: Lbl 16597 TC 0 S u TTL 1]
AS6805 ae6-0.0002.corx.02.fra.de.net.telefonica.de (62.53.0.49)
[MPLS: Lbl 16601 TC 0 S u TTL 1]
6. AS6805 ae1-0.0002.dbrx.01.dus.de.net.telefonica.de (62.53.16.36) 0.0% 10 16.7 16.9 15.9 18.3 0.8
[MPLS: Lbl 16597 TC 0 S u TTL 1]
AS6805 bundle-ether2.0003.dbrx.02.fra.de.net.telefonica.de (62.53.28.149)
[MPLS: Lbl 16601 TC 0 S u TTL 1]
AS6805 bundle-ether1.0003.dbrx.02.fra.de.net.telefonica.de (62.53.14.163)
[MPLS: Lbl 16601 TC 0 S u TTL 1]
AS6805 ae0-0.0001.dbrx.01.dus.de.net.telefonica.de (62.53.16.30)
[MPLS: Lbl 16597 TC 0 S u TTL 1]
7. AS6805 bundle-ether1.0003.prrx.01.dus.de.net.telefonica.de (62.53.8.193) 0.0% 10 18.7 18.3 15.9 19.5 1.2
AS6805 bundle-ether2.0003.prrx.01.dus.de.net.telefonica.de (62.53.8.211)
AS6805 bundle-ether1.0004.prrx.02.fra.de.net.telefonica.de (62.53.8.187)
8. AS12956 ae6-0-grtdusix1.net.telefonicaglobalsolutions.com (81.173.106.10) 0.0% 10 18.2 17.6 16.2 18.4 0.8
AS12956 176.52.252.28
9. AS9158 94.144.107.49 0.0% 10 19.9 19.4 16.5 25.4 3.0
AS12956 176.52.248.83
10. AS9158 94.144.107.49 0.0% 10 16.0 19.2 16.0 25.5 2.7
AS2914 ae-2.r21.frnkge13.de.bb.gin.ntt.net (129.250.6.41)
11. AS2914 ae-2.r21.frnkge13.de.bb.gin.ntt.net (129.250.6.41) 0.0% 10 40.8 330.9 18.4 3057. 958.1
AS2914 ae-12.r21.parsfr04.fr.bb.gin.ntt.net (129.250.5.27)
12. AS2914 ae-12.r21.parsfr04.fr.bb.gin.ntt.net (129.250.5.27) 0.0% 10 48.2 45.5 30.4 57.3 8.3
AS2914 ae-13.r02.mdrdsp03.es.bb.gin.ntt.net (129.250.2.14)
13. AS2914 ae-13.r02.mdrdsp03.es.bb.gin.ntt.net (129.250.2.14) 0.0% 10 55.9 48.9 47.4 55.9 2.6
AS2914 ae-0.a01.mdrdsp03.es.bb.gin.ntt.net (129.250.2.209)
14. AS2914 ae-0.a01.mdrdsp03.es.bb.gin.ntt.net (129.250.2.209) 50.0% 10 49.6 50.4 49.6 51.4 0.7
15. AS??? ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
Please post such a traceroute, I am sure you know this, but for remote help and diagnosis having access to the raw traceroute/mtr data and your interpretation is much better than only your memory 
Last seen 20 minutes ago...so hopefully he's running the traces.
please excuse me for the delay in my answers, English is not my language.. it requires a translation, and I am currently at my place of work which does not allow me to start all my tests that I look forward to forwarding to you for analysis!
Great, how about we pause until you are back at home and had time to measure and post what you want to share?
2 Likes
here is the test to be carried out on January 5, this IP address is recommended by the game developer EA, for diagnostic purposes which allows in the event of damage to contact ISP note for study .. unfortunately my ISP brushes it off wondering that they are not responsible for the traceroute.. which of course is a lie.. Zayo is a peering and partner of my ISP, I have this source information on!
easo.ea.com is not 213.179.218.36, so what is up with these two addresses?
easo.ea.com resolves for me in the U.S. with an RTT ~100ms, if you are playing on those server, I am not amazed if things do not work as expected.
BTW I see a similar jump to ~100ms with the first zayo hop, which leads me to believe that zayo might use mpls and we hence only get the final RTT reported for all intermediate hops. My MTR results confirm the MPLS hypothesis just fine:
user@1234-12345:~/SCRATCH$ mtr -ezbw -c 10 easo.ea.com
Start: 2022-01-17T12:26:52+0100
HOST: 1234-12345 Loss% Snt Last Avg Best Wrst StDev
1. AS??? _gateway (192.168.42.1) 0.0% 10 0.3 0.3 0.3 0.3 0.0
2. AS6805 loopback1.0004.acln.01.ham.de.net.telefonica.de (62.52.200.150) 0.0% 10 9.1 8.9 8.6 9.2 0.2
3. AS6805 bundle-ether30.0005.dbrx.01.ham.de.net.telefonica.de (62.53.12.24) 0.0% 10 9.4 9.2 8.9 9.4 0.2
4. AS6805 ae4-0.0002.corx.01.ham.de.net.telefonica.de (62.53.14.16) 0.0% 10 16.1 15.9 15.7 16.6 0.3
[MPLS: Lbl 16603 TC 0 S u TTL 1]
5. AS6805 ae6-0.0001.corx.01.off.de.net.telefonica.de (62.53.0.35) 0.0% 10 26.2 34.6 18.0 49.3 9.1
[MPLS: Lbl 16603 TC 0 S u TTL 1]
6. AS6805 bundle-ether2.0004.dbrx.02.fra.de.net.telefonica.de (62.53.28.151) 0.0% 10 16.3 16.4 16.0 17.2 0.3
[MPLS: Lbl 16603 TC 0 S u TTL 1]
7. AS6805 ae7-0.0001.prrx.09.fra.de.net.telefonica.de (62.53.5.75) 0.0% 10 15.9 15.9 15.6 16.2 0.2
8. AS??? as6461.frankfurt.megaport.com (62.69.146.139) 0.0% 10 16.4 19.5 15.8 27.9 3.6
9. AS6461 ae1.cs1.fra9.de.eth.zayo.com (64.125.29.64) 0.0% 10 98.3 98.4 98.2 98.7 0.2
[MPLS: Lbl 848516 TC 0 S u TTL 1]
[MPLS: Lbl 158 TC 0 S u TTL 1]
10. AS6461 ae0.cs1.fra6.de.eth.zayo.com (64.125.29.54) 0.0% 10 98.3 98.4 98.1 99.2 0.3
[MPLS: Lbl 158 TC 0 S u TTL 1]
11. AS6461 ae2.cs1.ams17.nl.eth.zayo.com (64.125.29.59) 50.0% 10 98.3 98.5 98.3 98.7 0.2
[MPLS: Lbl 247946 TC 0 S u TTL 1]
[MPLS: Lbl 187 TC 0 S u TTL 1]
12. AS6461 ae4.cs3.ams10.nl.eth.zayo.com (64.125.28.37) 90.0% 10 98.5 98.5 98.5 98.5 0.0
[MPLS: Lbl 402338 TC 0 S u TTL 1]
[MPLS: Lbl 187 TC 0 S u TTL 2]
13. AS??? ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14. AS6461 ae0.cs3.lhr11.uk.eth.zayo.com (64.125.29.118) 90.0% 10 98.6 98.6 98.6 98.6 0.0
[MPLS: Lbl 765088 TC 0 S u TTL 1]
[MPLS: Lbl 187 TC 0 S u TTL 4]
15. AS6461 ae5.cs1.lga5.us.eth.zayo.com (64.125.29.126) 10.0% 10 98.5 99.1 98.0 104.5 2.1
[MPLS: Lbl 731432 TC 0 S u TTL 1]
[MPLS: Lbl 187 TC 0 S u TTL 5]
16. AS6461 ae23.cs3.iad93.us.eth.zayo.com (64.125.28.189) 90.0% 10 99.4 99.4 99.4 99.4 0.0
[MPLS: Lbl 187 TC 0 S u TTL 1]
17. AS6461 ae22.er2.iad10.us.zip.zayo.com (64.125.29.121) 0.0% 10 98.2 98.4 98.2 98.7 0.1
18. AS6461 64.125.199.190.t00673-02.above.net (64.125.199.190) 0.0% 10 99.6 98.6 98.2 99.6 0.4
19. AS19541 159.153.92.98 0.0% 10 98.8 98.7 98.3 99.0 0.2
20. AS19541 159.153.92.94 0.0% 10 98.7 98.8 98.3 99.3 0.3
21. AS19541 bfbc2-ps3.gos.ea.com (159.153.64.173) 0.0% 10 98.3 98.3 98.0 98.5 0.1
@segal_72 we need to identify at least 1 gaming server you play on that is in Europe and experiences the problem. Then show a MTR output for that server.
mtr -ezbw -c 10 <ipaddr here>
We will wait for you to be back home.