Timers don't switch after a move

Hi, recently I got a couple of games where the timer didn't move to the other player after I moved. This results in losing the game as my tiime runs out.

Happens me alot nowadays too. They say its due to bad connection, but i get it on several different locations with good wifi. Never used to happened before. Last month is so boring.

I also have this problem in the last days, but my internet is the same as before.

related:

lichess.org/forum/general-chess-discussion/blog-XCpZphAAACwALGsT?page=2#18

wonder when this will get fixed.

They probably premoved, in which case it doesn't use any time. Its perfectly normal for that to happen in time scrambles or in bullet games, or any game really

I got this exact problem in Rapid Games some time ago, I had 6 minutes and my opponent had 9, connection was perfect. I made my move and my opponent time starts ticking to my surprise after his time elapses I had lost the game on time. No premoves involved, the server didn't seem to recieve my move though the interface accepted it and showed me that it was my opponents turn.

#4 @DerNickWarNochFrei Is right.

Also have exactly the same problem. It would be nice if any lichess dev could comment on that. It is really strange, since when I play on another PC or Laptop (same WiFi), it is flawless as it was before.

Things I have tried so far:
- use different browser
- disable browser plugins
- use VPN connection
- clear cookies and cache

Still nothing of this fixes the problem with this weird "lag".

Here is a video showing how this looks (Created with OBS studio):

www.youtube.com/watch?v=jFOPCslMh4A

Notice there are a few disconnections, the first three fix themself, the fourth kills me:

* After 6...d4 both clocks stop running but lichess restores time correctly after reconnecting.
* The same happens after 16... Rad8, this time paired with an refresh of the whole page.
* The same happens after 20... Kh7, this time his time keeps running, times then get correctly restored.
* Finally, after 21...f5 his clock runs and runs without him ever making a move and then, four seconds before his time runs out the page refreshes, shows that he actually moved and that my time has run out.

I hope the problem is now more clear. At least a comment by a dev would be appreciated.

I should add that this can be prevented by constantly pressing f5 (which i didnt do in this game) but of course this is not fun and it is impossible to play at full strength with these disconns. Playing 1 0 bullet is impossible.

Once again, this started suddenly around one month ago (i dont know the exact day) and i never had problems before and i changed nothing on my side.

Im not an expert in this, but i have the feeling it is the fault of the "improved websocket handling", see lichess.org/blog/XCpZphAAACwALGsT/lichess-end-of-year-update-2018

I saw the "Reconnecting" sign multiple times.