A quick follow-up that we identified the issue and deployed a fix a few hours ago. After some testing, it seems the problem is resolved but please let me know if you are still experiencing this issue.
Thank you to those who wrote to us letting us know and to everyone for your patience,
Kyle