Custom domain stuck in VALIDATING_OWNERSHIP for 18+ hours with no error reported

Question

Project: Spine - Sito Web (beefd873-30b9-480f-93d4-80acd9307007)

Service: sito (f0111ea4-45f5-4c14-a6d5-eb04e8367ad6)

Environment: production (10c44b44-65ff-406b-b1db-2081e3dfcd2e)

Domain: www.studiospine.it -> bdnnhm48.up.railway.app

Workspace plan: PRO

PROBLEM

`certificateStatus` has been `CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP` since 2026-08-05 18:12 UTC. `certificateErrorMessage` is empty. HTTPS on the domain is unusable: the edge still serves the wildcard `*.up.railway.app` certificate, so browsers reject the connection.

WHAT WE VERIFIED ON OUR SIDE (all correct)

• CNAME www.studiospine.it -> bdnnhm48.up.railway.app, confirmed at the authoritative GoDaddy nameservers (ns81/ns82.domaincontrol.com) and at 8.8.8.8, 1.1.1.1 and 9.9.9.9. Single record, no duplicates.

• Your own API reports dnsRecords status = PROPAGATED with currentValue == requiredValue.

• bdnnhm48.up.railway.app and www.studiospine.it both resolve to 69.46.46.98.

• Ports 80 and 443 are reachable on the domain.

• http://www.studiospine.it/.well-known/acme-challenge/ (any token) is answered by "Server: railway-edge" with a 404. Traffic reaches your edge; nothing in front intercepts it. The apex uses GoDaddy 301 forwarding, but www points directly at Railway and is not proxied.

• No CAA records at www.studiospine.it, studiospine.it, or the .it level.

• DNSSEC is not enabled on the zone.

• Domain is ACTIVE at the registry (registered 2026-08-05, expires 2027-08-05).

• Only one service and one environment in the project; no leftover custom domain entries.

WHAT WE ALREADY TRIED

1) Waited 2+ hours after the DNS change.

2) Deleted and re-created the custom domain. This changed the target from 1qpl7qjb.up.railway.app to bdnnhm48.up.railway.app and required a second DNS change on our side, which we made and verified.

3) Redeployed the service.

4) Called the customDomainIssueCertificate mutation via the public API. It returns {"data":{"customDomainIssueCertificate":true}} but the status does not change and no certificate is issued.

5) Waited several more hours after each of the above.

REQUEST

Please check why ACME issuance is not progressing for this domain. Since the mutation reports success but nothing happens, it looks like the issuance job is not being picked up on your side rather than failing validation.