Railway Status

When to Use

• User asks about Railway status, project, services, or deployments
• User mentions deploying or pushing to Railway
• Before any Railway operation (deploy, update service, add variables)
• User asks about environments or domains

When NOT to Use

• Detailed service configuration (builder type, dockerfile path, build command, root directory)
• Deploy config (start command, restart policy, healthchecks, predeploy command)
• Service source (repo, branch, image)
• Compare service configs
• Query or change environment variables

Check Status

railway status --json

command -v railway

Handling Errors

CLI Not Installed

command -v railway

Railway CLI is not installed. Install with:

npm install -g @railway/cli

or

brew install railway

Then authenticate:

railway login

Not Authenticated

railway whoami

Not logged in to Railway. Run:

railway login

No Project Linked

No Railway project linked to this directory.

To link an existing project:

railway link

To create a new project:

railway init

Presenting Status

• Project: name and workspace
• Environment: current environment (production, staging, etc.)
• Services: list with deployment status
• Active Deployments: any in-progress deployments (from

  activeDeployments

  field)
• Domains: any configured domains

Project: my-app (workspace: my-team)
Environment: production

Services:
- web: deployed (https://my-app.up.railway.app)
- api: deploying (build in progress)
- postgres: running

activeDeployments