On Call at Midnight: The Unpaid Volunteers Holding Small-Town Internet Together

It's 1:47 a.m. in Marlow, Oklahoma — population roughly 4,000 — and the phone on Dwayne's nightstand buzzes twice. Not a call. Just a text from the monitoring service: Node 3, packet loss 40%, uplink degraded.

Dwayne is 58. He owns a hardware store on Main Street. He is also, technically, the entire network operations center for the co-op that delivers broadband to about 300 households and every business in town, including the pharmacy, the bank branch, and the clinic that does telehealth appointments on Tuesdays.

He pulls on his boots, drives nine minutes to a metal cabinet behind the volunteer fire station, swaps a power supply by flashlight, and is back in bed by 2:40. Nobody pays him. Nobody ever has.

Who Actually Runs This Thing?

Here's a truth that surprises a lot of city folks: across rural America, a startling amount of internet infrastructure is maintained by people who don't get a W-2 for it. Volunteer fire departments. Library boards. Church IT guys. The retired telephone technician who "just kind of took over" when the last ISP gave up on the area.

These aren't hobbyists tinkering in a garage for fun — though plenty of them started that way. These are people carrying pagers, real ones in some cases, for networks that schools and doctors' offices depend on. If their switch dies on a Sunday, Monday's remote learning doesn't happen.

The pattern shows up everywhere once you start looking. A water district clerk in Kansas who also administers the tower that serves three unincorporated communities. A librarian in Vermont who maintains the public Wi-Fi, the patron printers, and — after a merger fell through — the town's only fiber lateral. A deacon in East Texas whose church steeple hosts the repeater that beams connectivity across a valley, making him the de facto ISP for two hundred families.

A Night on the Rotation

Back in Marlow, the morning after his 2 a.m. run, Dwayne walks us through what "on call" actually looks like. There's no ticketing system. There's a laminated sheet in the co-op's back office listing which volunteer has the phone each week — usually Dwayne, sometimes a school district tech named Carla, occasionally a kid in his twenties who works remotely for a software company in Tulsa and is, by unanimous agreement, the best at fixing things nobody else understands.

The monitoring setup is a patchwork of open-source tools. A Raspberry Pi pings every node every five minutes. If a node stops answering, a text goes out. From there, it's old-school: drive to the cabinet, look at the lights, listen for the fan, smell for the burnt-electronics smell every network tech knows by heart.

"People think we're heroes," Dwayne says, waving off the compliment. "We're just the ones who know where the cabinet is."

Why It Falls on Volunteers

The economics are brutal and simple. Running fiber to a town of a few thousand people can cost tens of thousands of dollars per mile, and big providers do that math and walk away. Federal programs like BEAD and the older Rural Digital Opportunity Fund have poured money into changing that, and co-ops and small municipal networks have proliferated. But grant money builds networks. It doesn't staff them.

A town of 800 can't support a full-time network engineer's salary — not from subscriber revenue alone. So the role gets absorbed by whoever has the skills and the stomach for a 2 a.m. phone. Often that's one person. Sometimes it's two.

The result is a quiet fragility. When the volunteer gets sick, moves away, or simply burns out, the network doesn't have a backup admin — it has a laminated sheet with one fewer name on it.

What Keeps Them Going

Ask why they do it and you get variations on the same answer. "Somebody's gotta." "It's my town." "I like fixing things." One volunteer in Minnesota put it plainly: "The clinic's in town because the internet's in town. The internet's in town because I climb that tower. That's the whole arrangement."

There's also, unmistakably, pride. These are people who can point at a grain elevator, a school, a diner, and say that runs through my rack. For a certain kind of technical mind, that beats a paycheck.

How Communities Can Lighten the Load

If your town leans on a volunteer admin — or if you are one — a few things genuinely help:

• Document everything. The single biggest risk to volunteer-run networks is knowledge trapped in one person's head. Passwords, IP maps, cabinet locations: write it down, store it in two places.
• Build a bench. One apprentice is worth more than any monitoring tool. High schoolers, remote workers, the ham radio crowd — recruit before the crisis, not during it.
• Fund the hardware, not just the build. Grants happily pay for fiber. Almost nothing pays for the spare switch sitting on a shelf. A $600 cold spare prevents a three-day outage.
• Pay for training. A community that covers a certification course or a conference ticket keeps its volunteer sharp — and keeps them from feeling like the only person holding the rope.

The Takeaway

America's connectivity story tends to be told in billions of dollars and terabits per second. But between the federal programs and the fiber builds, there's a quieter layer: the hardware store owner driving to a cabinet at 2 a.m., the librarian rebooting the town's link to the world.

They're not asking for parades. They're asking for a backup, a binder, and maybe one more name on the rotation sheet. That seems like a fair trade for keeping a town online.