3 ms·
Update: apparently Heroku is aware of the issue (http://status.heroku.com/incident/121 http://status.heroku.com/incident/121) though they claim to have solved i
by guynamedloren 16y ago
Update: apparently Heroku is aware of the issue (http://status.heroku.com/incident/121 http://status.heroku.com/incident/121) though they claim to have solved it, and I'm still experiencing pretty poor performance.