4 months 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.
- Project: https://railway.com/project/5dea1c29-6a5b-4299-9158-21275562936b/service/b83e51b5-1b81-47bf-9634-6a1db420dc78
- 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
4 months 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). All services healthy via \*.[up.railway.app](http://up.railway.app) URLs. Domain-to-service mapping appears broken on Railway's side.
4 months ago
Can you please try to strip the fastly-ff header before proxying to your upstream?
4 months 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 • 4 months ago