The human record
What it cost, and who reported it
These figures are not ours. Our archive records that a warning was issued, never what happened next, so every number here comes from the organization named beside it and was retrieved on September 2, 2026.
- at least 7 deaths
Midwest flooding in Indiana, Illinois, Ohio, and nearby states was documented in mid-August 2026; NPR reported at least five states were affected, and CNN reported at least seven deaths in Indiana as of August 14, 2026.
Source: CNN / NPR
ArchiveOur archive independently recorded 227 flash flooding alerts on 2026-08-14, one of this hazard's busiest days of the period.
- around 200 people displaced
Flash flooding in Ohio caused water rescues in Perry County and a flash flood emergency in Crooksville on August 10, 2026; CNN reported around 200 people were forced to leave or could not access their homes in Perry County.
Source: CNN
ArchiveOur archive recorded 173 flash flooding alerts covering Ohio in this period.
- about 23,000 ordered to evacuate; about 40,000 warned
Wildfires near Reno, Nevada, forced mass evacuations in late August 2026; ABC News reported about 23,000 people were ordered to evacuate and about 40,000 additional people were warned they might need to leave.
Source: ABC News
- 6 injuries
A fast-moving wildfire near Reno, Nevada, injured six people on August 24, 2026, according to CGTN, which said three civilians and three first responders were hurt.
Source: CGTN
- more than 300,000 acres burned; at least 60,000 evacuated
Western wildfires in Washington were documented in early August 2026; NPR reported close to a dozen active wildfires in Utah had burned more than 300,000 acres and that at least 60,000 people were evacuated in the Spokane, Washington, area.
Source: NPR
ArchiveOur archive recorded 103 wildfire alerts covering Washington in this period.
- 80,000 acres burned
A wildfire in Texas near Fort Worth expanded to 80,000 acres in late August 2026 and triggered evacuations in two counties, according to ABC News.
Source: ABC News
- more than a dozen feared missing
A Grand Canyon flash flood event in Arizona was reported on August 30, 2026; NBC News said more than a dozen people were feared missing after flash floods swept through the Grand Canyon.
Source: NBC News
ArchiveOur archive independently recorded 5 missing and endangered people alerts on 2026-08-30, one of this hazard's busiest days of the period.
- more than 45 million affected
Dangerous record-breaking heat affected the South and Southwest in late August 2026; The Guardian reported heat was expected to broil more than 45 million people across the southwestern U.S. through the end of August and into early September.
Source: The Guardian
A week of rain drowned the Midwest
The month's deadliest event built slowly and then broke fast. A week of heavy rain across Indiana, Illinois, Ohio and neighboring states peaked on August 12 and 14, when 229 and 227 flash flood warnings went out on those two days alone. August 11 was the single busiest day of the month across all hazards, with 2,303 emergency alerts sent nationwide — tornado warnings and flood warnings arriving together as the same storm complex moved east.
In Indiana, CNN reported at least seven deaths as of August 14. NPR reported that at least five states were affected and that thousands of people had been displaced. Those two accounts, from separate newsrooms, describe the same event our archive recorded at its peak.
Ohio was struck earlier in the sequence. On August 10, flash flooding hit Perry County hard enough to force water rescues, and a flash flood emergency was declared for Crooksville. CNN reported that around 200 people were forced to leave or could not reach their homes in Perry County. Our archive recorded 173 flash flood warnings covering Ohio across the month.
By August 15, the City of Indianapolis had issued its own emergency message — labeled INDY FLOOD 2026 — telling residents in the Rocky Ripple neighborhood to act urgently. The following day, a second city message reported that AES Indiana was surveying the Ravenswood neighborhood to find places where power might need to be shut off because of standing water. The flood had moved from a weather event into an infrastructure problem, and the warnings shifted with it.
Western fires burned through August from the first days to the last
Fire warnings came earliest and most intensely in the Pacific Northwest. The peak days for wildfire alerts were August 2 and 3, when 43 and 45 fire warnings went out respectively. Washington led all states with 103 wildfire alerts across the month, followed by Oregon with 90, California with 81, Wyoming with 77 and Idaho with 70.
NPR reported that close to a dozen active wildfires were burning in Utah by early August, that fires had burned more than 300,000 acres in that state, and that at least 60,000 people were evacuated in the Spokane, Washington, area. Our archive recorded 103 wildfire alerts covering Washington in this period. Evacuation orders from local agencies in Washington peaked on August 1 and 2, with 18 orders each day — the highest single-day totals for evacuation orders all month.
The named local alerts tell the sequence on the ground. On August 6, Granite County Disaster and Emergency Services in Montana issued a red evacuation order for the Frog Pond Basin area. On August 8, Washoe County Emergency Management in Nevada told Cold Springs residents to evacuate immediately as a wildland fire crossed from California. On August 9, the Granite County Sheriff issued a yellow evacuation warning for residents south of the Montana Highway 38 junction with Moose Lake Road. On August 10, Fremont County in Wyoming ordered all Twin Creek Drainage Area residents to go — evacuate now.
A separate fire near Reno, Nevada, produced the month's most specific injury count. CGTN reported that a fast-moving wildfire on August 24 injured six people — three civilians and three first responders. ABC News reported that about 23,000 people were ordered to evacuate and about 40,000 additional people were warned they might need to leave. Late in the month, a wildfire near Fort Worth, Texas, expanded to 80,000 acres and triggered evacuations in two counties, according to ABC News.
A heat dome settled over the South and Southwest
Extreme heat warnings and heat advisories reached more counties in August than any other single hazard — 2,055 counties across the month, compared with 932 for flash flooding. The warnings were quieter than a tornado alarm and easier to ignore, but the geography was vast.
Texas led with 355 heat alerts, followed by California with 253, Arkansas with 203, Oklahoma with 194 and Mississippi with 144. The peak days were August 12, 13 and 14, when between 102 and 113 heat alerts went out each day — the same window when Midwest flooding was at its worst, meaning large parts of the country were under simultaneous and different threats.
The Guardian reported that dangerous, record-breaking heat was expected to affect more than 45 million people across the southwestern United States through the end of August and into early September. The alert archive does not measure how many people were harmed; the documented outcomes research found no confirmed death toll for this event, and none is reported here.
A tornado outbreak crossed the Midwest on August 11
August 11 produced 137 tornado warnings — the highest single-day total for that hazard all month and part of the reason that day became the busiest of the entire month across all alert types. The outbreak was concentrated in Illinois, which led all states with 101 tornado warnings for August, and Ohio with 96. Kentucky, Iowa and Indiana followed.
The 608 tornado warnings for the month covered 285 counties. A second, smaller outbreak followed on August 20, when 89 tornado warnings went out — the second-highest single day for that hazard. The archive does not show confirmed tornado touchdowns or injuries from these events; the documented outcomes research did not return a verified toll for the August 11 outbreak, and none is reported here.
The timing mattered. August 11 was also the day the Midwest flood complex was intensifying, and the same storm system that produced tornadoes in Illinois and Ohio was driving the rain that would peak two days later in Indiana. The two hazards shared a cause and overlapped in the warning record.
County agencies named specific places and told people to move
The most direct warnings of the month came not from weather forecasters but from county sheriffs, emergency management offices and city agencies that named a neighborhood, a road junction or a subdivision and told the people there what to do.
In Wyoming, Fremont County issued at least three named emergency messages across August 9, 10 and 11: a wildfire threat on Highway 28 south of Lander, an immediate evacuation order for all Twin Creek Drainage Area residents, and an evacuation notice for the Crooked Creek subdivision near Fort Washakie. In New Mexico, AlertSantaFe placed the communities of Cundiyo and Cerro Pinon in ready status on August 8 as the Frijoles Fire grew, and New Mexico's Department of Homeland Security and Emergency Management followed on August 11 by placing Cordova in ready status as activity on the same fire increased.
On August 9, Siskiyou County in California issued a missing person alert for Joyce Hammon of Happy Camp, described as possibly en route to Gold Hill, Oregon, in a silver 2017 Ford Edge. That alert is one of 55 missing and endangered person alerts sent across 51 counties in August. The month's busiest day for that category was August 30, when five such alerts went out — the same day NBC News reported that more than a dozen people were feared missing after flash floods swept through the Grand Canyon in Arizona.
Washoe County, Nevada, was the most active single local sender in the fire corridor, with 24 events across the month. The county's August 8 message — telling Cold Springs residents that a wildland fire was moving in from California and that they should evacuate to the library — is the kind of alert that arrives on a phone with a specific address and a specific instruction, and that is what local emergency management is built to send.
What this data cannot tell you
The archive records when a warning was sent, where it was sent, and what people were told to do. It does not record whether anyone acted on it, whether they had a way to leave, or whether the warning arrived before the water did.
The lead time figure in this archive is not a measure of how much notice people received before a hazard arrived. It measures the gap between when an alert was sent and when it was set to take effect — and for most products those two moments are the same by design, so the figure does not describe forecast warning time in the way that phrase is commonly understood.
Evacuation and shelter counts are response counts. They record what people were instructed to do. Where an alert did not name a hazard, the record shows the instruction without a cause. The 8,091 shelter events whose hazard was unstated in the alert text are counted but cannot be assigned to a storm, a fire or anything else.
Deaths, injuries, acres burned and people displaced in this report come from CNN, NPR, ABC News, CGTN, NBC News and The Guardian, as cited in each paragraph. The alert archive itself measures delivery, not outcomes, and is never the source for a toll. Where the documented outcomes research found no verified figure, this report makes no claim.
How BePrepared watches this, all year
This report exists because we already watch the whole country. Every couple of minutes, around the clock, we read the emergency alerts going out across all fifty states and territories, and we keep them. A month of that record is what you have just read.
The national picture is the part most people never see. What matters to you is much smaller: which of these warnings would have reached your street, and what the risks around you look like on an ordinary day.
That is what BePrepared is for. Put in your ZIP code and you get the picture for where you live — the flood, fire and storm history around you, the dams and facilities nearby, and a plan for your household rather than a general one. With a free account you can keep a watchlist of the places you care about, like your home, your parents' address, and your kids' school, and set what you want to hear about.
The evidence
The alert record behind these events
The warnings that went out while the month happened. These are the figures the account above rests on, and they are downloadable below.
What was warned about
| Alert type | Warnings | Messages |
|---|---|---|
| Severe Thunderstorm Warning | 11,205 | 11,205 |
| Special Weather Statement | 9,778 | 9,783 |
| Flood Advisory | 2,672 | 2,673 |
| Flash Flood Warning | 2,659 | 2,659 |
| Special Marine Warning | 1,606 | 1,606 |
| Heat Advisory | 1,569 | 3,130 |
| Small Craft Advisory | 1,345 | 5,022 |
| Flood Warning | 1,221 | 1,900 |
Where
| State | Warnings |
|---|---|
| AZ | 1,957 |
| CO | 1,748 |
| FL | 1,699 |
| IN | 1,621 |
| OH | 1,556 |
| NC | 1,510 |
| GA | 1,494 |
| NE | 1,310 |
The busiest hour of the period was 5pm local time, with 3,608 warnings.
Counties reached most often
| County | State | Warnings |
|---|---|---|
| Pima | AZ | 509 |
| Maricopa | AZ | 336 |
| Pueblo | CO | 270 |
| Cochise | AZ | 266 |
| Pinal | AZ | 262 |
| Cherry | NE | 246 |
| Arapahoe | CO | 226 |
| Fremont | CO | 220 |
| San Bernardino | CA | 208 |
| El Paso | CO | 206 |
A county with no alerts is not a county with no risk. It can mean a quiet period, or a hazard that this feed does not carry.
Where the warnings landed
- Severe storms
- Extreme heat
- Flooding
- Everything else
Severe storms33,888 warnings · 2,525 counties
Extreme heat26,040 warnings · 1,977 counties
Flooding21,037 warnings · 1,794 counties
Fire3,353 warnings · 399 counties
Tornadoes1,176 warnings · 310 counties
Safety & civil700 warnings · 318 counties
Hurricane & tropical185 warnings · 38 counties
View as a table
| County | State | Warnings | Most frequent kind |
|---|---|---|---|
| Pima | AZ | 509 | Flooding |
| Maricopa | AZ | 336 | Everything else |
| Pueblo | CO | 270 | Everything else |
| Cochise | AZ | 266 | Severe storms |
| Pinal | AZ | 262 | Everything else |
| Cherry | NE | 246 | Severe storms |
| Arapahoe | CO | 226 | Everything else |
| Fremont | CO | 220 | Everything else |
| San Bernardino | CA | 208 | Flooding |
| El Paso | CO | 206 | Everything else |
| Elbert | CO | 196 | Everything else |
| Duval | FL | 194 | Everything else |
| Custer | CO | 186 | Everything else |
| La Paz | AZ | 186 | Severe storms |
| Douglas | CO | 183 | Everything else |
| Washington | OH | 180 | Flooding |
| Laramie | WY | 177 | Everything else |
| Huerfano | CO | 176 | Everything else |
| Adams | CO | 168 | Everything else |
| Gila | AZ | 167 | Flooding |
When the warnings arrived
View as a table
| Local hour | Warnings | Of which most severe |
|---|---|---|
| 12am | 1,014 | 19 |
| 1am | 867 | 18 |
| 2am | 870 | 9 |
| 3am | 669 | 7 |
| 4am | 614 | 6 |
| 5am | 649 | 7 |
| 6am | 592 | 13 |
| 7am | 554 | 14 |
| 8am | 638 | 26 |
| 9am | 671 | 25 |
| 10am | 739 | 37 |
| 11am | 908 | 24 |
| 12pm | 1,149 | 31 |
| 1pm | 1,686 | 47 |
| 2pm | 2,508 | 53 |
| 3pm | 3,102 | 93 |
| 4pm | 3,510 | 124 |
| 5pm | 3,608 | 104 |
| 6pm | 3,362 | 84 |
| 7pm | 3,026 | 95 |
| 8pm | 2,474 | 76 |
| 9pm | 1,975 | 83 |
| 10pm | 1,492 | 65 |
| 11pm | 1,254 | 22 |
The feed repeats itself
View as a table
| Stage | Count |
|---|---|
| Messages received | 47,345 |
| Of which updates | 20,465 |
| Of which cancels | 0 |
| Distinct warnings | 37,931 |
| Counties reached | 3,754 |
How severe they were
- Minor
- Moderate
- Severe
- Extreme
- Not classified
View as a table
| Severity | Warnings |
|---|---|
| Minor | 5,054 |
| Moderate | 12,228 |
| Severe | 19,125 |
| Extreme | 1,082 |
| Not classified | 442 |
What people were told to do
- Execute
- Shelter
- Avoid
- Everything else
Where those instructions came from
- Shelter (11,832) — 2690 corroborated as flood, 1009 corroborated as tornado, 32 corroborated as wildfire, 10 corroborated as hurricane, 8091 with no hazard stated in the alert text
- Evacuate (107) — 5 corroborated as flood, 57 corroborated as wildfire, 45 with no hazard stated in the alert text
View as a table
| Response | Warnings | Share |
|---|---|---|
| Execute | 12,215 | 32.2% |
| Shelter | 11,832 | 31.2% |
| Avoid | 10,160 | 26.8% |
| Monitor | 2,254 | 5.9% |
| Prepare | 1,043 | 2.7% |
| Unstated | 303 | 0.8% |
| Evacuate | 107 | 0.3% |
| AllClear | 17 | 0.0% |
How these numbers were counted
Counted AUG 1, 2026 – SEP 1, 2026 · Frozen at publishThe alert figures in this report — how many warnings, where, when, and how severe — come from the alerts this archive received from FEMA IPAWS and the National Weather Service between August 1, 2026 and September 1, 2026, counted once and frozen when the report was published.
Deaths, damage and acreage are not ours and are never drawn from this archive. Each is attributed to the organization that reported it, above.
What was counted
- cap_status = 'Actual' (tests, exercises and demos excluded)
- SAME test codes RWT/RMT/DMO/NPT/NAT excluded, and any event type containing "test"
- An event is the first message of a CAP identifier chain; updates and cancels are counted separately
- Alert time is cap_sent, falling back to ingest time when the feed omits it
- Counties come from the alert geocodes (SAME/FIPS); statewide codes are not counted as counties
What these numbers cannot tell you
- Lead time is the gap between when an alert was sent and when it takes effect. This archive collapses CAP onset into effective, so for many products those are the same instant by design — it is not a measure of forecast warning time.
- 142 alerts expire exactly 24 hours after they were sent because the feed omitted an expiry and the ingest substitutes a default. They are excluded from the duration distribution rather than charted as real forecasts.
- Evacuation and shelter figures are RESPONSE counts. They record what people were told to do, not what caused it; where the alert text does not name a hazard, the row is reported as unstated.
- Hour-of-day figures use each alert’s own local time, resolved from its state. Alerts spanning several states resolve to the first state in their geocodes.
- National Weather Service alerts began arriving in volume on 2026-06-12. Earlier months hold only the handful that reached this archive by other routes, so they undercount weather alerts badly and cannot be compared with later months.
- Population figures are not available for these counties, so alert counts are reported per county and never per resident.
This archive
Collection began 2026-03-27. National Weather Service alerts began arriving in volume on 2026-06-12 (a small number reached the archive by other routes from 2026-03-31). Months from 2026-07-01 onward can be compared with each other; earlier ones cannot.
For newsrooms and researchers
Use these figures
Journalists, emergency managers and researchers are welcome to reuse anything in this report, including the underlying counts, with attribution. Version 1 of these figures is frozen: if a correction changes them, it appears above as a dated note rather than silently replacing what you cited.
BePreparedSolutions.co. "Floods, fires and heat struck across 3,754 counties in August 2026." Alert Pulse, September 2, 2026. https://bepreparedsolutions.co/reports/alert-pulse/2026-08
Source: BePrepared Solutions, Alert Pulse (2026). Alert counts from FEMA IPAWS and National Weather Service feeds; casualty and damage figures as attributed in the report.
<iframe src="https://bepreparedsolutions.co/reports/alert-pulse/2026-08/embed/reach_map" width="100%" height="520" style="border:0" loading="lazy" title="Floods, fires and heat struck across 3,754 counties in August 2026"></iframe>
The embed updates itself if we publish a correction, so it never goes stale the way a screenshot does.
The CSV carries the same frozen figures as this page, keyed to version 1.