2 months ago
Hey Railway team,
We’re running into a pretty serious issue right now where deployments are getting stuck on “Initialization” and never progress.
Imagine if this is happening at the worst possible time, if we had a critical hotfix that needs to go out, and we’re basically blocked from shipping.
What’s happening
Builds/deployments get stuck on Initialization
No clear error output
Retrying doesn’t reliably help
This is effectively a full deployment outage on our side
This week has already been rough from our end because we’ve also been seeing weird routing behavior when using Cloudflare.
When Cloudflare proxy is enabled, Railway consistently reports traffic entering through:
x-railway-edge: railway/asia-southeast1-eqsg3a
-----------------------------------
Railway is great when it works, but issues like this are brutal in production. When deployments stall with no actionable feedback, it’s not just “a minor inconvenience”, it’s downtime risk.
If anyone else is seeing builds stuck on Initialization right now, please comment. Would be good to know whether this is isolated or widespread.
Thanks.
Attachments
8 Replies
2 months ago
Hey, Railway is currently suffering from an incident on build times
https://status.railway.com/cmkhgk0vh040fth2frxk93tvp
The team is already aware and working on a fix! Sorry for any inconvenience
For future reference, the Railway team is actively working on solving issues related to builds and even released their new build system named "Metal Builds", they're really working hard on closing all the gaps
2 months ago
Invalid prisma.user.findUnique() invocation: Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 30, connection limit: 100)
will1980j
Invalid prisma.user.findUnique() invocation: Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 30, connection limit: 100)
2 months ago
Hey, that does not look like to be an issue related to the current incident, can you please open your own help thread?
2 months ago
Confirming passos that we are working on this to resolve as quickly as possible.
Status changed to Awaiting User Response Railway • about 2 months ago
passos
Hey, Railway is currently suffering from an incident on build timeshttps://status.railway.com/cmkhgk0vh040fth2frxk93tvpThe team is already aware and working on a fix! Sorry for any inconvenienceFor future reference, the Railway team is actively working on solving issues related to builds and even released their new build system named "Metal Builds", they're really working hard on closing all the gaps
2 months ago
Thanks for the quick response, I appreciate that!
Would you guys recommend getting off of Metal if it's not yet production ready yet, with these gaps that need closing?
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Seems to be many things at once stuck re-deploying and git auth is broken too
steelzeh
Thanks for the quick response, I appreciate that!Would you guys recommend getting off of Metal if it's not yet production ready yet, with these gaps that need closing?
2 months ago
I would not recommend as Metal Builds is becoming the de-facto standard for builds and it is production ready, also the current incident also affects non-metal builds. From my own comms with the team, they're actively taking this as top priority and asking us, community members, to bring to their attention any issue related to Metal Builds.
2 months ago
Yeah GIT oAuth is broken, guessing that's why the builds are stuck and not working
Status changed to Solved sam-a • about 2 months ago