Project ID: b74ef3b4-071c-4680-9fb9-d856fa6f26e2

Environment ID: a8346d6e-9fce-4187-a921-8ab0b9e8bf38

Service ID: 7727849b-3573-46d4-bb0e-2632f9ff7633

railway up has been failing consistently for several attempts today with:

error sending request for url (https://backboard.railway.com/project/.../environment/.../up?serviceId=...)

Caused by:

0: client error (SendRequest)

1: connection error

2: An existing connection was forcibly closed by the remote host. (os error 10054)

The dashboard shows a corresponding failed deployment: "Deployment failed during initialization process" → "Initialization > Snapshot code" → "Failed to create code snapshot. Please review your last commit, or try again." Build never starts. The built-in Diagnosis tool couldn't identify a cause either.

I've already ruled out the usual suspects on my end:

• Upload size: with --verbose, the actual compressed payload is only 8,446,610 bytes (~8MB) — well under any known limit.
• Network path: identical failure from both my regular network and a separate mobile hotspot.
• .railwayignore: confirmed no BOM issue, node_modules/.next/.git properly excluded.
• Local code: builds and type-checks cleanly.

The existing production deployment (railway up, successful, currently Online/ACTIVE) is unaffected. Could you check the backend logs around this service/environment for these snapshot-creation failures? Happy to provide the exact timestamps of each failed attempt if useful.