a day ago
Our service backend-production-8904.up.railway.app (edge IP 153.52.255.0, served by railway-hikari) is unreachable from some mobile carriers in Iraq: connections are aborted (ERR_CONNECTION_ABORTED), including a plain browser request to /health. The same phones reach it at once through a VPN, and it worked from those same networks until early November. Other users report the same on 153.52.255.x since 2026-11-06 (station thread "Custom domains + railway.app domain unreachable"). Can you check reachability of your new edge from Iraq (Asiacell / Zain / Korek), or move our domains to an edge IP that is reachable?
2 Replies
a day ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 1 day ago
a day ago
Unfortunately, if this is a regional block on railway generated domains caused by some ISPs in Iraq, then your only option would be to set up a custom domain proxied through cloudflare, as this isn't an issue related to Railway.
4 hours ago
On your question about moving the domain to another edge IP, Railway’s support bot addressed this in a related thread. It said Railway cannot assign or exclude a specific public edge IP for a domain, and that redeploying or moving the service to another region does not select a different one. I’d leave the deployment running while you narrow down where the connection fails. Related Railway support reply
There is also a relevant incident on the status page. On November 4, Railway reported that some external networks had blocked Railway IPs after seeing traffic with forged source addresses. Railway closed that incident on November 9 at 18:03 UTC. Your November 6 timeline overlaps, but the notice does not identify Asiacell, Zain, Korek, or 153.52.255.0. The same phone working through a VPN narrows this to a difference between the two network paths. It still leaves DNS, routing, and filtering as possibilities. Railway incident report
The most useful next test is from one affected SIM. A laptop tethered to the phone is enough. With Wi-Fi and VPN off on the phone, run these two commands close together. The second uses the IPv4 address from your report while preserving the HTTPS hostname and certificate checks. If Railway’s current IPv4 address has changed, use the current one for that comparison. How curl’s --resolve works
host=backend-production-8904.up.railway.app
curl -4sv --connect-timeout 8 --max-time 15 "https://$host/health" -o /dev/null
curl -4sv --connect-timeout 8 --max-time 15 \
--resolve "$host:443:153.52.255.0" "https://$host/health" -o /dev/null
- If the first request fails to resolve the name and the second returns HTTP, send the carrier its DNS result alongside the working pinned-address test.
- If both attempt the same IP and fail before curl prints Connected to, repeat the pinned test through the VPN. A successful VPN run gives Railway and the carrier a comparison with the destination IP, port and hostname held constant.
- If curl prints Connected to and then fails during TLS, include the exact TLS error. If it returns an HTTP status, include that status and the X-Railway-Edge header if present. Those outcomes point to different stages of the connection.
For escalation, one failed run and one successful control are enough to start. Include the UTC timestamps, carrier, destination IP, and the last curl line before failure. Ask Railway whether it can correlate the failed attempt at its edge, and ask the carrier to review reachability to that IP on TCP 443. Share the subscriber’s public IP privately if support needs it for correlation.
For an immediate workaround, the Cloudflare suggestion above is worth testing on a second hostname before changing the production API URL. Add the custom hostname to the same Railway service, publish the CNAME and verification TXT Railway supplies, enable Proxied on the traffic CNAME, and wait for Railway to verify the domain. Then try /health on that hostname from the same SIM with the VPN off. If it succeeds while the generated hostname still fails, you have a tested workaround for that carrier without moving the app. Railway custom domains · Cloudflare proxy behavior
AI-assisted. I checked the linked sources. I haven’t tested from an Iraqi mobile network.