Project: adgenixlab (workspace "Adgenix Lab", Pro plan) — the web service that serves adgenixlab.com, production environment. Domains created via the Public API using the service/environment/project IDs injected into the deployment.

Domains affected: americanhomecenter.org and www.americanhomecenter.org

Symptom: customDomainCreate succeeds, the Let's Encrypt certificate issues and serves correctly via SNI, the API reports syncStatus: ACTIVE and targetPort: 8080 (same port as our working domain), and DNS is verified correct at the per-domain targets (authoritative + 8.8.8.8 + 1.1.1.1). But every HTTPS request to the hostname returns 404 {"status":"error","code":404,"message":"Application not found"} with server: railway-hikari, x-railway-fallback: true (observed x-railway-edge: mia1) — including when pinned via --resolve to the edge IP that serves our working domain.

Control: adgenixlab.com on the same service serves HTTP 200 through the same hikari/mia1 edge (request id trqnTbX8Tm2S9X24woOzXw).

Reproduced on 4 consecutive registrations (delete + recreate via API, apex targets in order): 2aezreb5 → 4u9kewv8 → lzuq08lp → 0lp46863 .up.railway.app (www: 54rbzl3n, 8tq52i40, …). Every one: certificate issued, route never provisioned — the first was left ~2 hours.

Timeline (UTC): Jul 7 ~22:10 first registration; 22:51:29 first cert notBefore; Jul 8 00:49 hikari 404 confirmed while API reported ACTIVE; re-registrations ~00:52, ~01:40, ~02:10 — identical result each time.

Failing request IDs: Qx5rVqPOSLe8cCJ0FFmdQQ, _FZJFv4aSTuNNec0aP71AA, E5WPfgIHThOCvk9wwoOzXw, vLfyrdBaSDWCVQ-ZCYBc-A, uR28lMnHRhWVgH5JxtoGcA, JhBpMTBfSKmPDyLmyCLmYg, kInI3I-wQAybC1YNU79b0g, rIYDGrn5QpGaIb_s8u2xcg

Why do custom-domain edge routes for this service never provision despite ACTIVE status, and can you push/repair the hikari config for these hostnames? We've now consumed 4 of 5 weekly LE duplicate-certificate slots, so we've stopped re-registering on our side.