3600 seconds is the current limit for Healthchecks Timeouts. I have moved this question to the Feedback section so others can upvote.

I need increase on Healthchecks Timeouts, otherwise I have to announce community that I will have to spend 24 hours to update the backend. This gives too much friction on deploying backend.

Or is there a way to prepare a certain path to check if the backend has finished backfill without timeout?

Call it like "Readyness check".
Instead of requesting to the path frequently like health check, Readyness check can set the interval to send request (e.g. 1 hour, 1 day, 1 week, etc).

This can provide efficient solution for projects with long backfills without wasting resources on sending request to check path every 6~8 seconds.

Minimum interval should be 1 hour.

Hi there, unfortunately that's the limit we have set.

What about readyness path idea? can you implement that?

Unfortunately at this time, we are not able to do this, but maybe if more folks request, we can bring it to our roadmap.

+1 for raising the healthcheck timeout

Thank you all for the feedback folks, ticketed internally and we'll revisit if there's more demand so please smash that upvote / comment here if you'd like this!

+1 for longer healthcheck timeouts. We're building an open source project that would benefit a lot from this. When our service starts up there's a historical backfill that can potentially take a few days. We'd love for there to be a better deployment narrative through Railway.

Some additional background info on our context: https://github.com/namehash/ensnode/issues/110#issue-2820548935

+1 for longer healthcheck timeouts.

+1

+1 We want our blockchain indexer to catchup to realtime before being available, increasing health check timeout would help us too.

Yes, please!! Longer timeout for railway is much needed!!