Looks like Heroku posted a status page incident, largely retroactively: https://status.heroku.com/incidents/2409