Skip to content
Deployment fails repeatedly on Railway
myselfprince
OP

13 days ago

Deployment 9ae87cf6 repeatedly fails before npm install/Next.js build. Railpack cannot download mise v2026.10.14 from GitHub: HTTP 504 Gateway Timeout. Earlier attempts also failed downloading Railpack v0.43.0. Region: Southeast Asia. Plan: Hobby. The previous deployment works, and the same code builds on Vercel. Please investigate the build-tool download failure.

Solved

3 Replies

Railway
BOT

13 days ago

We're sorry for the trouble. Your deployment failed while the build was downloading its build tools from GitHub, and GitHub is currently having an outage that is causing build failures. We're tracking it as the GitHub Outage Affecting Builds incident and are still monitoring.


Status changed to Awaiting User Response Railway • 13 days ago


Railway

We're sorry for the trouble. Your deployment failed while the build was downloading its build tools from GitHub, and GitHub is currently having an outage that is causing build failures. We're tracking it as the [GitHub Outage Affecting Builds](https://status.railway.com/incident/97GIDVEY) incident and are still monitoring.

myselfprince
OP

13 days ago

Thanks. Manual redeploy also fails while downloading Railpack/mise from GitHub. Please keep this open until the incident is resolved.


Status changed to Awaiting Railway Response Railway • 13 days ago


Railway
BOT

13 days ago

The GitHub outage is still open on our side and we don't have an ETA yet, since recovery depends on GitHub restoring service. Your manual redeploy fits that picture: its build stops while downloading Railpack and mise from GitHub, and those downloads are failing during the outage.


Status changed to Awaiting User Response Railway • 13 days ago


Railway
BOT

6 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 6 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...