8 months ago
Hey Railway team — I’m experiencing a critical issue with my production app hosted on Railway.
Problem: My API URL (
*.up.railway.app) is throwingERR_NAME_NOT_RESOLVED.
The project was working perfectly until a few days ago. Initially I ignored it thinking it's on users end and very few were having the issue but now more people are having the issue.
I tried updating with new API URL in my frontend (still using Railway’s default URL).
No custom domains are involved right now.
It works for me (even in incognito and new browsers), but multiple users from different part of the country are affected — they’re all getting the error.
I checked similar threads in the forum and saw replies that this is usually an issue on the user’s end (DNS, ISP, etc.), but how could that explain multiple users being affected at once?
nslookupand public DNS checkers (like Google or Cloudflare) also fail to resolve the Railway URL.This is driving me crazy, and I’ve been trying to fix it all day. It’s negatively impacting real users, and I need help confirming:
Is there any DNS propagation or issue on Railway’s end right now?
Could something internal be rate-limiting or misrouting this service URL globally?
I’ve really enjoyed Railway until now, but this issue is severe and blocking — and if it persists, I may have to migrate. :(
Thanks in advance — really hoping for helpful comments to get resolved quickly.
7 Replies
8 months ago
I wonder if this might be an issue that I've seen before related to stale records on cloudflare. Unsure, can we get a bit more info about the project?
8 months ago
I'm currently experiencing some similar issues here. Broken deployments and inconsistent responses even after successfully restoring a previous deployment.
noahd
I wonder if this might be an issue that I've seen before related to stale records on cloudflare. Unsure, can we get a bit more info about the project?
8 months ago
Sure, what do you want to know?
zerorinadmin
Sure, what do you want to know?
8 months ago
Whats the tech stack. Is it an API? Have you recently purchased the domain or switched settings with it?
noahd
Whats the tech stack. Is it an API? Have you recently purchased the domain or switched settings with it?
8 months ago
React and node. I have been using the default API url that Railway provides and havent switched. But now I regenerated the new url from railway, updated the old one in code still got same issue. The worst part is its working fine on my end even with the new browser incognito mode, but my users arent able to access so hard to reproduce. I havent changed any settings. But do let me know if there is anything i need to check.
zerorinadmin
React and node. I have been using the default API url that Railway provides and havent switched. But now I regenerated the new url from railway, updated the old one in code still got same issue. The worst part is its working fine on my end even with the new browser incognito mode, but my users arent able to access so hard to reproduce. I havent changed any settings. But do let me know if there is anything i need to check.
8 months ago
Can you try flushing your cache? That might be a solution to see. You said multiple users from different countries are having issues. Is that due to private network firewall configuration blocking railway?
noahd
Can you try flushing your cache? That might be a solution to see. You said multiple users from different countries are having issues. Is that due to private network firewall configuration blocking railway?
8 months ago
Private network firewall from user's end? Also "flushing the cache" where. In my laptop/OS? Although my users are from local market, Some of my friends from other countries tried to use the app and they were not able to access it. However im not sure if its due to the same issue or the other issue. But first want to solve the ERR issue.