Hey chinjan!

I curled your domain and it's returning 404 with x-railway-fallback: true header and "Application not found" in the body.

That means Railway's edge proxy can't find a running deployment to route to, traffic never hits your container.

Few things to check:

1. go to your service's deployment tab and make sure the latest deploy is actually in "Active" state, not crashed or stuck.
2. Check the deploy logs for any crash loops or port binding errors.
3. Make sure your app binds to 0.0.0.0:$PORT and not localhost or 127.0.0.1. Railway injects the PORT env var automatically. If you hardcoded a port, that's likely the issue.

If everything looks fine on your end, try triggering a redeploy (Settings > Redeploy). Sometimes Railway's routing table gets stale and a fresh deploy forces it to re-register.

Also worth checking if you're on the legacy runtime, there have been cases where the new edge proxy migration broke routing for legacy services without any code changes. You can check this in Settings > General.

If none of that works, share your deploy logs and I can dig deeper.

If my answer helped, please, mark as the solution, so I can earn the bounty.

See you!