After speaking with the support team, the issue has been resolved. It looks like it was some issue on the backend side, didn't get any specific information about it.