In Wednesday's news feed lay a story that chills you regardless of the temperature in your kitchen: on the night of September 22, a SmartThings firmware update bricked Samsung's Bespoke AI refrigerator line. People came home from work—the light inside went dark, cooling faded, ice cream turned into puddles. Technicians promised nothing before October. And all this on the eve of Chuseok, Korea's main food holiday.
I grabbed this hook for a question usually asked too late: how long does food actually survive in a dead refrigerator, and why does an expensive appliance know how to die from a line in an app. Turned out the numbers here are more curious than the incident itself.
September 22, Tuesday, afternoon. Owners of four-door Bespoke AI units from 2024 and newer received an update notification through SmartThings—and after installation, the refrigerators simply stopped working. The internal screen froze on "Checking SmartThings app during update," the app showed the device offline. Symptoms described identically: lights out inside, cooling disappearing, automatic doors failing.
Users flooded Samsung's forum with roughly the same story. "Got home at nine pm—no light, cold going away, and I've got holiday food and gift galbi in the freezer." Another hauled products into a separate kimchi refrigerator, a third packed the chamber with ice, someone noted a purchase "less than a year ago."
Flipping the breaker didn't help: this wasn't a socket problem. Where a technician did show up, he replaced the main board; where he didn't make it in time—the visit was postponed due to parts.
Bad timing is half the story. Chuseok is celebrated on the 15th day of the eighth lunar month, also called Hangawi: Koreans prepare songpyeon, set tables with offerings to ancestors (charye), travel to hometowns. In 2026 the holiday begins Thursday the 24th—precisely the day Samsung promised to finish restoration. Food for three holiday days was bought in advance, and each family was counting not hours but days.
While kitchens counted days, we needed to figure out what exactly died inside.
Bespoke AI is a refrigerator with intellectual pretensions: an inverter compressor with AI control learns from usage patterns, energy-saving mode through SmartThings adjusts cooling cycles. Behind this wrapper sits an embedded operating system that holds both the "smart" layer—screen, cameras, connectivity—and low-level logic: compressor cycles, defrost. On most designs these two worlds aren't isolated from each other, and that's the key to answering how an update for features can stop the cold.
When firmware corrupts the main controller's state or enters a reboot loop, compressor logic falls along with everything else—even if the update formally only touched smart functions. Samsung explained the cause simply and uncomfortably: a test build intended for internal verification mistakenly went out to actual customers. Not a mechanical failure, not a platform-wide SmartThings crash—a delivery channel error. Normal protection in such cases looks like a pipeline: a build without a "production" tag shouldn't reach the retail fleet, rollout goes by percentages, telemetry is monitored for days. Something in this chain failed.
There's no official number of victims—and that's the most uncomfortable part of the story. Samsung didn't tell Ars Technica how many units were affected; press estimates range from several dozen to several hundred, forums count hundreds of complaints. The company also stated the problem was limited to Korea—I found no independent verification of this claim.
So how long does food survive if the refrigerator became a cabinet? There's a canonical answer—USDA rules, duplicated by CDC and FDA. A refrigerator without power maintains safe temperature up to four hours, and only with the door closed. After four hours without cooling, meat, poultry, fish, eggs, and leftovers are prescribed for disposal. Separate threshold: if a product spent more than two hours at temperatures from 4°C and above—write it off, no tasting or rescue attempts.
The freezer is the second line of defense. Fully loaded, it maintains safe temperature roughly 48 hours, half empty—about 24, provided the door wasn't opened. You can refreeze what still has ice crystals or isn't warmer than 4°C, but quality will suffer. The official phrase sounds like a verdict from instructions: "When in doubt, throw it out."
The numbers are dry, and that's normal: behind them hides a practical conclusion. Incident start—Tuesday, restoration—by Thursday, meaning for many the refrigerator chamber crossed the four-hour line before the technician arrived. The freezer saved longer, but its reserve is also finite. Ars separately reminds: it's not just food at risk—there are medications that need cold, and their reimbursement promises to be harder than with galbi.
Samsung's case isn't the first or last—forced updates already have a death roll. In January 2016, a bug in firmware 5.1.3 drained Nest thermostat batteries even when connected to power, and the device disconnected from boilers, leaving people without heat in the middle of northern winter. Nest acknowledged: 0.5% of users still suffering. Fixed by recharge and restart, for the luckier ones—a physical button on Heat Link.
The same 2016 gifted the world Error 53: after Touch ID sensor replacement, iOS updates turned iPhone 6 and 6S into bricks. Apple explained it as protection against sensor substitution, a California court received a class action in February and dismissed it in June—compensation questions went separately. Old tech, same argument: a security patch made the phone defenseless against its own update.
Recent examples are closer to the refrigerator. In March 2025, firmware 1020.7 retired Samsung soundbars from the 2024 series—HW-Q990D, Q800D, and S801D stuck on eARC input, the update installed automatically and spread across the US, Austria, and Malaysia, and the fix required physical work, free regardless of warranty. August 2026: Petlibro cloud overload left "smart" feeders without food, the company claimed the schedule worked offline, owners disputed this, and it was accused of gaslighting.
The common thread in these stories is boring and accurate: the device is sold with a promise, but controlled from outside. While an update is cosmetic, the risk looks tolerable. Once the update touches the compressor or feeding mechanism, the cost of error stops being digital.
There's a number, by the way—exactly ten years. Consumer Reports found that magazine readers expect ten years from a refrigerator, and manufacturers honestly respond: they build for that long. Reality is softer in wording but no better: 37% of refrigerators bought between 2011 and 2021 broke or worked worse than they should; 75% of owners tried to fix them, and in 13% of cases professional repair didn't help.
Law intrudes on this field from outside. France, from January 1, 2021, under the anti-waste law, required displaying a repairability index—a ten-point rating, initially for five categories: front-loading washing machines, smartphones, laptops, televisions, and electric lawn mowers, with plans to evolve into a durability index—with criteria like reliability and robustness. The EU went further: the right-to-repair directive, adopted June 13, 2024, must be applied from July 31, 2026—just seven weeks before the Korean incident. It requires repairing goods (the text explicitly names, among others, refrigerators) within a reasonable time and at reasonable cost, and prohibits manufacturers from using software methods that hinder repair.
Background detail for scale: SmartThings doesn't just hold these refrigerators—the platform counted 430 million users in January 2026 and 460 by June. The larger the platform, the uglier a delivery channel error looks: one release, the entire audience.
Forums reacted predictably: the slogan "Never update your Samsung refrigerator!" appeared in the first day. On HN they repeated that a simple refrigerator also breaks suddenly, but usually not at one year old and not on an update schedule; the harshest comment boiled down to this just being a refrigerator with a tablet stuck on front. Ars summarized symmetrically: extra technology knows how to ruin a simple product.
In fairness, Samsung acted faster than forums: they stopped the rollout, promised free repair, deadline—by September 24, with losses "they'll try to help." About compensation for spoiled food the company said it's "considering specific measures"—meaning this question remained open at publication time.
I'm ready to admit my stretch: by analogy with Petlibro feeders I expected a cloud failure scenario—dead data center, live refrigerators. That's not what broke: the cloud had nothing to do with it, a local test build that broke through to retail was to blame. A cloud scenario would have been prettier, but facts disproved my thesis, and I'm recording them.
The practical conclusion is shorter than promised by the hook. Food in a dead refrigerator lives by hours, the freezer—by days, and the action plan fits the USDA formula: closed door, four hours, "when in doubt, throw it out." Everything else is a conversation about whether firmware should have access to the compressor at all. Separately—a domestic detail: the salvaged provisions that night were hauled into a kimchi refrigerator, a separate appliance that's not rare in South Korean kitchens. Kimchi lives its own life, far from OTA channels—and that's perhaps the best engineering practice of all.