Hey Railway team,

I'm trying to go live today and I'm stuck on the very last step. My two custom domains

have been sitting on "Verified: no" with the certificate stuck on "Issuing" for about

3 hours now — and I've triple-checked the DNS, it's all correct and already resolving to

your edge on every public resolver I try. My best guess is your verifier is holding onto an

old/cached DNS lookup from before I set things up (I moved the whole domain to new

nameservers earlier today). Could you please give it a nudge from your side and force the

re-verification + certificate? I'd really appreciate it.

Here's everything you might need:

Project: 50pick (5e87353c-1d59-433d-a683-a32b9149f74c)

Environment: production

Service: 50pick (baba8802-7f79-4306-9706-1e19a4b95e7c), US-West

A 404 page I hit showed Reference ID: rj7opBEDTVK1z1dxCYBc-A

The two domains (both Active, both Verified: no, cert Issuing):

• 50pick.tz — expects CNAME @ → g31rs69a.up.railway.app

                    + TXT _railway-verify = railway-verify=5a2ae218422d38d9c358ffaa0e6e559cb1244d1daebe2e8af197a05b461cdd13

• www.50pick.tz — expects CNAME www → ss3egn8f.up.railway.app

                    + TXT _railway-verify.www = railway-verify=b159edaa5b8003bc7267e79f780838a320f9d186ad733a1aa3d049d10bf2306c

What I've already confirmed from my side (checked on both 1.1.1.1 and 8.8.8.8):

• Nameservers now point to Cloudflare (ollie/yadiel.ns.cloudflare.com), zone is active, DNSSEC off

• 50pick.tz → 69.46.46.49 and www.50pick.tz → 69.46.46.51 (your edge)

• Both _railway-verify TXT records resolve and match exactly what the dashboard asks for

I tried "certificate retry" in the CLI but it says it's only available after a failure, and

mine is still "Issuing" — so I can't nudge it myself. Anything you can do to push it through

would make my day. Thank you so much!