Every few years, someone announces the death of TCP in the data center. This time the announcement is aimed squarely at AI clusters, it comes from a person with the track record to be taken seriously, and — unlike most protocol proposals — it shipped as a working Linux kernel module you can install today without a reboot. John Ousterhout, Stanford professor emeritus and the person behind Raft, Tcl/Tk, and a shelf of distributed-systems papers, is now, in his own words, on a "life's mission" to replace TCP for data-center RPC with a protocol called Homa.

The why-now is real and checkable. His talk "Homa: The End of TCP for AI Clusters" landed at the AI Engineer World's Fair on September 17, 2026; The Register covered the campaign on October 1; the Hacker News thread ran October 4; and the Internet-Draft text in the homa-rfc repository was revised on October 3, 2026 to track the current implementation. The kernel module itself was pushed to the day we wrote this. This is not a dormant research artifact.

But "actively developed" and "you should run this in your GPU fleet" are different claims. This piece separates the two: what the protocol actually does, what the benchmark numbers do and do not establish, what is genuinely shipping versus what is still a README promise, what the GPU idle time behind TCP tail latency costs at 2026 prices, and — because no pattern is universally good — exactly when you should skip Homa entirely.

The Problem Is Real, Even If the Pitch Oversells It

The failure mode Ousterhout is attacking is not controversial. It is incast: several machines sending to one destination at once, overwhelming the last hop. If three incoming links each run at line rate toward a receiver whose single downlink drains at one line rate, packets queue up at the top-of-rack switch's egress queue. A tiny latency-sensitive message heading to that same receiver joins the back of that queue. Its own transmission time is microseconds; its wait time is dominated by the backlog in front of it.

  bulk sender A ───┐
                  │    ToR switch egress queue          receiver
  bulk sender B ───┼──► [ 40+ queued MTUs, low prio ] ──► downlink
                  │         ^                          (1x line rate)
  bulk sender C ───┘         │
                             │ trapped here behind bulk traffic
  short msg (KV probe) ──────┘   <- the message your GPU is waiting on