Port 1809: Oracle-VP1 — Registered, Unexplained

Port 1809 sits in the registered port range with an official assignment and almost no explanation. IANA lists it as Oracle-VP1, assigned to both TCP and UDP, with a contact name at Oracle. Beyond that: silence. No RFC. No public documentation. No Oracle support article explaining what VP1 stands for or what it does.

It is a named ghost.

The Registered Port Range

Port 1809 falls in the registered ports range: 1024 through 49151. This range is governed by IANA, the organization that assigns port numbers to services so that applications can find each other reliably. When a vendor registers a port, they're claiming a consistent meeting point: "my software will be here."

Unlike the well-known ports below 1024 (HTTP at 80, SSH at 22, HTTPS at 443) — which are famous enough to be common knowledge — the registered range is where enterprise software, middleware, and specialized protocols live. Most of these ports are unknown to anyone who doesn't use the specific product they belong to.

Oracle-VP1

The IANA registry lists port 1809 as oracle-vp1, with Oracle's Craig Fowler as the registered contact.¹ The "VP1" label doesn't match any publicly documented Oracle product or protocol. The closest candidates — Oracle Virtual Private Database (VPD), Oracle's various listener configurations — don't cleanly map to this designation.

This happens more often than you'd expect. A vendor registers a port during product development, the product ships internally or gets discontinued or gets absorbed into a larger system, and the registration outlives any public trace of what it was for. The port number persists in the registry long after the context that created it has vanished.

If you're seeing traffic on port 1809, it's almost certainly Oracle software of some kind — but which product, in which configuration, isn't something the public record can tell you.

How to Check What's Listening

If port 1809 is active on a machine you manage, these commands will tell you what's using it:

Linux/macOS:

# Show process listening on port 1809
sudo ss -tlnp sport = :1809

# Or with lsof
sudo lsof -i :1809

Windows:

netstat -ano | findstr :1809

The output will show the process ID. From there, your process manager (Task Manager on Windows, ps on Linux/macOS) will tell you what application owns it.

Why Unassigned-in-Practice Ports Matter

The registered port range contains thousands of entries. Many are actively used by software that millions of people run every day. Some are relics — registered once, never documented publicly, and now just occupying a number that nobody else can claim.

This matters because port numbers are how operating systems and firewalls make routing decisions. A port that carries real traffic needs to be open; a port that carries no traffic but is listed as "Oracle-VP1" still raises questions when it appears in firewall logs or security scans. You have to investigate either way.

The gap between "officially registered" and "publicly documented" is one of the quiet realities of how the port namespace actually works.