Port 2102: Zephyr — The notification system that invented the ping

Port 2102 carries Zephyr, a real-time notification and messaging protocol developed at MIT in the late 1980s. IANA registers this port as zephyr-srv — the primary Zephyr server port.

Most people have never heard of Zephyr. But every time someone sends you a notification, a ping, an instant message, they're doing something Zephyr figured out first.

What Zephyr Is

Zephyr is a publish-subscribe notification system. Users subscribe to classes (topics). When someone sends a message to a class, every subscriber gets notified instantly — across the network, in real time, whether they're on the same machine or a different one entirely.

It supported direct messages, group channels, and presence detection. It knew who was logged in and where. It delivered messages that said "you have mail," "someone wants to talk," or anything else a system or human wanted to broadcast.

In 1987, this was remarkable. The Internet existed, but it was a quieter place. Nobody was pushing notifications to your screen. Zephyr changed that.

How the Port System Works for Zephyr

Zephyr uses a cluster of adjacent ports:

Port 2102 is the front door. Messages sent to a Zephyr server arrive here first.

The protocol runs over UDP — fast, connectionless, appropriate for notifications that don't need a persistent channel. A notification fires off, the server receives it on 2102, and routes it to whoever is subscribed.

The MIT Project Athena Story

Zephyr was built by a team at MIT as part of Project Athena — a joint initiative between MIT, Digital Equipment Corporation, and IBM that ran through the 1980s.² Athena's goal was to build a distributed computing environment where students could sit down at any workstation on campus and have access to their files, their environment, their identity.

To make that work, they needed infrastructure that didn't exist yet. So they built it. Athena gave the world the X Window System (still the foundation of Linux desktop graphics), Kerberos (still the dominant network authentication protocol), and Zephyr.

The Zephyr Development Team — Mark Eichin, Robert French, David Jedlinsky, John Kohl, William Sommerfeld — wrote the initial codebase in the late 1980s. They were solving a real problem: how do you notify people in real time when they're scattered across hundreds of workstations?

Their answer: a server on port 2102, a protocol over UDP, and a subscription model that would look completely familiar to anyone who's used Slack.

Current Status

Zephyr is still running. Not everywhere — at most universities it was displaced by XMPP, then by proprietary services. But MIT, Carnegie Mellon, Brown, and a few others still operate Zephyr servers.³ There are users who have been on Zephyr continuously since the 1990s.

The protocol itself is frozen in amber. No one is extending it. But the concept it pioneered — subscribe to a topic, receive notifications when something happens — is now the architecture of almost every messaging platform on Earth.

Checking What's on Port 2102

If you want to see whether anything is listening on this port on your own machine:

# macOS / Linux
sudo lsof -i :2102

# Or with ss (Linux)
ss -tlnp | grep 2102

# Windows
netstat -ano | findstr :2102

On most machines, nothing will be there. Zephyr servers are rare. If you do find something on 2102, it's either a Zephyr installation or something that chose this port because it was available.

Why Unassigned Neighbors Matter

Port 2102 is registered. Its neighbors 2100 and 2101 are not. This is how the registered port range (1024–49151) actually works in practice: blocks of ports get claimed by specific services, leaving gaps between them that applications use opportunistically.⁴

If you write software that needs a port and doesn't want to conflict with known services, you look for those gaps. Port 2100 is one of them. Port 2102 is not — it belongs to a 35-year-old notification system from MIT that almost no one runs but that IANA still formally recognizes.

The gaps and the registrations together form a map of what people were trying to solve, in roughly the order they tried to solve it.