2 months ago
My project is affected by a networking issue that appears to be at the Railway Edge layer.
Evidence:
• Deployment succeeds.
• Application startup completes successfully.
• Uvicorn listens on 0.0.0.0:8080.
• Public Networking is configured correctly.
• Both my original service and a newly created service have the same issue.
• DNS resolves normally.
• curl reaches the Railway IP but times out during the TCP connection.
• ITDog global tests also fail.
• The application itself is healthy.
The Railway AI Agent already concluded:
"The TCP timeout strongly suggests the edge layer isn't routing traffic to your replicas."
Could you please have the infrastructure team check the networking for this project/service?
The problem reproduces on two independent Railway services in the same project.
8 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
Can you confirm that you have set the right port for the generated/custom domain?
mayori
Can you confirm that you have set the right port for the generated/custom domain?
2 months ago
Yes.
Both the generated domain and the custom domain are configured to use port 8080.
The application starts successfully and Uvicorn is listening on:
Uvicorn running on http://0.0.0.0:8080
The deployment is marked as successful and the service status is Online.
However, both the generated Railway domain and the custom domain time out during the TCP connection stage.
I also created a brand-new Railway service with the same code and the same result.
So it doesn't appear to be an application or port configuration issue.
I also tested from multiple external networks (including ITDog global tests), and all requests time out before reaching the application.
0x5b62656e5d
Can you share the URL?
2 months ago
Sure.THX
Generated Railway domain:
https://practical-happiness-production-2370.up.railway.app/health
Custom domain:
Both domains time out before reaching the application.
The application itself starts successfully:
- Deployment succeeds
- Service status is Online
- Uvicorn listens on 0.0.0.0:8080
- Public Networking is configured to port 8080
I also tested from multiple external networks and ITDog global HTTP tests, and both domains consistently time out.
2 months ago
I'm able to access that URL just fine. Try using a VPN to access the site.
Attachments
0x5b62656e5d
I'm able to access that URL just fine. Try using a VPN to access the site. 
2 months ago
Could you also let me know which IP address the generated domain resolves to on your side?
Mine resolves to:
69.46.46.97
I want to confirm we're reaching the same edge node.
2 months ago
69.46.46.97
If you're experiencing an ISP/regional block, then your only options would be to use a different network, a VPN, or use 1.1.1.1 as DNS.
2 months ago
thank u