a month ago
Project ID: 594445ec-ecc5-4b4e-95dd-95f8c33775c1
Service: frontend
Domain: savvystat.com (root/apex)
DNS is correctly configured (CNAME @ → xs1g0hbj.up.railway.app, proxied via Cloudflare; TXT verification record present). www.savvystat.com on the same service works correctly (HTTP 200). The apex domain has been stuck in a non-working state for 1+ hour.
curl -I https://savvystat.com returns:
HTTP/1.1 404 Not Found
x-railway-fallback: true
x-railway-edge: ams1
This confirms the request reaches Railway's edge but Railway isn't routing it to the service — the domain doesn't appear to be registered/verified on your side despite DNS being correct.
I already tried deleting and re-adding the custom domain once (per community reports of a similar bug on the forum), which issued a new CNAME target (xs1g0hbj.up.railway.app) that I updated in DNS — but the issue persists.
Could you check why savvystat.com isn't routing correctly on your end?
1 Replies
a month ago
The apex domain is routing correctly now and returning HTTP 200 through Railway's edge, with the certificate valid, DNS propagated, and verification confirmed. The transient fallback you saw can occur when a domain entry is removed and re-added (as you did), since the new CNAME target and verification token need a short propagation window before edge routing picks them up.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved alexeyiakovlev • about 1 month ago