A man checking his parents’ home network logs last week spotted something absurd. Their new Keurig K-Supreme SMART coffee maker had pushed more than a terabyte of data in just over 10 days. One terabyte. From a device meant to brew single cups of coffee.

The discovery, shared on X by a user known as Nomad, quickly drew millions of views. “Hey uh, @Keurig – what the hell is a COFFEE MACHINE uploading, let me double check… ONE FUCKING TERABYTE OF DATA IN 10 DAYS!?!?” he posted on October 6. “Immediately unplugging that. Getting my parents a new coffee machine.” Dexerto reported the original post.

Nomad, who has spent more than a decade in IT and now works as a technical field and community specialist at 3D printer maker Prusa, didn’t stop at the initial shock. He dug into the Ubiquiti UniFi controller data. The numbers were stark. The device labeled “Keurig-20CE2A28C5CE” showed 9.94 gigabytes downloaded but a staggering 1,008.45 gigabytes uploaded over 10 days and nine hours. That works out to roughly 97 gigabytes per day on average. Or about 9 megabits per second of constant upstream traffic.

But here’s the twist. Most of that traffic never left the house. “I looked further into this, it did broadcast 1TB of data, but most of that didn’t escape my network. This is likely a bug with this unit. It did saturate my AP, that sucked,” Nomad explained in follow-up posts. The access point handling the 2.4 GHz connection became overwhelmed. Other devices on the same network slowed to a crawl. His parents had even complained about sluggish internet before he investigated.

And. He rebooted the machine. Moved it to a segregated VLAN. The excessive traffic stopped. No recurrence. Whatever loop or malformed packet storm had gripped the device’s network stack apparently cleared with a restart. “Whatever the issue was, was fixed with a reboot. Anything more nefarious would have come back as soon as it saw a path to internet. It’s likely this was a bug in their network stack,” he added, as detailed in coverage by Tom’s Hardware.

The K-Supreme SMART connects to Wi-Fi for practical reasons. Owners can brew coffee remotely via the Keurig app. It uses BrewID technology to scan K-Cup pods, customize strength and temperature, suggest recipes, and handle reorder deliveries. Voice control with Alexa or Google Home works too. These features require cloud communication. Yet normal operation should involve tiny packets. Status updates. Pod identification. Firmware checks. Not a sustained flood that swamps local wireless hardware.

Nomad considered capturing packets with tools like Wireshark to pinpoint the exact cause. Loop in the firmware? Bad multicast storm? Memory leak triggering endless retries? He decided against it. “It’s not worth keeping an IoT device connected that has the capability of bugging out and causing saturation like this did,” he told followers. The machine now sits unplugged. His parents received a basic, non-connected replacement.

This episode echoes earlier oddities. A smart washing machine once generated 3.6 gigabytes in a short period, enough to raise eyebrows but far short of a terabyte, Cybernews noted. Commenters on Nomad’s post joked about crypto mining, torrent seeding, or data exfiltration. Others worried about privacy. Yet evidence points to a mundane software flaw rather than malice. No signs of outbound internet traffic at scale. No unusual server connections reported.

Still. The incident throws light on broader headaches with connected home devices. Average households now juggle 16 or more internet-linked gadgets. Smart TVs, doorbells, lights, plugs, thermostats, vacuums. Many sit idle yet chatter constantly. They check for updates. Phone home with usage stats. Some models transmit far more than advertised. A recent analysis found certain appliances send 3 to 19 megabytes per week even with minimal use, according to tests summarized in industry reports.

Consumer Reports examined models from GE, LG, Maytag, Samsung and Whirlpool. All sent data to manufacturers covering performance, usage patterns and sometimes location details. The information is usually encrypted. Vulnerabilities were not found in that sample. But scale matters. One misbehaving device on a congested 2.4 GHz band can degrade service for everything else. Routers and access points struggle when dozens of low-power gadgets demand attention.

Recent coverage highlights similar friction. A TechSpot article on the Keurig case warned that packing homes with IoT gear increases the chance one glitch will clog the network. It pointed out smart appliances can also create security vectors or become paperweights if manufacturers abandon support. TechSpot explored those risks.

Network professionals recommend isolation strategies. Place all smart appliances on a guest network or dedicated IoT VLAN. This contains any runaway traffic. It limits lateral movement if one device is compromised. Monitor usage with tools like UniFi, Pi-hole or commercial firewall dashboards. Update firmware promptly, though many appliances receive infrequent patches.

Keurig has not publicly commented on Nomad’s experience as of October 9. The company promotes its smart brewers as convenient. Remote coffee making from bed sounds appealing until the device decides to broadcast enough data to fill a hard drive in days.

Nomad’s story resonates because it feels familiar. Who among us hasn’t traced a Wi-Fi slowdown to some forgotten smart bulb or sensor? The promise of the connected home collides with reality. Cheap hardware. Inconsistent software quality. Limited oversight once devices ship. Bugs that surface only after days of operation, exactly as happened here.

So the coffee maker joins a short but growing list of household objects that turned out to be network hogs. It won’t be the last. As more appliances gain chips and antennas, expect more strange logs. More surprised homeowners. More quiet decisions to rip out the Wi-Fi and go analog. Sometimes the simplest fix beats chasing ghosts in the firmware.