Chats not updating -- related to 406 NETWORK_BAD_REQUEST, Long-poll failed?

[romanrm]

Since a few days ago I'm getting the issue of chats not showing new messages, until F5 is pressed to reload the entire Telegram Web page. At the moment of reload, there are a few suspicious error messages in the browser console.

This is the same no matter whether on my self-hosted install, or on the instance currently at web.telegram.org.

Messages are as follows, adding a screenshot for readability: https://romanrm.hk/2021-04-03T154408Z-lpfail.png
angular.js:17945 Long-poll failed undefined
:8000/app/js/lib/mtproto.js:1202 Encrypted request failed Object {code: 406, type: "NETWORK_BAD_REQUEST", url: "https://venus.web.telegram.org/apiw1", originalError: Object}
(anonymous) @ :8000/app/js/lib/mtproto.js:1202
processQueue @ :8000/app/vendor/angular/angular.js:17945
(anonymous) @ :8000/app/vendor/angular/angular.js:17993
$digest @ :8000/app/vendor/angular/angular.js:19112
$apply @ :8000/app/vendor/angular/angular.js:19500
done @ :8000/app/vendor/angular/angular.js:13343
completeRequest @ :8000/app/vendor/angular/angular.js:13600
requestAborted @ :8000/app/vendor/angular/angular.js:13520
:8000/app/js/lib/mtproto.js:900 Long-poll failed undefined
:8000/app/js/lib/mtproto.js:1202 Encrypted request failed Object {code: 406, type: "NETWORK_BAD_REQUEST", url: "https://pluto-1.web.telegram.org/apiw1", originalError: Object}
(anonymous) @ :8000/app/js/lib/mtproto.js:1202
processQueue @ :8000/app/vendor/angular/angular.js:17945
(anonymous) @ :8000/app/vendor/angular/angular.js:17993
$digest @ :8000/app/vendor/angular/angular.js:19112
$apply @ :8000/app/vendor/angular/angular.js:19500
done @ :8000/app/vendor/angular/angular.js:13343
completeRequest @ :8000/app/vendor/angular/angular.js:13600
requestAborted @ :8000/app/vendor/angular/angular.js:13520
:8000/app/js/lib/mtproto.js:900 Long-poll failed undefined

[anton-samal]

the same thing with me. still sometimes I see chats in which I'mnot a member. I thought it was a joke by April 1st. but apparently not