a month ago
Hello Team,
I am currently hosting a Node.js backend with a MySQL database on Railway. The deployment is successful, and the APIs are working correctly in some environments.
However, I am facing a critical issue:
- The API works when accessed from certain networks/devices.
- But it does NOT work when accessed from:
- Jio mobile network
- WiFi connections (multiple tested)
In these cases, the request either:
- Times out, or
- Fails to connect to the server
Details:
- Backend: Node.js (Express)
- Database: MySQL (Railway hosted)
- Deployment status: Successful
- Public URL: https://graceful-prosperity-production.up.railway.app/health
What I have verified:
- The service is running and accessible from some networks
- No application-level errors in logs
- Routes are correctly defined
- CORS is configured (if applicable)
Concern:
This appears to be a network accessibility or routing issue rather than an application bug.
Request:
Could you please check:
- If there are any IP restrictions or regional/network-level blocks affecting access
- If Railway services are fully accessible across all ISPs (especially Jio India)
- If there is any issue with public networking, DNS, or edge routing
This issue is impacting real users who are unable to access the API from mobile and standard WiFi networks.
Looking forward to your assistance.
Thanks & Regards,
Paramjit Singh
1 Replies
a month ago
Your services are deployed and running successfully on our end, and we do not apply any IP restrictions or ISP-level blocks. We are aware of reports from users in India where certain ISPs (including Jio) block or filter traffic to *.up.railway.app domains. A workaround is to use a custom domain on your service, which routes traffic through a different hostname that these ISPs are not filtering. You can also run our Network Diagnostics tool from an affected network and share the output here so we can investigate further.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago