# Earthquake Response

Major earthquakes cause cascading infrastructure failures within minutes: power out, cell towers down, roads blocked. A pre-deployed mesh network provides an immediate communication layer requiring no external infrastructure to function.

## The critical first 72 hours

Emergency management doctrine focuses heavily on the first 72 hours post-earthquake as the window when mesh communications are most valuable:

- Cell towers typically restore within 24 - 72 hours for most users, but coverage is severely reduced
- Landlines may be out for days to weeks in heavily damaged areas
- Internet is intermittent; most social media platforms are unreliable in the first hours due to server load
- A pre-deployed mesh network with solar power and no internet dependency provides communications throughout this window

## Infrastructure resilience by node type

<table id="bkmrk-node-typeexpected-re"><thead><tr><th>Node type</th><th>Expected resilience</th><th>Key vulnerability</th></tr></thead><tbody><tr><td>Ground-level portable (T-Echo, T1000-E)</td><td>High - battery-powered, no infrastructure dependency</td><td>Battery depletion after 7 - 14 days without recharge</td></tr><tr><td>Building rooftop (solar)</td><td>High if solar intact and antenna survived shaking</td><td>Antenna damage from building movement; chimney/parapet collapse</td></tr><tr><td>Hilltop (solar, remote)</td><td>Very high - rarely near structural damage</td><td>Snow/debris on panel; equipment theft in post-disaster chaos</td></tr><tr><td>Building-powered (mains only)</td><td>Low - loses power immediately</td><td>Grid outage (add UPS for short-term backup)</td></tr></tbody></table>

## Neighborhood resilience net design

A "neighborhood net" approach that works well for earthquake-prone communities:

1. **One "net anchor" per neighborhood:** A solar-powered repeater on the highest accessible residential rooftop, battery-backed for 7+ days autonomy.
2. **Block captains with personal nodes:** Each block captain has a device pre-configured for the neighborhood channel. 5 - 10 devices within range of the anchor.
3. **Welfare check protocol:** Pre-established check-in schedule (e.g., every 8 hours). Any block captain who misses check-in triggers a welfare check by neighbors.
4. **Resource messaging format:** Simple standard format: "\[LOCATION\] STATUS: \[OK/NEED HELP\] INJURIES: \[none/n\] DAMAGE: \[minor/moderate/severe\]"
5. **Community coordination center connection:** The neighborhood net connects to a city-wide mesh via the anchor repeater - aggregate status flows up to emergency operations.

## Pre-event preparedness steps

- Deploy solar-powered anchor repeaters *before* an earthquake, not during response
- Distribute personal nodes to all neighborhood net participants
- Conduct quarterly check-in tests to verify devices are charged and configured
- Store node charging cables in emergency kits alongside device
- Document the channel/preset configuration in printed form, stored with the device - don't rely on memory under stress
- Coordinate with local CERT or ARES team so mesh participants know how to integrate with larger response structure