Hi Railway team,

I'm experiencing an issue with my service ijaari-server (production: ijaari-server-production.up.railway.app).

Issue:

After pushing a code update to GitHub, Auto Deploy triggers correctly and the Build completes successfully (image push finishes, status shows "Active"). However, the Deploy Logs tab remains permanently stuck on "Your logs are loading..." — no Starting Container line ever appears, and the service is unreachable (DNS/connection failures from the public domain).

What I've tried:

Manual Restart on the deployment — no logs appeared afterward either

Manual Redeploy — same result, build succeeds, deploy logs stay empty

Verified the public domain exists under Settings → Networking (port 8080, matches my app's PORT env var usage)

Confirmed via the in-browser Console that when the container was previously running, it bound correctly to the assigned port

Reviewed historical Deploy Logs — prior to this issue, the service ran fine and even showed a clean Starting Container → app startup sequence, followed by periodic SIGTERM / container restarts that I could not explain (multiple restart cycles within the same hour, no error logged before the SIGTERM)

Service details:

Service name: ijaari-server

Domain: ijaari-server-production.up.railway.app

Runtime: Node.js 22.22.3 (railpack v0.27.2)

Builder: Metal builder (builder-lwbyjv)

Region: US West

Last known working deployment had build digest: sha256:80877932f5a41639786b4cb15367028112b8ebc45ee534a05efc1c02e315b298

Question:

Is there a known issue with the Deploy Logs stream or container startup on this builder/region right now? Could this be related to infrastructure on your end rather than my application code, given the build itself completes without errors but the runtime phase never logs anything?

Any help identifying whether this is a platform-side issue would be greatly appreciated.

Thanks!