Tell HN: Heroku crashes for new deploys

21 points by danielskogly ↗ HN
Update: The fault seems to be limited to new deploys, and according to ntomas the problem lies with Heroku Router

We just did a routine deploy on Heroku, and _every single request_ began failing. Checking logs it says "code=H10 desc="App crashed"" without anything else.

Looking around elsewhere, I see other apps are failing with the exact same error (eg. https://isdown.app/integrations/heroku?c=1685469931)

Seems there was scheduled maintenance on some logging system, and there's some homepage / sign-up page service being done too (https://status.heroku.com/).

15 comments

[ 4.9 ms ] story [ 42.5 ms ] thread
Sites I've found being down with the exact same error. No clue what's going on here:

  1. Ours - https://instorier.com 
  2. IsDown - https://isdown.app 
  3. LexGo - https://www.lexgo.be  
  4. Zen Factuur - https://zenfactuur.be/  
  5. Dandelion events - http://dandelion.events/
Multiple other people on Twitter saying the same: https://twitter.com/search?q=heroku&src=typed_query&f=live
I deployed updates to two apps in the last hour and they are now offline.. apps that didn't receive a deploy are working correctly.

Console also works fine for all apps

Exactly the same here - the ones not deployed recently works fine!
Checking the logs for the web process, and they are working correctly. The worker process also working fine.

The problem is with the Heroku router...

Yeah I also managed to run the web process without any issue:

```

heroku run bash -a myapp

$ bundle exec puma -C config/puma.rb

[All fine]

```

It's definitely coming from their router. Opened a ticket 1h ago without reply so far, and it makes you wonder why they even bother to have a status page.

Same here, both Staging and Production are completely down. Yet their statuspage shows no error at all.
And now https://isdown.app/integrations/heroku?c=1685469931 is also down because they use Heroku and they did a deploy without realising they would go offline as a result :-)
Yep... founder of IsDown here!

Really happy with this! At least we are still monitoring everything, and it will continue to send notifications...

I will receive a notification from IsDown when Heroku status page is updated :)

Received a support ticket response saying they are looking into it and that they'd be updating the status page soon. (I want to be understanding, but 2+ hours is a long time to not update the status page)
Our app crashed by simply changing an environment variable. Was searching for over 45 minutes without finding anything.
I got an update on the support ticket. To try to deploy a new release and check if it works again. It worked for me.
It also worked for me. Thanks for your message.