Hi Railway team,

I’m seeing a routing/domain issue on production. The service deploys successfully and passes healthchecks, but public domains return:

“Not Found - The train has not arrived at the station.”

Project/Env:

- Environment: production

- Service status in dashboard: SUCCESS

- Region in build logs: us-east4

Affected domains:

- default Railway public domain (.up.railway.app)

- custom domain (proxied by Cloudflare)

(both fail with the same Railway error page)

Request ID shown on error page:

- YK7RZKtyR4eEfkVL8u2xcg

What I observe in logs (2026-02-27):

- Build completes successfully

- Start command runs: npm run start -> next start

- App becomes ready Ready in 609ms)

- Listening on localhost:8080

- Healthcheck /api/health succeeded

- Service keeps running after startup

Relevant log highlights:

- “Starting Healthcheck”

- “[1/1] Healthcheck succeeded!”

- “> next start”

- “✓ Ready in 609ms”

- “Local: http://localhost:8080”

Expected:

- Domains should route to the running app.

Actual:

- Public domains return Railway “train has not arrived” page despite healthy app/container.

Could you please check edge routing/domain provisioning for this service/environment and rebind if needed?

Thanks.