Sorry to hear this. This may be being caused by a temporary network/connection issue, or disruption with the backend, I’ve seen other similar reports this morning, so this may be why. Though everything appears stable for the backend currently. Can you check again and let me know if the error persists?
If so, are you able to try temporarily switching to a mobile data connection to check if the same error occurs? This can help in isolating the issue and for us to determine if the problem is network/ISP-related.