5 years ago
Delay in game
Hello. I faced such a problem when playing Apex, after connecting to the match I periodically get into the game where I have a ping(delay) of 500+, it does not fall, does not decompose, but when i l...
You can let show them the results of your UO Trace. That should give them some good information to start investigating.
I show them the results of my UO Trace. that what they message me
"1. The loss starts inside the zayo backbone and 123ms per server in the States is a good value.
2. Here is a trace through different upstreams
Host Loss% Snt Last Avg Best Wrst StDev
1. *** 0.0% 642 0.3 0.2 0.2 2.0 0.1
2. 10.255.254.1 0.0% 642 0.5 2.3 0.3 63.9 8.5
3. 80.93.116.37.in-addr.arpa 0.0% 642 0.6 1.1 0.6 16.1 1.3
4. fft1-od0.ett.ua 0.0% 642 28.2 30.3 28.1 94.3 9.4
5. er1.ams1.nl.above.net 0.0% 642 46.3 40.7 37.8 86.4 5.0
6. ae11.cs3.ams10.nl.zip.zayo.com 89.1% 642 115.9 116.2 115.0 127.3 2.0
7. ae10.cs1.lhr15.uk.eth.zayo.com 79.9% 642 496.6 470.9 318.6 604.0 51.5
8. ae0.cs3.lhr11.uk.eth.zayo.com 95.0% 642 116.2 115.9 115.0 120.0 1.0
9. ae5.cs3.lga5.us.eth.zayo.com 19.0% 642 115.2 115.4 114.7 124.2 1.3
10. ae23.cs3.iad93.us.eth.zayo.com 92.5% 642 488.9 476.5 380.2 586.5 51.8
11. ae22.er2.iad10.us.zip.zayo.com 0.0% 641 114.8 114.9 114.5 150.6 2.5
12. 64.125.199.190.t00673-02.abov 0.0% 641 114.8 114.8 114.6 133.7 0.8
13. 159.153.92.98 0.2% 641 115.7 115.1 114.9 124.6 0.4
14. 159.153.92.94 0.0% 641 115.4 115.2 114.9 127.2 0.9
15. bfbc2-ps3.gos.ea.com 0.0% 641 513.9 471.6 236.5 647.1 53.0
Host Loss% Snt Last Avg Best Wrst StDev
1. *** 0.0% 12 0.3 0.3 0.2 0.3 0.0
2. 10.255.254.1 0.0% 12 0.4 0.5 0.4 0.7 0.1
3. 10.12.12.1 0.0% 12 0.8 0.9 0.7 1.2 0.1
4. ae1-7.rt.tc2.lon.uk.retn.n 0.0% 12 48.0 49.1 46.3 62.6 5.8
5. gw-zayo.retn.net 0.0% 12 333.4 461.2 333.4 553.2 66.2
6. (waiting for reply)
7. ae5.cs3.lga5.us.eth.zayo.com 90.0% 11 118.9 118.9 118.9 118.9 0.0
8. ae23.cs3.iad93.us.eth.zayo.com 70.0% 11 516.3 559.1 516.3 606.6 45.3
9. ae22.er2.iad10.us.zip.zayo.com 0.0% 11 118.4 120.0 118.3 136.3 5.4
10. 64.125.199.190.t00673-02.above.net 0.0% 11 118.5 118.4 118.3 118.5 0.0
11. 159.153.92.98 0.0% 11 118.9 118.9 118.7 119.2 0.1
12. 159.153.92.94 0.0% 11 118.9 118.8 118.6 119.0 0.1
13. da2.gos.ea.com 0.0% 11 506.3 535.9 443.7 611.3 61.0
as you can see the routes run normally until the penultimate hop.
this is the route through the American upstream:
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.8.2 0.0% 12 0.3 0.3 0.2 0.3 0.0
2. 10.255.254.1 0.0% 12 0.4 0.5 0.4 0.7 0.1
3. 10.12.12.1 0.0% 12 0.8 0.9 0.7 1.2 0.1
4. ae1-7.rt.tc2.lon.uk.retn.net 0.0% 12 48.0 49.1 46.3 62.6 5.8
5. gw-zayo.retn.net 0.0% 12 333.4 461.2 333.4 553.2 66.2
6. (waiting for reply)
7. ae5.cs3.lga5.us.eth.zayo.com 90.0% 11 118.9 118.9 118.9 118.9 0.0
8. ae23.cs3.iad93.us.eth.zayo.com 70.0% 11 516.3 559.1 516.3 606.6 45.3
9. ae22.er2.iad10.us.zip.zayo.com 0.0% 11 118.4 120.0 118.3 136.3 5.4
10. 64.125.199.190.t00673-02.above.net 0.0% 11 118.5 118.4 118.3 118.5 0.0
11. 159.153.92.98 0.0% 11 118.9 118.9 118.7 119.2 0.1
12. 159.153.92.94 0.0% 11 118.9 118.8 118.6 119.0 0.1
13. da2.gos.ea.com 0.0% 11 506.3 535.9 443.7 611.3 61.0
here is about the same picture, but we pass a completely different route and still see that a critical increase in the "ping" value occurs on the last hop (as well as on other routes), i.e. on the actual server we are testing.
Give IP servers in Europe - let's check the passability on them.