NC: Durham ShotSpotter 'heard' almost 1,000 shots in 3 square miles in January
The short version: WRAL reports Durham's ShotSpotter flagged nearly 1,000 rounds fired in a 3-square-mile zone in January, but only a fraction triggered real police response.
Our Take
Credit to WRAL for pulling the raw numbers on this one: almost 1,000 detected rounds, roughly 200 alerts sent to Durham police, all packed into a tiny slice of the city. That's the kind of stat local officials love to cite as proof a system is 'working,' but it also tells you how much of this data never turns into an arrest, a recovered weapon, or anything resembling justice for a victim. It's mostly just a running log of noise in a handful of neighborhoods that happen to be wired for sound.
ShotSpotter isn't an ALPR, but it's part of the same playbook we track every day at DeFlock: acoustic sensors, license plate cameras, and drone programs get sold to city councils as narrow tools for gunfire or stolen cars, then quietly become permanent, always-on surveillance infrastructure concentrated in specific zip codes. Durham's numbers are a reminder that these systems generate enormous volumes of data and dispatches with very little public accounting of outcomes — who got stopped, who got searched, what happened after the alert.
If Durham or your city is layering ShotSpotter, Flock cameras, and drones on top of each other, that's worth mapping and pushing back on. Check our camera map to see what's already deployed near you, and if you want to push your council for real transparency on these contracts, our take-action page has next steps.
This is DeFlock The USA’s original commentary. The video above is the work of WRAL, published on YouTube — full credit to the creator.