My custom domain www.bidarch.com returns HTTP 404 with x-railway-fallback: true, although the control plane reports everything healthy:

• DNS: www.bidarch.com -> wy3ox1c4.up.railway.app, currentValue == requiredValue, status PROPAGATED.
• Certificate: VALID (Let's Encrypt), edge serves a valid CN=www.bidarch.com cert.
• Binding: correct serviceId + environmentId, targetPort 3000 — identical to the working service domain frontend-production-03c6.up.railway.app (returns HTTP 200). The app is healthy; only the custom-domain host is not routed by the edge.
• Already tried: delete + re-add the custom domain (got a new target + new edge node each time), manually issue the certificate, customDomainUpdate (reset targetPort), redeploy the service. The fallback 404 persists on every edge node.

Even when currentValue == requiredValue and status is PROPAGATED / cert VALID / syncStatus ACTIVE, the edge still returns the fallback 404 — so DNS is not the deciding factor; the route never reaches the edge. This looks identical to another open Station ticket (webgen.emiko.io, a Next.js app) with the same x-railway-fallback behavior unresolved for several days — likely a control-plane -> data-plane (hikari) sync issue.

Please clear / re-sync the edge routing for this host, or tell me what is preventing the route from propagating to the edge.

Project ID: 5d585812-f5f0-431c-926c-e5454e6be149

Frontend service ID: 8b3ffcfc-b5eb-487e-a753-e9dfc566b559

Custom domain ID: 7e7ab41a-8690-4817-9f5d-c744cfa0cea2

Environment ID: 47c91da1-495f-4c1a-a0fe-d2951ffcbf0c

Example request-id: qOxx_cxGT--Kvf8clt7tkg | edge cdg1 | trace cdg1.e9jw