railway private-network status and update commands
Introduced 2026-06-19 · score 0.95
HOW TO USE IT
When you need to inspect or rename a service’s private networking endpoint, run `railway private-network status` or `railway private-network update <name>`. Supply project, environment, service, or network selectors as needed; `<name>` is the short endpoint prefix without `.internal`.
railway private-network statusrailway private-network status --service <service> --network <name-or-id> --jsonrailway private-network update <name> --service <service>WHY THIS HELPS
Inspect or rename a service's private networking endpoint from the CLI.
REQUIREMENTS AND LIMITATIONS
- Version: v5.17.0
- --service: Service name or ID; defaults to the linked service.
- --environment: Environment; defaults to the linked environment.
- --project: Project ID; defaults to the linked project.
- --network: Private network name, ID, or DNS name.
- --json: Output in JSON format.
- <name> (required): Endpoint name prefix, without the `.internal` suffix.
- Prerequisite: Authenticate with a Railway account using `railway login`; for CI, use `RAILWAY_TOKEN` for project-level actions.
- Prerequisite: Use an installed Railway CLI. The docs list Homebrew, npm, Scoop, binaries, and installer options; npm requires Node.js 16 or higher.
- The status command reports networking for the selected project, environment, and service.
- The update command takes the endpoint short name; full `.internal` hostnames are rejected, and only the short prefix is accepted.
- The update command validates malformed and reserved names and checks name availability before renaming.
FIRST-PARTY EVIDENCE
- https://github.com/railwayapp/cli/releases/tag/v5.17.0
- https://github.com/railwayapp/cli/pull/977
- https://raw.githubusercontent.com/railwayapp/cli/v5.17.0/src/commands/private_network.rs
- https://github.com/railwayapp/docs/blob/main/content/docs/cli.md
Check the installed version and the source before using it. Entry JSON