Custom domain stuck on edge fallback ("Application not found") despite valid cert + correct DNS.

Project: heroic-vitality (a219ef11-a39e-496f-b156-1b477ef58349)

Environment: production (817b8e50-aa3a-40d6-b336-e3a833bf14dc)

Service: fisiocriotibur (671eb0ca-316d-4f1c-b56d-b8986c9beae0)

Custom domain: www.fisiocriotibur.it (id 51877ba2-eef8-490c-9958-fa4678f5f3c2)

CNAME target: j62ddfn3.up.railway.app

Everything is green in the API: DNS status = PROPAGATED (CNAME correctly resolves to j62ddfn3.up.railway.app), certificateStatus = VALID, latest deployment = SUCCESS, single service / single environment.

But HTTPS requests to https://www.fisiocriotibur.it return:

HTTP/2 404, server: railway-hikari, x-railway-fallback: true

body: {"status":"error","code":404,"message":"Application not found"}

(sample request-id: 2OXJxXFVT6uKdHbX8Hk9cQ)

HTTP on port 80 correctly 301-redirects to HTTPS, so the edge knows the hostname — but HTTPS content is not bound to the service.

The native service domain https://fisiocriotibur-production.up.railway.app serves the exact same deployment perfectly (HTTP 200).

I already tried: delete + recreate the custom domain (previous target was 0q3cvgcs.up.railway.app, identical failure), forced certificate issuance, and redeployed the service. No change. This looks like a stale/missing edge binding for this custom domain. Can you please re-bind it at the edge? Thanks!