ccount: stephanostrander@gmail.com

Affected domains:

• execdb.xeroshoes.com — project xs-exec-dashboard

(c2a28493-7134-4200-b876-877ab7097afb), env

71ecb30f-466c-46f3-9af0-2b18bb7cb696, CNAME target

5tg5v0up.up.railway.app

• survey.xeroshoes.com — project xs-culture-survey

(d075ee77-d4a1-4e1f-a1ce-5b7460a5fac0), env

c27aea38-d8a0-4148-ba97-c79e988289b9, CNAME target

xe0emkvt.up.railway.app

Problem: Both have been stuck at certificateStatus =

CERTIFICATE_STATUS_TYPE_ISSUING for 40+ minutes with no

progress. DNS is fully correct, propagated, and already

accepted by Railway — only Let's Encrypt issuance isn't

completing. Both domains return HTTP 404 with

x-railway-fallback: true and serve the default

*.up.railway.app cert.

Verified (DNS is not the issue):

• CNAME reports DNS_RECORD_STATUS_PROPAGATED, requiredValue

== currentValue (per your API) for both.

• Ownership TXT (_railway-verify.*) accepted — Railway no

longer lists it as required, so verification passed.

• DNS identical across Cloudflare/Google/Quad9 +

authoritative NS.

• No CAA records on xeroshoes.com (LE not blocked); records

are DNS-only/not proxied.

• Sibling domain on the same zone, financeops.xeroshoes.com,

issued fine.

Not done on purpose: We have not deleted/re-added the

domains, to avoid LE rate limits.

Ask: Please retry/force cert issuance for these two, or

advise if there's an LE rate-limit / internal issuance error

blocking them.