Network Behavior & Troubleshooting

Networking Behavior by Server State

State Network Access Public IP Status SSH / RDP / HTTP / API Access Notes
Running Full network communication Available Accessible (depends on whether services are started) Server is up; all services running normally
Terminated Network resources destroyed Released Completely inaccessible Server deleted; all resources unrecoverable
Queued / Provisioning Network not yet initialized Not ready Not accessible Server is being created or initialized

Common Networking Issues

Issue Common Causes
Cannot SSH (Linux) Wrong Public IP, SSH service not started, or the OS firewall is blocking port 22.
Cannot RDP (Windows) Wrong Public IP, RDP service not started, or the OS firewall is blocking port 3389.
API / Web Service Not Accessible Service is bound only to 127.0.0.1 (localhost), incorrect port configuration, OS firewall blocking access, or the service is not running.
Port Blocked The following TCP ports are blocked by default at the platform level: 135-139, 427, 445, 593, 1024-1030, 1080, 1363-1377, 3128, 8888, 9999, 5985, 389, 4444, 3333, 14444, 33333, 2222, 22222. Most AI workloads (FastAPI, vLLM, TGI, ComfyUI, etc.) are not affected. If your application uses a blocked port, switch to an open port such as 8000, 8080, or 5000.

PTR (Reverse DNS)

PTR records are supported for most IPs. The following IP ranges do not currently support PTR:

77.xxx.xxx.xxx, 93.xxx.xxx.xxx, 83.xxx.xxx.xxx, 155.xxx.xxx.xxx, 38.xxx.xxx.xxx

To set up a PTR record, provide the target domain, and our technical team will assist with configuration.

Bandwidth

All servers provide unmetered network bandwidth. 100 Mbps / 500 Mbps refers to the port speed, not a monthly traffic cap. There is no per-GB billing.