Thanks for pointing. It's fixed now, it was some deployment bug.