Hi @Brandon and @Terry_Deeb — There was an issue that has since been resolved by our team. You can read more here:
Apologies for the trouble!