16 days ago
Hi, I’m seeing an issue on a new Railway workspace where all newly generated *.up.railway.app service URLs are not resolving publicly.
The services themselves are healthy and deployments are successful, but opening the generated Railway URLs gives DNS resolution errors like ERR_NAME_NOT_RESOLVED / Could not resolve host.
This is affecting multiple services, not just one app, so it looks broader than a single deployment issue. Has anyone seen this before, or is there anything specific I should check on the Railway side?
1 Replies
16 days ago
All six of your .up.railway.app service domains are resolving and responding with HTTP 200 from our edge right now, so the issue is on the DNS resolver side of your network rather than on Railway. The most common cause is an ISP, VPN, or local network DNS resolver that filters or fails to return records for *.up.railway.app. Try switching your device or router to a public resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8), flush your local DNS cache, and test from a different network (e.g. phone on mobile data) to confirm.
Status changed to Awaiting User Response Railway • 16 days ago
9 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 9 days ago