15 days ago
All custom domains on our project have been returning 504 Gateway Timeout or connection timeouts for 2+ hours. All services
respond normally when hit directly via *.up.railway.app URLs — only custom domain routing is affected.
Region: us-west2
Started: ~1:20 PM PST (Feb 26)
Status page shows "Elevated Error Rate in Edge Network" with fix deployed at 9:21 PM, but issue persists
Affects both production and staging custom domains
All backend services healthy via Railway internal URLs
Is there an ETA for full resolution? Happy to provide request IDs if helpful.
Attachments
4 Replies
15 days ago
Update: 504s have stopped, now getting 404 {"message":"Application not found"} from Railway's edge since ~6:10 PM PST.
Tried: redeployed gateway, removed and re-added custom domain with fresh CNAME + TXT (both verified green in dashboard). All
services healthy via *.up.railway.app URLs. Domain-to-service mapping appears broken on Railway's side.
Attachments
dekodeveloper
Update: 504s have stopped, now getting 404 {"message":"Application not found"} from Railway's edge since ~6:10 PM PST.Tried: redeployed gateway, removed and re-added custom domain with fresh CNAME + TXT (both verified green in dashboard). Allservices healthy via *.up.railway.app URLs. Domain-to-service mapping appears broken on Railway's side.
15 days ago
Can you please try to strip the fastly-ff header before proxying to your upstream?
15 days ago
Update: Was planning to try stripping the fastly-ff header in our nginx gateway config (as suggested by @brody), but all our
custom domains just came back on their own (~7:56 PM PT). Looks like Railway resolved it on their end. All subdomains recovering
now.
Status changed to Solved brody • 15 days ago