Hi,
Luckily it was only the same issue as before. The fix for the update check was implemented in the previous release, and the one installed on the site was older than that.
I simply deactivated and activated the code again on the plugin back-end (Updates panel) to refresh the local transient cache, and that worked. This issue should not reappear after this update (4.22.5).