Service: editorial-app-production (project id 235a9ae6-3022-4927-a4ca-4142c68367de, service id 28a3024a-ddf4-418d-aa29-7b6ec94c0f31)

The deployment shows as "Active" and the deploy logs confirm gunicorn starts successfully and listens on 0.0.0.0:8080, matching the port shown under Networking. However, every request to both my custom domain (gestio.editorialgerminar.com, CNAME to editorial-app-production.up.railway.app) and the raw editorial-app-production.up.railway.app domain returns an "upstream error", and no new log line appears in Deploy Logs when the request is made — meaning the request never reaches the container. I performed a manual restart of the service (fresh clean boot confirmed in the logs at 09:51 UTC) and the issue persists identically. I've ruled out DNS (CNAME confirmed correct), client network/browser (tested on 2 networks + private browsing, same result), Serverless/sleep (disabled), and there's no reported platform-wide incident. Could you check the routing/proxy state for this service?

I also found a similar report in this Discord (thread: 'Evidence: nucleus replicas unresponsive while Railway reported 12/12 active') describing the same dashboard-vs-reality mismatch (service shown as active/healthy while unresponsive) — might be a related underlying issue.