Our custom domain ribits.swampsage.com returns Railway’s “Application not found” 404 and serves the default Railway certificate.

Service: ribits-preview

Project ID: 6d6151cc-43d8-4653-9748-0400961add28

Custom domain ID: d4e9688f-9194-4b39-89ca-79279327635a

DNS was configured November 7 at approximately 8 p.m. Eastern. Both records match Railway’s requirements and are publicly resolvable:

• CNAME ribits → 4hrfeh8v.up.railway.app
• TXT _railway-verify.ribits → railway-verify=75c2fb9f1973163d7becd802a266d0e8cb87111c7566e63c213aa98033efafc2

Railway’s API reports:

• DNS status: DNS_RECORD_STATUS_PROPAGATED
• Ownership verified: false
• Certificate status: CERTIFICATE_STATUS_TYPE_ISSUING
• No certificate error message

The default URL works: https://ribits-preview-production.up.railway.app/

The custom domain was added weeks before the DNS records were configured. Could you investigate whether ownership verification is stalled and restart verification/certificate provisioning if necessary?

I’m aware of incident QBCLHG1V. Could it also affect domain ownership verification or certificate issuance? Our default Railway URL works, but the custom domain remains unverified despite matching public DNS records.