Hey, sorry to hear that. My hope is that this has something to do with some testing we were running over the weekend for our update today. Hopeflly the issue is fixed now, but if not, please do let us know
