Heroku was Down • Hacker News Board

Re: Heroku was Down

#91

Post by gjs278 » Thu, Feb 24, 2022, 5:10 PM UTC

jermaustin1 wrote: post #79

reubano wrote: post #69

Earlier quoted context omitted.

I still don't get why they use images Instead of unicode: https://www.htmlsymbols.xyz/unicode/U%2b2705

if the image tag is drawn dynamically then it is actually probably less bandwidth than the unicode character since the image can be cached at multiple locations including the browser.

No post body was provided.

Re: Heroku was Down

#92

Post by dc-programmer » Thu, Feb 24, 2022, 5:11 PM UTC

driverdan wrote: post #72

iamricks wrote: post #13

So... what are the chances this is related to a cyber attack from Russia? Also our apps are down

Practically zero. Why would Russia care about Heroku?

Collateral damage (but probably DNS lol)

Re: Heroku was Down

#93

Post by jrochkind1 » Thu, Feb 24, 2022, 5:12 PM UTC

reubano wrote: post #27

AWS is down too, this is likely the cause since Heroku runs on it. https://downdetector.com/status/aws-amazon-web-services/

AWS status page is all green.... Just kidding! I know the information content of the AWS status page is literally zero, it's always green!

Re: Heroku was Down

#94

Post by jamil7 » Thu, Feb 24, 2022, 5:12 PM UTC

And we're back? I think.

Re: Heroku was Down

#95

Post by jrochkind1 » Thu, Feb 24, 2022, 5:13 PM UTC

My heroku app was back up again as of about 100 seconds before this comment timestamp.

My app was down about 35 minutes total, according to my monitoring.

Re: Heroku was Down

#96

Post by jmartens » Thu, Feb 24, 2022, 5:13 PM UTC

djbusby wrote: post #73

reubano wrote: post #63

Earlier quoted context omitted.

What makes Downdetector unreliable? It's showing a huge spike right now.

Their (metrist) claim is that DD is human reported and therefore unreliable. Metrist monitors via bots

It can be useful, but you have to take it with a grain of salt. A perfect example is the recent Facebook (Meta) outage. When that happened, Downdetector showed that ATT, Verizon, and T-Mobile all had issues. They didn't, it was just Facebook and users mentioned or otherwise claimed that it was their mobile carrier.

Re: Heroku was Down

#97

Post by Trasmatta » Thu, Feb 24, 2022, 5:14 PM UTC

driverdan wrote: post #72

iamricks wrote: post #13

So... what are the chances this is related to a cyber attack from Russia? Also our apps are down

Practically zero. Why would Russia care about Heroku?

Heroku runs on AWS, so it would be an AWS attack of some sort. But AWS in general seems to be up from what I can tell, so I'm feeling like it's not a cyberattack, and just a Heroku specific problem.

Re: Heroku was Down

#98

Post by craigkerstiens » Thu, Feb 24, 2022, 5:14 PM UTC

It appears to only be affecting apps that have multiple dynos.

While Heroku is busy fixing the issue if you scale your app to a single dyno (assuming it can handle the traffic) it should restore availability.

Re: Heroku was Down

#99

Post by reubano » Thu, Feb 24, 2022, 5:15 PM UTC

zorpner wrote: post #77

reubano wrote: post #63

Earlier quoted context omitted.

What makes Downdetector unreliable? It's showing a huge spike right now.

Downdetector relies on user reports, so e.g. if a user's ISP is down and they can't get to Facebook, they might report Facebook being down (or vice versa). DD spikes are typically indicative of _something_, but it's not always the actual down service.

Gotcha. Although for a spike this large (over 1000) for a tech service (AWS vs Facebook) I'd give some credence to it. It could be that everyone who reported AWS as down is running on Heroku. Definitely possible. For comparison Azure [0] and Google Cloud [1] have spikes under 30.

[0] https://downdetector.com/status/windows-azure/ [1] https://downdetector.com/status/google-cloud/

Re: Heroku was Down

#100

Post by bisRepetita » Thu, Feb 24, 2022, 5:17 PM UTC

craigkerstiens wrote: post #98

It appears to only be affecting apps that have multiple dynos. While Heroku is busy fixing the issue if you scale your app to a single dyno (assuming it can handle the traffic) it should restore availability.

I had single dynos affected.