You call it #Heroku outage, we call it "Yet another Thursday when we are not able to deploy for 4 hours to production because Heroku is having issues with their API"
https://status.heroku.com/incidents/2558
Update: The issue was resolved, it only took 196 minutes to fix.
> The Heroku API, Dashboard, and CLI are working as expected.
> The impact start time is 15:08 UTC and the end time is 18:24 UTC.
You call it #Heroku #outage, we call it "Yet another Friday when we are not able to deploy for 3 hours to production because Heroku is having issues with their API"
https://status.heroku.com/incidents/2561
Days since the last Heroku incident: 15 days.
@esparta it’s a feature, no?
@jremsikjr @esparta If the Heroku API can take an early mark, we can _all_ take an early mark.
@Ryanbigg @jremsikjr it's all jokes and fun until the day when a RCE would need to be fixed while also #Heroku is not able do to releases or what not...
Or depending on your app, a previous deployment broke production and now you can't fix it because Heroku's API is down (again).
@jremsikjr yes, it's not a bug, it's a feature.
So we all can go home - I'm already at home - and/or stop working until Heroku is back.
@esparta I took the right afternoon off.