Hello Railway Support,

my Railway-generated domain returns an edge fallback 404 even though the service is active and healthy.

Service: Schimmern-Heilung

Domain: schimmern-heilen-production.up.railway.app

Target port: 8080

Uvicorn is running successfully on:

0.0.0.0:8080

Debug request:

GET /health?test=9999

Response:

HTTP/1.1 404 Not Found

server: railway-hikari

x-railway-fallback: true

x-railway-request-id: b_s-t98QTgySPlOR55So4g

x-railway-upstream-zone: railway/europe-west4-drams3a

Response body:

{"status":"error","code":404,"message":"Application not found"}

The request does not appear in the Uvicorn logs, confirming that it never reaches the application.

I have already:

• verified that the active deployment is healthy;
• verified that Uvicorn listens on 0.0.0.0:8080;
• verified that the domain target port is 8080;
• deleted and regenerated the Railway-generated domain;
• assigned target port 8080 again;
• restarted and redeployed the service.

The problem remains unchanged.

Please inspect the Hikari hostname-to-deployment mapping for this Railway-generated domain and manually re-publish, re-sync, purge, or rebuild the edge route.

Please do not redirect this to application-level debugging. The response is generated by Railway's edge fallback, and the request never reaches Uvicorn.

Thank you.