For six weeks in the fall of 2025, a budget fight in Washington reached into the cupboards of 29,000 Buncombe County residents. What the SNAP pause taught the county was not really about a food benefit. It was about how short the wire is between a distant decision and a local kitchen table.
By the fall of 2025, Buncombe County had spent a year digging out from a flood. Then a second blow arrived, and this one did not come from the sky. On October 1, the federal government shut down. Hundreds of miles from Asheville, a budget fight stalled, and within weeks it reached down into the grocery budgets of about 29,000 local residents who use SNAP to put food on the table.
What the county learned over the next six weeks is worth keeping. The lesson was less about a food benefit than about how short the wire is between a decision made in Washington and a grocery run that does not happen in Oakley, or Leicester, or West Asheville. (For what SNAP is and how it works, see the companion primer, How to Think About Food Insecurity.)
A flood gives you days of warning and something to blame. This time there was no storm, only a choice, and it landed just as fast.
A pause does not skip a step. It moves down a schedule until it arrives at a table.
The machinery worked like this. On October 10, the U.S. Department of Agriculture directed North Carolina to hold November SNAP payments while the shutdown continued. SNAP is entirely federal money, and the state and counties are barred from fronting it and waiting for reimbursement. The decision came from Washington, and Buncombe could only brace.
Benefits load on a rolling schedule that runs through the 21st of each month, so the loss came in a wave rather than all at once. About 1,500 county families would feel it first, on November 3. By November 21, every one of the county's roughly 16,000 SNAP households would be cut off. Twenty-nine thousand people, on a clock.
Then came the legal whiplash. Several states, North Carolina among them, sued. On November 7 a partial payment went out, about 65 percent of the usual amount, before a Supreme Court order paused the rest; that day roughly 190,000 North Carolina households received $16 or less on their cards. Days later the shutdown ended, the longest in the country's history at 43 days, and full November benefits finally flowed. For about three weeks, families had no way to know from one day to the next how much, if anything, would be there.
SNAP money does not vanish into the air. It vanishes out of grocery stores.
The average SNAP benefit in Buncombe runs about $171 a person and $344 a household, in a county with one of the highest costs of living in the state. That money is spent almost as fast as it lands, and it is spent close to home, swiped like a debit card at the same groceries everyone else uses. By a common estimate, every dollar of SNAP generates around a dollar and a half of local economic activity, because it moves quickly and stays nearby.
So a pause does more than leave families hungry. It punches a hole in the local economy. County officials estimated that SNAP and the related WIC program together put about $13 million a month into Buncombe's food economy, and that nearly all of it stood to stop in November. The same shutdown was separately costing the county government about $838,000 a week in delayed federal reimbursements for the staff who run these programs. The damage did not sit in one place. It spread to grocers, to county payroll, and through a regional economy still healing from Helene.
Buncombe did nearly everything a county can do. It was never going to be enough on its own.
The county moved fast. It kept its Economic Services offices open so residents could keep applying even while no benefits could be issued. It turned its public libraries into food-drop sites and stood up a countywide food drive with MANNA FoodBank and the nonprofit Bounty & Soul. Residents gave; the county counted the drive at about 7,000 meals. MANNA, already running more than 200,000 pantry visits a month, watched demand climb about 15 percent as families braced, and a single Food for All distribution in Asheville served more than 1,800 households in a day.
It mattered, and it could not close the gap. Roughly 7,000 donated meals stood against $13 million a month in benefits, which is the arithmetic of why local charity can soften a federal pause but cannot stand in for it. That gap is the subject of a companion piece, Why Food Banks Can't Fix Hunger. The thing that fed Buncombe again was not the food drive. It was the benefit coming back on.
Set the politics aside and three plain lessons are left.
First, it was man-made. Buncombe had just spent a year learning what a natural disaster does to a food supply; now it learned what a budget does. There was no hurricane to point at this time, no act of God, only a decision, and it reached local tables within days. County leaders made the contrast directly: a flood is something that happens to a place, while this was something chosen.
Second, the county is more exposed than it looks, and the exposure moves quickly. Twenty-nine thousand residents, $13 million a month in food spending, a county payroll leaning on federal reimbursement, all of it tied to a vote far away and all of it at risk inside a single benefit cycle. When a benefit stops, hunger here does not build over years. It arrives on the third of the month.
Third, the local safety net is real and it is thin. The libraries filled with cans, the food bank surged, neighbors gave, and all of it bought time. What ended the crisis was the restoration of the public benefit, which is the only thing built at the scale of the need. A county can prepare for a pause. It cannot self-fund what Washington stops.
The pause ended. Benefits were restored in full, December ran on its normal schedule, and the libraries went back to lending books. It would be easy to file the episode away as a scare that passed. That would be the wrong lesson. For six weeks, the food security of 29,000 neighbors hung on a fight none of them were part of, and the distance between that fight and their kitchens turned out to be about three days.
Buncombe did what a community should: it organized, it gave, it kept the doors open. None of it would have mattered if the benefit had not returned, because a county can buy time but cannot print a federal benefit. The most useful thing this county can take from the autumn of 2025 is not a better food drive. It is the knowledge of how thin the wire is, and a refusal to treat the program at the other end of it as something optional.