Finally! Seems like this is fixed now. Special thanks to anyone who sent a tweet to the CEO about this issue.
