Heroku was Down
Incident: https://status.heroku.com/incidents/2402
Update: our apps appear back up after 23 minutes total downtime. Others are reporting applications still down.
Update: it appears most or all services have been restored.
Update: our apps appear back up after 23 minutes total downtime. Others are reporting applications still down.
Update: it appears most or all services have been restored.
148 comments
[ 299 ms ] story [ 3091 ms ] threadI've seen a few get to the front page.
But when we're right we're right.
I mean, yesterday was a good day. But today's the best you've got if you didn't do it then.
Heroku and AWS are organizations no?
> While there are not currently any specific credible threats to the U.S. homeland, we are mindful of the potential for the Russian government to consider escalating its destabilizing actions in ways that may impact others outside of Ukraine.
like what
I'm just posting what would lead somebody to that conclusion. Nobody is definitively saying anything right now.
As an aside, I spoke with our AE in early January on where they are going in dealing with AWS unreliability. One would think they would have a good answer. They don't.
I recall at least one of them I could not deploy new versions of my app though, which is pretty bad. I don't believe I had any downtime at all due to heroku platform outages in 2021. i believe you if you say you did though!
This particular outage definitely seems to be of a rare level of severity.
Didn't bring my deployed app down though! No user-facing outage for me.
This time my app was down for about 35 minutes.
It's much better than it was 5+ years ago. Back then they had almost weekly downtime.
Of course, they won't. If they host is on someone else's then that might look bad (tacitly saying that a competitor is reliable and might be up when they are down) and if they hive off an extra copy of some of their infrastructure there will still be single points of failure either accidentally, by human error (someone somehow messing up both segments at once), or by design (possibly through management trying to save pennies when they noticed this extra bit of infrastructure on the balance sheet).
I worked there and I vaguely remember something like this but it's been a long time.
If I had to guess this is probably a DNS issue (it's always DNS).
Link here to latest snapshot:
https://postimg.cc/McZHpCWg
No issues noted there.
Cache freshness checks involve a lot of headers, which take up way more bandwidth than one unicode character.
/s
But, this really happened in 2017.
Metrist monitors via bots
[0] https://downdetector.com/status/windows-azure/ [1] https://downdetector.com/status/google-cloud/