Hello Railway team,

On 2026-09-30 between about 07:35 and 07:40 UTC our production site kattachegirma.uz returned your "Not Found / The train has not arrived at the station" page to real users.

Request ID from the error page: 1C3k4Sv2Thuv_ZrGpHNmDw

Project: 10ee375a-a64b-470b-a42b-aafce14c8679

Service: kattachegirma (ee20567f-3b0e-44c1-8e9f-faefde178b9a)

Environment: production (527ff546-5fdf-403c-8021-e2bc563ae906)

What we see on our side:

• Service HTTP logs stop at 07:34:39.484Z and resume at 07:39:26.033Z, on the same deployment and the same instance (no restart, no redeploy).

• Network flow records continue during the gap.

• The request ID above does not appear in our service HTTP logs.

• Serverless is disabled, the latest invoice is paid, no payment warnings.

• The custom domain is proxied through Cloudflare. We did not change DNS or the service around that time.

Could you please trace this edge request and tell us:

(1) which hostname / route / upstream was selected for it and why it returned Not Found;

(2) whether there was a routing or provisioning incident at that time;

(3) whether any account restriction was involved;

(4) what we can do to prevent this in the future.

Thank you!