Hi Railway team,

Our two custom domains have been stuck without SSL certificates for 8+ hours. DNS is fully propagated and Railway's own DNS cache is showing the correct CNAME values, but certs are not being provisioned.

**Project:** monday-pilates / mpc-os

**Project ID:** c75e29cd-0d09-4a22-9348-ba7eb5132996

**Environment ID:** ca1e6229-c25e-42fd-9101-26ff15ff6120

**Plan:** Hobby

**Domain 1 — admin.monday-pilates.club**

- Custom domain ID: 62c1628c-bf4c-4935-aaae-1ff106a1c85d

- Railway CNAME target: ly2imifw.up.railway.app

- DNS status: CNAME verified (Railway cache matches)

- SSL status: still serving *.up.railway.app wildcard — no domain cert

**Domain 2 — staff.monday-pilates.club**

- Custom domain ID: 1b276ecd-8675-4e66-a0ad-b836ba09207c

- Railway CNAME target: d2ezm2nn.up.railway.app

- DNS status: CNAME verified (Railway cache matches)

- SSL status: still serving *.up.railway.app wildcard — no domain cert

**What we've tried:**

- Deleted and recreated both domains (fresh DNS records)

- Ran customDomainUpdate mutation repeatedly via GraphQL API to force cache refresh

- Confirmed DNS propagation via Google (8.8.8.8) and Cloudflare (1.1.1.1)

- Redeployed both services multiple times

- Waited 8+ hours total — still no cert

The Railway dashboard says DNS is verified but SSL is not provisioned. Services work fine on *.up.railway.app internal URLs. Could you please kick the SSL provisioner for these two domains?

Thank you!