Port 10150 — Unassigned, Borrowed by GPU Workers

What Port 10150 Is

Port 10150 is unassigned—there is no official IANA service designation for it. It lives in the registered port range (1024–49151), which means it's available for use by applications that need it, but nobody owns it globally.

Port Ranges Explained

The Internet Port system divides ports into three bands:

• Well-Known Ports (0–1023) — Reserved for system services. SSH is 22, HTTP is 80, HTTPS is 443. IANA assigns these carefully. They're the public telephone numbers of the Internet.
• Registered Ports (1024–49151) — Available for service assignment. Software vendors can register their services here. Port 10150 sits in this middle ground—open but structured.
• Dynamic/Ephemeral Ports (49152–65535) — Temporary scratch space. When your client connects to a server, it uses an ephemeral port automatically. These numbers are never reused while a connection exists.

Port 10150 belongs to the registered band, but nobody has claimed it at IANA.

What Actually Uses Port 10150

GPUStack uses port 10150 as its default worker port. ¹ GPUStack is an AI inference orchestration platform—it distributes large language model inference across GPU nodes. When you run a GPUStack worker, it listens on 0.0.0.0:10150 by default, waiting for the controller to send requests.

This is the most documented use of the port. You won't find it in IANA's official registry, but if you're running GPU workload distribution, this port has become the understood standard.

How to Check What's Listening

To see what's actually running on port 10150 on your system:

Linux/macOS:

# See what process is listening
sudo lsof -i :10150

# Or with netstat
sudo netstat -tlnp | grep 10150

# Or modern systemd systems
sudo ss -tlnp | grep 10150

Windows:

netstat -ano | findstr :10150

The output will tell you the process ID and application name. From there, you can investigate further.

Why Unassigned Ports Matter

The fact that 10150 remains unassigned reveals something important: the registered port range works because teams don't ask permission, they just pick numbers and build. GPUStack chose 10150 because it was available, documented that choice, and now thousands of machines run that protocol on that port without any central coordination.

This is why the port system hasn't collapsed under the weight of 65,535 possible addresses. Not because IANA controls everything, but because they control the top tier (well-known ports), and the middle tiers self-organize through documentation and convention.

If you find port 10150 open on a machine and don't recognize it, assume it's either GPUStack or a service configured to mimic GPUStack's choice. Check your running processes. The port won't tell you—the process will.