Hi Railway team,

Custom domains in my project are not routing to my services. They return a Railway edge fallback 404 even though the TLS certificate is VALID and the DNS records are correct and propagated. I believe the domains are stuck/claimed from a previously deleted project and the edge routing table was never updated.

Project / services

Project: TRX — 481ab9b7-c880-43ae-8e45-758ddd7c48fc

Environment: production — a8cb5cc2-e660-4a08-9671-1bd606f954f2

Service web (Next.js) — 0fba9299-e97c-4783-a19b-13a21dd6efb0

public service domain (WORKS): web2-production-fce4.up.railway.app

Service TRX-api (FastAPI) — cfcc5b42-694d-45ba-ab79-00817c3381d4

public service domain (WORKS): trx-api-production-f1fd.up.railway.app

Custom domains affected

Domain Service Required CNAME target

overtron.io web ga2d7ti0.up.railway.app

www.overtron.io web hjb0mox3.up.railway.app

admin.overtron.io web 1wxtb2r2.up.railway.app

api.overtron.io TRX-api a7r0tfyl.up.railway.app

Evidence it is an edge-routing problem (not DNS, not cert)

admin.overtron.io has cert status VALID and DNS status PROPAGATED in the Railway dashboard, the CNAME resolves correctly, yet HTTPS returns a Railway fallback 404:

$ curl -v https://admin.overtron.io/admin/overview

• Trying 69.46.46.13:443...
• Connected to admin.overtron.io (69.46.46.13)

< HTTP/2 404

< server: railway-hikari

< x-railway-fallback: true

< x-railway-request-id: cuQksf3dRLKjAZSInbOCzg

< content-type: application/json

The same path on the service's own railway.app domain works (HTTP 200):

$ curl -o /dev/null -w "%{http_code}" https://web2-production-fce4.up.railway.app/admin/overview

200

DNS resolution is correct:

$ dig +short admin.overtron.io

1wxtb2r2.up.railway.app.

69.46.46.13

What I already tried (no effect)

Deleted and re-created the custom domains (twice)

Re-issued the certificate (customDomainIssueCertificate) → cert became VALID

Redeployed both services after adding the domains

Set targetPort explicitly on the custom domains

Confirmed there is only one environment (production) and one active SUCCESS deployment per service

The x-railway-fallback: true header on a domain with a valid cert strongly suggests the edge routing entry for these hostnames is missing or still points to a deleted project/service.

Background

This project was re-created after a previous TRX project was deleted. The domains overtron.io / www / admin / api were attached to the old (now deleted) project before. I suspect the global domain claim from the deleted project was never released, so the new project's edge registration silently fails.

Request

Please release/clear the stuck domain claims for overtron.io, www.overtron.io, admin.overtron.io, api.overtron.io and re-register them against the current services above, or tell me what I need to do to force a clean re-registration.

Thanks!