| Error report |
| Describe problem and what you saw | I have been experiencing horrendous ping on a daily basis for the past few weeks.
I did not originally realize that the game was unplayable due to bad ping (I thought it was my laptop acting up)
It gets hard to play well between 150-200 and I have been having a ping in the region of 350-550 on a daily basis - especially during weekends or during sector conquest.
Basically at this point you just go for a walk and thank Gaijin for helping you spend less time on your laptop!
I am based in London UK if that helps understand why I can’t play online - usually am logged on European servers. |
| What you expected to see | I expected to see a good ping and a playable game, especially when I can get online and when my corpo is online 
Obviously, I tested my connection and it is rock steady and super fast (fiberoptics). The issue does not come from my ISP - more likely from the game servers.
Here s the content of my log (copy of attached .zip)
— Date: 2021-11-03 (Wed Nov 2021) GMT Standard Time UTC+00:00
19:00:18.145 | //////////////////////////////////////////////////////////
19:00:18.146 | //
19:00:18.146 | // Connection Tester 1.9.3.147311 (Oct 28 2021 16:07:01)
19:00:18.146 | //
19:00:18.147 | //////////////////////////////////////////////////////////
19:00:18.147 |
19:00:18.154 CONSOLE| executing ‘connection_tester.cfg’
19:00:18.157 | There are total of 2 hosts to check
19:00:18.157 | ConnectionTester: new state ‘CTS_INITIALIZED’
19:00:18.158 | ConnectionTester: new state ‘CTS_RESOLVING’
19:00:18.162 | Resolving ‘google.com’ …
19:00:18.191 | ‘google.com’ is 172.217.169.46
19:00:18.191 | Resolving ‘node09st-ru.star-conflict.com’ …
19:00:18.192 | ‘node09st-ru.star-conflict.com’ is 95.213.156.195
19:00:18.192 | ConnectionTester: new state ‘CTS_PINGING’
19:00:19.025 | 76 bytes from 172.217.169.46 ( icmpseq=0, triptime=9ms, TTL=119 )
19:00:20.027 | 76 bytes from 172.217.169.46 ( icmpseq=1, triptime=9ms, TTL=119 )
19:00:21.029 | 76 bytes from 172.217.169.46 ( icmpseq=2, triptime=9ms, TTL=119 )
19:00:22.018 WARNING| 95.213.156.195 response (seq 0) timed out
19:00:22.031 | 76 bytes from 172.217.169.46 ( icmpseq=3, triptime=10ms, TTL=119 )
19:00:22.163 | Pinged for 4.0 seconds
19:00:22.163 | google.com: packets: 4/4 ( 0% loss), avg: 9ms, min: 9ms, max: 10ms
19:00:22.163 | node09st-ru.star-conflict.com: packets: 4/0 (100% loss), avg: 0ms, min: 0ms, max: 0ms
19:00:22.164 | ConnectionTester: new state ‘CTS_UDP_TESTING’
19:00:37.769 | UdpTester(95.213.156.195|35900): Failed to connect
19:00:37.771 | UDP tester work time: 20.0 seconds
19:00:37.771 | UdpTester(95.213.156.195|35900): MTU size: 576
19:00:37.771 | UdpTester(95.213.156.195|35900): Ping: avg: -1ms, min: -1ms
19:00:37.772 | UdpTester(95.213.156.195|35900): Packets received by server: 0/0
19:00:37.773 | UdpTester(95.213.156.195|35900): Sizes of packets received from server (0):
19:00:37.774 | ConnectionTester: new state ‘CTS_FINNISHED’
19:00:37.784 | ConnectionTester::Shutdown |
| Conditions in which error reproduce | random but seems to depend on how many users are online (busier during sector conquest and weekends) |
| Problem details | very bad ping.
the ship acts “drunk” like waddling, spinning on its axis, and you can barely orientate the direction in which it flies, definitely not shoot anything with precision. |
| Frequency of reproduction | frequent |
| Time of bug | Too many occurrences to list. Usually sector conquest 6pm 8pm winter GWT time or 7pm 9pm summer GMT time. or weekends) but it can really happen at any time of the day. |
[bad ping log.zip](< base_url >/applications/core/interface/file/attachment.php?id=21408&key=3cded97eca4a4392ce0d4466ab0589af)