Proposal: Adopt the Coffeepot as a Base Unit
A kitchen appliance moved a terabyte in ten days and nothing in the entire stack noticed. We need a unit for that.
Behind the curtain+
The Keurig that moved a terabyte and the speech recognizer that fits in 16.9 MB landed on the same front page, and the gap between them is the whole story. The $5 VPS thread supplied the counterexample: hundreds of people who can recite exactly what their box is doing, standing next to four people whose kitchen was running a port scanner. The illustrator dashboard and the big-arrow tool are the same artifact twice, people hand-building instruments the stack refuses to ship. DeepSeek Flash supplied the far end of the ruler and the memory-pricing fight supplied the proof that the illiteracy runs all the way down.
A metrology submission, because the argument is about units and the form had to be a document that proposes one. The deadpan of a numbered standards proposal lets the arithmetic carry the anger without the prose having to announce it. Derived units are kept flat and brief so they read as definitions rather than exhibits; the weight sits in Rationale and Anticipated Objections, where the sources are dissolved into a single argument rather than given turns.
Submitted for consideration. Status: in earnest.
1. Scope
This document proposes a new base unit of data volume, the Coffeepot (symbol Cp), together with its derived quantities, a measurement procedure, and transitional provisions for existing literature.
The Internet Engineering Task Force has addressed the coffee pot once before, in RFC 2324, and was joking. We note this and proceed.
2. Rationale
On 7 October a man logged into his parents’ router and discovered that their Keurig had moved one terabyte in ten days.
It was not uploading coffee. It was sweeping the local network. Port scans, mDNS probes, a continuous roll call asking the dishwasher and the thermostat and the television to identify themselves, so that the manufacturer could sell the census of the house to people who buy censuses of houses. Ten days of a kitchen appliance taking the names of the other appliances.
The volume is not the scandal. The scandal is the detection.
Nothing in that system noticed. Not the router, which forwarded it. Not the ISP, which carried it. Not the manufacturer, which commissioned it and apparently does not add up its own bills. Not the parents, who own the machine, pay for the line, and were told at setup that they had consented. The sole functioning instrument anywhere in the stack was a son who happened to log in. One terabyte, and the measuring apparatus was a visiting adult child.
Compare the other end of the house. The same week, someone asked what people run on a five-dollar VPS that is worth keeping online around the clock, and five hundred and twenty-eight replies arrived with the answer. Mail and IMAP for a family domain. Authoritative DNS. A rendezvous server for two friends behind NAT. Per-vendor email aliases, so that when bestbuy@example.com starts receiving Russian spam you know precisely who sold you. One man had kept a box running for ten years and wrote a small eulogy when he finally shut it down. These people can tell you the uptime, the transfer, the services, and the month the IP reputation stabilised. They are describing an instrument they built so they could see.
Both of these are the same observation. Hundreds of people who know every byte on a five-dollar box, and four people who could not tell you their kitchen was running a port scanner. The difference is not competence. It is that one group has instruments and the other group was sold an appliance with the gauges removed.
So they build the gauges by hand. This week a man hired a human illustrator to draw his house, and wired the drawing to Home Assistant, so that the lights and the heaters sit where the lights and the heaters actually are and he can look at a picture and know what his home is doing. The same week, a developer shipped a tool whose function is to paint an enormous arrow on your monitor, because when an agent is running on your machine there is no longer any reliable way to see what it is touching, and the state of the art is a six foot arrow. A commissioned painting and a giant arrow. These are not whimsical projects. They are instrumentation, privately funded, because the stack ships none. The parents had no such instrument, which is why the instrument had to be their son.
Oxide has now raised four hundred and forty-five million dollars on roughly this premise, that you should be able to see inside the rack. Deno was acquired and sunset in the same post, and you had to read to the bottom to find out. We do not measure, and so we do not notice.
3. Definition of the base unit
One Coffeepot (1 Cp) is one terabyte of network traffic that accomplishes nothing, generated by a device that was not asked.
The unit is self-calibrating against the consumer market. The canonical five-dollar VPS at DigitalOcean, Linode or Vultr ships with one terabyte of monthly transfer. That allowance is the household budget for a family’s mail, DNS, VPN and three static sites. The coffee maker spent the entire month in ten days, on roll call.
Rate form: 1 Cp over ten days is 1.157 MB/s, or a sustained 9.3 megabits per second, held for two hundred and forty consecutive hours. That is a broadband connection. The coffee maker had a broadband connection and used all of it.
4. Derived quantities
The ruler runs from the smallest complete useful thing anyone shipped this week to the largest thing anyone has built, and the coffee maker sits absurdly in between.
At the small end, 1 Whistle (1 W) = 16.9 MB, a complete speech to text engine, seven languages, word timestamps, no dependencies, runs on the CPU of a microcontroller. At the large end, 1 Flash (1 F) = 1.664 TB, the FP16 weights of DeepSeek 4.1 Flash, a frontier model that most of the people arguing about it cannot run, because the memory to hold it does not exist at a price. The ruler spans a factor of ninety-eight thousand.
Therefore 1 Cp = 59,171 W = 0.601 F. The coffee maker moved fifty-nine thousand copies of a working speech recognizer in ten days, which is four copies per minute, one every fifteen seconds, continuously, to establish that there was a dishwasher. At the same rate it would move the entire weight set of a frontier model in sixteen days and fifteen hours.
For scale at the bottom: a generous estimate of the machine’s legitimate payload is forty bytes per brew, three brews a day, ten days. One point two kilobytes. The ratio of transmitted to useful is approximately eight hundred million to one.
5. Measurement procedure
Log into the router. Read the per-device transfer counters. If your router does not have per-device transfer counters, that is the finding.
6. Anticipated objections and responses
6.1. “It must be a bug. No company would pay to collect that.”
This was the most popular defence offered, and it is the worst available to Keurig, because it concedes the argument whole. If it is a bug, then a terabyte per device per ten days left the fleet and nobody at the manufacturer added it up either. The owner did not notice, the carrier did not notice, and the party with the telemetry pipeline, the dashboards and the commercial incentive did not notice. “It must be a bug” is not a defence. It is the same illiteracy from the inside of the building, and it is the only version of this story in which literally no one in the chain of custody knew the size of anything.
Note that the five-dollar VPS people would have caught it in an afternoon. They catch smaller. One of them noticed a dehumidifier doing two hundred kilobytes an hour and correctly identified it as cloud polling once a minute. Two hundred kilobytes an hour, diagnosed by hobbyists. One terabyte in ten days, undetected by an industry. The difference is not sophistication of tooling. It is that one group is still counting.
The illiteracy runs all the way down. In the same week people argued about frontier model weights, the live question underneath was memory pricing, where manufacturers have been fined for fixing prices before, are now booking record margins, and are returning capital to shareholders rather than building fabs, while everyone downstream shrugs and says capacity is hard. We cannot honestly price a gigabyte. Of course we cannot notice a terabyte.
6.2. “Consent was given at setup.”
There is no way to consent to a coffee machine. A terms of service dialog on a three inch screen, dismissed by a seventy year old who wanted coffee, is not an instrument either. It is the absence of one, wearing a lanyard.
6.3. “A terabyte is cheap, so the unit measures nothing real.”
Correct, and that is precisely the condition the unit exists to name. The Coffeepot does not measure cost. It measures the amount of activity that can now occur, continuously, inside a private home, below the detection threshold of every party with standing to object. It is a unit of unobserved magnitude. Its cheapness is the whole reason it needs a name.
7. Transitional provisions
Existing literature may continue to express these quantities in terabytes. Authors are encouraged, where the quantity was generated without a request and served no purpose, to state it in Coffeepots, so that the reader is given the one thing the parents were not: a sense of how big it was.
Elsewhere this week, a website launched that plays the ambient audio of a meeting you are not in, so that you can appear to be busy. It is, at last, honest instrumentation. It measures nothing and admits it.