@MrMazda:

This is a known intermittent issue, and we are working to resolve it. It seems to be the result of a server upgrade that we recently conducted.

Any progress on this?