Subject: Custom domain not routed by edge: valid cert + propagated DNS, but 404 x-railway-fallback

Hi Railway team,

The edge cluster never picks up routing for my custom domain, even though the config is correct in Railway's system. Your in-dashboard Agent investigated and exhausted all configuration steps — it concluded this is a "hard edge routing sync failure" that only your team can fix.

Project / service:

• Project: 51619c7d-d77f-4db9-8e01-3d8ae01111fc (sr-dashboard), env production (415680d5-7312-4bd1-9a3a-7deb55a35589)
• Service: f5e70954-7d16-44d9-93a8-29aa5976a470 (TG_Guest-web)
• Custom domain: menu.togathergdansk.pl (id 63f68010-acf2-48bb-a852-f28a901ff909, target port 3000)

Symptom:

• Certificate: VALID (edge serves CN=menu.togathergdansk.pl, issued 2026-07-12 18:32 UTC)
• DNS: CNAME → yaidhp6u.up.railway.app, PROPAGATED
• serviceDomains config: confirmed by the Agent to include the domain with port 3000
• Yet every HTTPS request returns 404 {"message":"Application not found"} with headers x-railway-fallback: true, server: railway-hikari — no routing entry on the edge, for 4+ hours
• Request IDs for your edge logs: fUeGSifhSFSrmsHN6WHkDg, r8wu9N2dRcqn7khD6WHkDg, rwRij2viRleU2YHln6XIxQ
• The railway-provided domain tgguest-web-production.up.railway.app works fine on the same service/port

Already tried (no effect): domain deleted + re-created twice; certificate re-issue; service redeploys including the Agent's fix deployment eb3da230-e8e6-4e64-bae7-51243c0a9d5f (SUCCESS, 2026-07-12 20:59 UTC); ports verified; CAA clean. RAILWAY_PUBLIC_DOMAIN env already resolves to menu.togathergdansk.pl — the variables subsystem sees the domain, the edge doesn't.

Ask: please check edge routing logs for the request IDs above and manually sync/purge/rebuild the edge routing entry for menu.togathergdansk.pl. Also curious why the config never propagated to the edge on deployment.

Thanks!