Hey, sorry for the inconvenience! We’ve since reverted a broken deploy and it should work fine again.