Apologies for the trouble. We had an incident earlier today affecting deployments across all regions due to a Google Cloud infrastructure issue, which has since been resolved. The backend errors during that window could have caused the 404s you saw on upload. Please try railway up again now, and you can see the full timeline here: status.railway.com/incident/VVL3A03V.

Thanks for checking! Unfortunately, still getting the exact same error after retrying:

Indexing...

Uploading...

Failed to upload code with status code 404 Not Found

I also re-checked the service state, and it's unchanged from before:

• railway status → Linked service: None
• railway service list --json → returns empty []
• railway service link "trustworthy-gentleness" → "Service not found"

Could someone confirm specifically whether service ID 03659ca6-5e2f-4c9f-b828-a62dc73ff9e5 is in a healthy state on your end? It seems like this particular service might still be stuck, even if the broader incident is resolved.

To correct our earlier message, this does not appear related to the deployment incident. The project and service IDs you provided cannot be reached from the account this thread is tied to, which explains the 404 on upload and the "Service not found" errors from the CLI. If those resources live under a different account or workspace, you would need to run railway up while authenticated against that account.

Update: I was posting as Anonymous before and wasn't aware Central Station uses a separate session from the main dashboard. I'm now properly logged in (estebanviquez45-rgb / estebanviquez45@gmail.com). Could you please re-check the status of these resources now that the thread is tied to my actual account?

Project ID: b50361a5-2276-451d-9263-d1d4e68959fd (dynamic-fire)

Service ID: 03659ca6-5e2f-4c9f-b828-a62dc73ff9e5 (trustworthy-gentleness

The project you named resolves to a workspace under a different account than the one this thread is now tied to. Your current account's workspace has no services or projects matching those IDs, which is why railway up returns 404 and railway service list comes back empty. The CLI commands and deployments for that project need to be run while authenticated against the account that owns it.

Update: I was posting as Anonymous before and wasn't aware Central Station uses a separate session from the main dashboard. I'm now properly logged in (estebanviquez45-rgb / estebanviquez45@gmail.com). Could you please re-check the status of these resources now that the thread is tied to my actual account?

Project ID: b50361a5-2276-451d-9263-d1d4e68959fd (dynamic-fire)

Service ID: 03659ca6-5e2f-4c9f-b828-a62dc73ff9e5 (trustworthy-gentleness

We re-checked with your now-authenticated account and the result is the same: that project resolves to a workspace under a different account than this one. Your current workspace has no services or projects matching those IDs, which is why the CLI returns 404 and empty service lists. The CLI commands and deployments for that project need to be run while authenticated against the account that owns it.

You can run railway whoami to check the account name and email authenticated with the CLI, Then compare it with the account on the web dashboard that has the workspace of the project