4 months ago
This is a recurring issue I've documented previously: https://station.railway.com/questions/extremely-slow-first-request-latency-1-4cded57d
Latest Incident:
- Date/Time: Feb 3, 2026, 9:30-9:34 AM CST
- Domain:torquetrader.io
- Request ID: 016YyGc5T0CNez2ZozsQ6Q
- Error: Railway "Not Found" page - "The train has not arrived at the station"
Evidence this is Railway infrastructure, not my app:
- My app was healthy the entire time - Railway metrics show continuous CPU/Memory/Request activity throughout the incident
- Uptime.com monitoring (checking every 60 seconds) showed 100% uptime with no downtime detected
- Workaround: Toggling Cloudflare proxy off/on immediately fixes it
Pattern: This happens regularly on weekday mornings around 9:00 AM CST. I have to toggle Cloudflare proxy settings to restore connectivity, which suggests Railway's custom domain routing is losing the domain mapping.
Question: Is there a known issue with Railway's custom domain routing when Cloudflare proxy is enabled? Should I disable Cloudflare proxy permanently, or is there a fix on Railway's end?
1 Replies
4 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 4 months ago
4 months ago
another user with same issue today: https://station.railway.com/questions/some-users-can-t-reach-service-tcp-con-78d4efdc