Make sure the port your URL is mapped to is the same port your application is listening to. Also, ensure that the application is listening to 0.0.0.0 and not :: or localhost.

I would check the app binding first. A Railway deployment can show as online while the public URL still fails if the process is only listening on localhost, 127.0.0.1, or a hardcoded port.

The service should listen on the port Railway provides and bind to all interfaces:

host: 0.0.0.0
port: process.env.PORT

For common setups, that usually means one of these patterns:

Express:
const port = process.env.PORT || 3000;
app.listen(port, "0.0.0.0");

Next.js custom start:
next start -H 0.0.0.0 -p $PORT

Vite preview:
vite preview --host 0.0.0.0 --port $PORT

After changing that, redeploy and check the runtime log line that says what host and port the app is listening on. If it says localhost, 127.0.0.1, or a port that is not $PORT, the Railway proxy will not be able to reach it even though the deployment itself is running.

Also confirm the service has a public domain attached under the service networking settings. If the app only has a private/internal address, it can be online inside Railway but still not reachable from a browser.

My order of checks would be:

1. Service has a public Railway domain or custom domain attached.
2. App start command uses $PORT, not a fixed port.
3. App binds to 0.0.0.0, not localhost.
4. Runtime logs show the app listening after deploy.
5. Any healthcheck path configured in Railway actually returns 200.

Most cases with this symptom come down to the app listening on the wrong host or port, especially when the deploy is marked online but the URL itself does not load.

Thanks for replies

The issue seems to be occured due to some ISP problem( I believe)

That network was not being reaching out to railway.com

I tried changing to my mobile network, then url is reachable..

Glad to hear you tracked it down. If your ISP is blocking or failing to resolve Railway domains, you can try switching to a public DNS resolver like 1.1.1.1 or 8.8.8.8 on that network, which often works around ISP-level DNS issues.