a month ago
Title: Repeated US East deployment timeout before any build output
I’m experiencing repeated deployment failures for a service hosted in Railway’s US East region.
Across three attempts over several days:
- One failed during
Initialization → Snapshot code - Two failed during
Build → Build image - Every attempt returned
Failed to connect before the deadline - The latest attempt failed after approximately seven seconds
- No normal Docker or application build output appeared
- Pre-deploy and Deploy never started
The application configuration remained unchanged between attempts. Railway’s public status page showed operational status during the latest attempts.
Could this indicate an isolated Railway builder, task-queue, or control-plane connectivity issue? What should I check before attempting another deployment?
I can provide project, service, and deployment identifiers directly to Railway staff if there is a private way to share them. Additional context: I found another Central Station report from August 18 describing the same empty build logs and Failed to connect before the deadline errors. Railway’s bot confirmed those symptoms were consistent with the active all-regions deployment incident.
My service has continued showing the same behavior after that public incident was marked resolved, including another US East Build → Build image failure on August 21 with no normal build output. Could Railway confirm whether there may be a lingering or isolated builder issue affecting this service or project?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Thanks for the detail, it made this quick to trace. This isn't the Aug 17-20 platform incident coming back. Your builds are reaching our builders and failing on a specific, fixable error.
On the attempts with no output, the build fell back to Railpack and stopped at "No start command detected," so it never reached your Docker build. That happens when the deploy doesn't pick up your Dockerfile config and uses the default builder. On the attempt that did use your Dockerfile, the image built and pushed fine and the failure moved to your pre-deploy step, which matches your latest commit enforcing a pre-deploy migration failure. "Failed to connect before the deadline" is a generic config-error label here, not a network or builder outage, and the same builder built your service fine on an earlier commit.
Push a new commit to trigger a fresh deploy rather than using Redeploy, and confirm the service builds from your Dockerfile so it doesn't fall back to Railpack. If it then stops at pre-deploy, check that migration step's logs. Everything build and deploy side is green right now, with no failures tied to your project since the Aug 21 attempt.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago