This happened to me earlier, `heroku restart` fixed it but of course I was assuming some change we deployed was monkeying things up.