Networking: SSH, open ports and outbound rules

Connecting

ssh -p <port> root@<instance-name>.<domain>

The console fills in the port and hostname for your instance. The traffic reaches your machine through fixed port forwarding, so the port stays the same for as long as the machine is yours.

Service ports

Each machine has ten extra ports you can use to serve something to the internet, such as a Jupyter server or an inference API. The console lists exactly which ports are open for your instance. A service listening on one of those ports inside the container is reachable at the instance hostname on the same port number.

A service on an open port is reachable by anyone who knows the address. Add authentication before you expose anything.

jupyter lab --ip 0.0.0.0 --port <service-port> --no-browser

Outbound traffic

• Outbound connections on port 25 (email) are blocked.
• Outbound traffic is rate-limited per machine so one instance cannot use all of the shared line.
• Instances cannot reach other machines' addresses or the platform's management network.

All instances share one public address for outbound connections, so abuse by one renter affects everyone. We keep per-machine connection records and remove instances that break the terms of service.

Multi-node networkingPlanned

Nodes in a two-node or four-node instance can reach each other over SSH without a password. The machines are cabled with 200G ConnectX-7 links. Whether your container gets direct access to that link is still being validated, and the console will say so for your size.