Silver Springs Earthquake
On the evening of April 13, 2026, a magnitude 5.7 earthquake struck near Silver Springs in Lyon County, about an hour east of Reno. Strong shaking rolled through Fallon, Carson City, and the Truckee Meadows. The USGS recorded more than two dozen aftershocks in the hours that followed.
While residents checked on neighbors and store aisles picked up the pieces, something else was happening on the air. The Nevada mesh network saw a sharp increase in traffic. Handheld nodes and repeaters kept passing messages through the event and its aftermath.
What the USGS reported
The epicenter sat roughly 13 miles east-southeast of Silver Springs at a shallow depth of about 3 miles. The quake was felt across northern Nevada and well beyond state lines. Lyon County reported no major damage to critical infrastructure, but the shaking was real. Grocery stores in Fallon lost glass and inventory. People reached for phones.
That last part is the stress test we care about. Cellular networks often stay up after a moderate earthquake, but they can saturate, lose backhaul, or fail outright when power and transport lines take a hit. Radio repeaters on towers depend on grid power and maintenance crews. A backup layer that does not need either is worth having before the next incident, not after.
What we saw on the mesh
MeshEnvy monitors statewide LoRa traffic through regional ingestors. During the Silver Springs event, message volume in and around the affected area climbed noticeably compared to a typical Monday evening baseline. Nodes that were already on the air stayed on the air. Community handhelds and backbone repeaters continued routing text traffic without any central command to "activate."
We are not claiming the mesh replaced 911 or carrier service that night. Lyon County reported that conventional systems largely held. What we can document is simpler and still important: when people reached for a mesh radio, the network was there. Paths stayed open while chatter spiked. That is exactly the kind of live-fire exercise you cannot schedule in a lab.
The geography helped. MeshEnvy and partner repeaters already cover much of the corridor between Reno, Carson City, and the basin east of Sparks. Sites like Spanish Benchmark sit on high ground above the Truckee Meadows rim. They extend reach into valleys where a single tower would not be enough. The Silver Triangle backbone we are building is meant to tie those high points into a statewide safety net. The quake showed why that net matters on an ordinary weekday, not only during a wildfire or a grid outage.
Why this counts as a case study
Disaster communications planning often focuses on the worst-case headline: towers down, fiber cut, generators flooded. Nevada also needs resilience in the messy middle. A shallow M5.7 event with aftershocks, scattered damage, and everyone trying to check in at once is a credible scenario. Our mesh behaved the way we designed it to behave.
Solar-powered repeaters do not care about grid fluctuations at the foot of the mountain. LoRa nodes in the ISM band do not wait on a carrier ticket queue. A volunteer with a handheld does not need permission to send a check-in message across a hop chain that was already running before the ground moved.
That is the record we want partners, land managers, and funders to see. Not a simulation slide. A dated incident with attributable network behavior.
What we are doing next
This post is the public version of a proof point we have cited in BLM introductions and partner letters since April. We are working on the same kind of deep dive for the Bug and Stallion fire near Virginia Peak, where conventional cell and tower sites failed while mesh nodes kept routing.
If you have mesh logs, screenshots, or field notes from the Silver Springs window, we would like to hear from you. Richer telemetry and community stories will make the next revision of this case study stronger.
In the meantime, you can explore live coverage on the Silver Triangle map and read how we talk about incident performance on the Towers page. The mesh is not theoretical in Nevada. It already has a scorecard.
