@dawn_armfield thanks for letting us know. It's a temporary problem from Heroku (our hosting). Should be fixed now