@slajax @aarongraves @heroku @SFAnswers This was an issue with AWS, one of their 'reachability checks' failed an issue with infrastructure.