Security Disclosure Recommendation: Recover Failing Deploys

Author: Mykal Machon

This guide is part of Railway's response to the security disclosure published on October 21, 2026.

During the October 21st security incident, Railway stopped accepting new deployments while the platform was secured. Follow the Railway status page for the latest updates. Now that deployments are accepted again, some services need a manual push to catch up. This guide explains why a deploy may fail during recovery and how to fix each case.

## Why deploys fail during recovery

Commits pushed while Railway was not accepting deployments were not queued. Your service keeps running its last successful deployment until you trigger a new one. Two other recovery steps can also cause failures:

• GitHub connections were revoked during the incident and must be reconnected before Railway can pull from your repository.
• API tokens and CLI sessions were revoked, so manual deploys from your machine or CI fail until you create new credentials.

Work through the sections below in order. Most services only need the first step.

## Reconnect GitHub

Build errors such as "unable to pull repository" or "build could not be started" mean Railway can no longer reach your repository. Reconnect your GitHub account, then retry.

1. Open Account Settings and confirm your GitHub account is connected. Reconnect it if it isn't.
2. Confirm the Railway GitHub App still has access to the repository in your GitHub installation settings.
3. Return to the service, open Settings, and disconnect then reconnect the repository.
4. Open the Command Palette (CMD/CTRL + K) and select Deploy Latest Commit again.

Autodeploy only works when at least one project member has a connected GitHub account with contributor access to the repository. In a team project, the member who originally connected the repository is the one who needs to reconnect. See GitHub autodeploys for more troubleshooting steps

## Recreate credentials for CLI and CI deploys

If your service is not connected to GitHub and you deploy with railway up or from a CI pipeline, your existing credentials were revoked during the incident. Create new ones before deploying.

### Deploy from the CLI

Log out to clear the revoked session, then log in again.

railway logout
railway login

Then link the project and deploy as usual.

railway link
railway up

### Deploy from CI

CI pipelines authenticate with a token in RAILWAY_TOKEN (project token) or RAILWAY_API_TOKEN (account or workspace token). Both were revoked. Create a replacement and update your CI secrets.

1. For a project token, open your project Settings and navigate to Tokens. For an account or workspace token, open the tokens page in your account settings.
2. Create a new token with the same scope as the old one.
3. Replace the old value in your CI provider's secrets.
4. Re-run the pipeline.

See Tokens for the differences between token types.

## Before contacting support

If deploys still fail after reconnecting GitHub and recreating credentials, contact support and include:

• The project, service, and environment.
• The deployment ID of the failed deploy.
• The error shown in the build logs.
• Whether the service deploys from GitHub, the CLI, or CI.