All Railway-generated public domains on our project are returning Not Found [CFN #0005] from Railway's CDN layer, despite services showing as healthy and running in the dashboard. This affects every service in the project simultaneously, which strongly suggests a DNS or CDN routing misconfiguration on Railway's infrastructure rather than an application issue.

Affected URLs (all Railway-generated domains):

https://matsya-farm-ai-ui-production.up.railway.app/

Error response received (via curl):

HTTP/1.1 404 Not Found

Content-Type: text/html; charset=iso-8859-1

Content-Length: 21

Not Found [CFN #0005]

All domains resolve to Railway's IP 64.29.151.221 (TCP connection succeeds), but Railway's proxy returns this 404 before the request ever reaches our containers. For HTTPS, the TLS handshake also fails on some URLs.

What we've confirmed:

• Services are running and healthy in the Railway dashboard
• Application logs show Next.js starting successfully on the correct port (8080)
• Public networking is configured with port 8080 for the UI service
• We are using Railway-generated *.up.railway.app domains — no custom DNS involved
• Tried removing and re-adding the generated domains — same result
• Tried generating fresh domains for new service deployments — same result
• The issue affects ALL services in the project simultaneously

Suspicion: Since we are exclusively using Railway-generated domains (no custom DNS configuration on our end), the routing failure must originate within Railway's own CDN/proxy layer. The CFN layer is not mapping these *.up.railway.app subdomains to our running service backends. TCP connectivity to 64.29.151.221 succeeds, confirming Railway's servers are reachable, but the internal routing table appears to have no valid backend entries for any of our domains.