22 days ago
After the recent EU West outage, my two custom domains are stuck and
won't serve my app.
Symptoms:
-
Both the apex domain and its www subdomain return HTTP 404 with the
header x-railway-fallback: true
-
The TLS certificate has been stuck in VALIDATING_OWNERSHIP for 12+ hours
-
The default *.up.railway.app URL works perfectly — the service itself
is healthy and serving 200
What the API shows (all looks fine):
-
Custom domains: syncStatus = ACTIVE
-
DNS records: status = PROPAGATED
-
DNS is correct on my side (CNAME via Cloudflare DNS-only, pointing at
the Railway edge targets)
This started right after the EU West incident. It looks like the edge
routing table never picked these domains back up after the outage — the
edge keeps returning the fallback 404, so the Let's Encrypt HTTP
challenge can't complete either.
I have not touched the domains since (no further delete/recreate).
Could someone force an edge cache flush / re-sync for these two domains?
I can share my Project ID, Service ID and custom domain IDs privately —
happy to DM them to a team member.
Thanks!
Pinned Solution
22 days ago
Make sure to add the TXT record to your domain. If you’re using the API, you can access the content for it under the verificationToken property under status.
2 Replies
Status changed to Open Railway • 22 days ago
22 days ago
Make sure to add the TXT record to your domain. If you’re using the API, you can access the content for it under the verificationToken property under status.
22 days ago
That was it — I was missing the _railway-verify TXT records.
Added them, domain is verifying now. Thanks a lot!
Status changed to Solved Railway • 22 days ago
