Doesn't look like a cloudfront issue per se, though that is the error that comes up when trying to get to the Heroku dashbaord.

Still having issues, had a deploy (luckily just to staging) that seemed like it went through but old code still present in app. Can't restart dynos, cli commands sometimes work, sometimes don't.

Now a wider isssue, status.salesforce.com is also down

12 hours in and sites are still down, https://status.heroku.com/incidents/2822

Looks like we are getting production sites up and running again by restarting either via the CLI or the dashboard, worth a try if you are down.

To restart your heroku dynos from the CLI, do the following:

CLI command is:

`heroku restart --app <app-name>`

This does not work for private spaces, for those you need to do:

`heroku ps:stop <dyno-type> --app <app-name>`

Where <dyno-type> is probably web, worker etc.

Once down, then you do:

`heroku restart --app <app-name>`

This has gotten about 10 apps online already for us so far - we are monitoring our fleet of 100 heroku apps and moving through the rest.

This is a pain in the butt.