After renaming my project today and adding a couple of custom domains to

two services, the Railway edge returns 404 "Application not found" with

x-railway-fallback: true on the custom domains. Hitting the Railway-

generated bridge hostname directly returns the same 404, so the issue is

not DNS/cert — looks like the edge router has no service mapping for the

bridge hostnames.

- Custom domains: hit the bridge hostname x.up.railway.app shown in the

domain dialog — 404 "Application not found" with x-railway-fallback: true

- Same services via their Railway-provided default domains: 200, everything

serves fine

- DNS verified correct at the authoritative nameserver

Already tried:

- removing + re-adding the custom domain (got a new bridge hostname,

updated DNS accordingly — new bridge also 404)

- regenerating the default Railway domains (new ones work, custom ones

still 404)

- redeploying both services multiple times

- waiting ~60 minutes

Most likely trigger was a project rename earlier today (edit: yes, the

renamed project is the one showing this problem).

I can share project ID, service IDs, affected bridge hostnames, and

Fastly request IDs by DM — they're logged-in-account specific, don't

want them in a public post. Could someone from staff take a look?

Thanks.