railway outbound-network manages service outbound networking

Introduced 2026-06-24 · score 0.97

HOW TO USE IT

When managing a Railway service’s outbound networking, use `railway outbound-network` with the relevant status or enable/disable subcommand and service selectors as needed. Redeploy after static IP changes; apply staged environment changes after IPv6 changes.

WHY THIS HELPS

Manage a Railway service’s outbound networking from the CLI while maintaining or debugging its deployment configuration.

REQUIREMENTS AND LIMITATIONS

• Version: v5.21.0
• -s, --service <SERVICE>: Service name or ID; defaults to the linked service.
• -e, --environment <ENVIRONMENT>: Environment to use; defaults to the linked environment.
• -p, --project <PROJECT_ID>: Project ID to use; defaults to the linked project.
• --json: Output in JSON format.
• static-ip subcommand (required): Choose `status`, `enable`, or `disable` to inspect or change Static Outbound IPs.
• ipv6 subcommand (required): Choose `status`, `enable`, or `disable` to inspect or stage an Outbound IPv6 change.
• Static IP enable and disable report that a redeploy is required before outbound traffic changes.
• Static Outbound IP status reports whether enabled, whether the returned assignment is high availability, and assigned IPv4 addresses.
• The CLI contract does not expose a legacy/single-IP mode.
• Outbound IPv6 commands stage an environment config patch for `deploy.ipv6E

FIRST-PARTY EVIDENCE

• https://github.com/railwayapp/cli/releases/tag/v5.21.0
• https://github.com/railwayapp/cli/pull/984
• https://github.com/railwayapp/docs/blob/main/content/docs/cli/outbound-network.md
• https://raw.githubusercontent.com/railwayapp/cli/v5.21.0/src/commands/outbound_networking.rs

Check the installed version and the source before using it. Entry JSON

Report a problem with this card