Project ID: 10707cfb-7cfc-418c-98a9-d5f74ff1eeda

Service ID: c0b66006-2fb4-4182-aad1-3b4efcf73034

Domain: materials-dashboard-production-dea1.up.railway.app

Issue: The service domain (HTTPS) doesn't forward any traffic to the container — not a single packet gets through. Running railway logs --network during a live request to the domain shows zero TCP packets reaching the container — only background mDNS noise from container startup.

I also tested the alternative public access mechanism (TCP proxy) on the same application port — it works correctly and returns a proper response from the application. This means the container is fully healthy and network-reachable in principle — the problem is specifically in the HTTP(S) service-domain edge routing configuration for this service.

Already ruled out: WAF / Under Attack Mode is disabled; tried 2 regions (us-west2, us-east4); 2 fresh projects recreated from scratch; 4 different port-binding configurations in the app (IPv4-only, IPv6-only, dual-stack, default); toggled targetPort back and forth (8080→8081→8080); recreated the domain multiple times; the status page shows no active incidents.

Could someone from infrastructure please check the domain → container routing binding for this service? It looks like an edge routing bug rather than a service misconfiguration.