← Back to all charts

The Data

Everything on this site is built from one dataset: every Home Front Command alert since January 12, 2020 — 160,000+ events and counting, refreshed every 30 minutes. All of it is free to download, from this page or from the GitHub repository. If you use it, cite Under Fire and link back here.

alerts.csv.gz CSV · gzip · ~2.4 MB

One row per alert, per location. Timestamps are Israel local time. Origin is attributed from alert location and timing — see the mission page for methodology and caveats. Download ↓

ColumnTypeDescription
timestampdatetimeAlert time, Israel local (e.g. 2023-10-07 06:29:59)
city_hestringLocation name in Hebrew, as issued by Home Front Command
city_enstringLocation name in English
lat / lonfloatLocation coordinates (WGS 84)
area_enstringHome Front Command alert region (30 regions, e.g. "Gaza Envelope", "Confrontation Line")
alert_type_idint1 = rocket/missile, 2 = hostile aircraft (UAV/drone)
originstringEstimated firing actor: Hamas, Hezbollah, Houthis, Iran, or Unknown
sourcestringIngestion source (rocketalert-live, tzevaadom-fallback, data1)

Ready-made JSON

The pre-computed files the site's charts consume, regenerated from the master every 30 minutes. All paths live under data/processed/.

FileSizeWhat's inside
stats_summary.json<1 KBHeadline totals: alert count, date range, per-origin breakdown, busiest day, unique locations/areas.
timeline_weekly.json~10 KBWeekly alert totals since 2020, broken down by attributed actor.
actors_monthly.json~3 KBMonthly totals per actor — the "Four Fronts" chart data.
daily_counts.json~47 KBPer-day national counts — estimated: weekly totals spread by the global day-of-week distribution. Do not use for single-day analysis; per-day extremes live in records.json.
hourly_dow.json~2 KBAlerts by hour of day (per actor) and by day of week.
actor_hour.json~4 KBFlat actor × hour counts for the patterns heatmap.
areas_summary.json~6 KBPer-region totals, rocket/drone split, active days, peak day, origin mix.
area_monthly.json~7 KBPer-region counts for every calendar month — the time-lapse choropleth data.
area_polygons.json~70 KBGeoJSON polygons of the 30 alert regions (Voronoi of ~1,449 town seeds, clipped to the national footprint).
operations.json~12 KBStats per named operation/campaign: window, totals, peak day, intensity, actor mix, top areas, daily series.
oct7_replay.json~385 KBEvery October 7, 2023 alert with timestamp and coordinates — the replay data.
records.json<1 KBPrecomputed extremes: busiest day and hour, longest quiet streak, biggest single-area spike.
recent_alerts.json~5 KBThe last 30 alert events, salvo-grouped, plus exact per-day counts for the last 14 days. Feeds the live feed.
story_chapters.json~61 KBThe scroll-story's chapters: text, per-chapter map points, and replay sequences.
arsenal.json~45 KBCurated reference data on the weapon systems fired at Israel — specs, ranges, salvo history, sources. Editorial, not derived from the alert data.

What this data is — and isn't

Alerts are Home Front Command (Pikud HaOref) "Tzeva Adom" warnings, aggregated by RocketAlert.live with tzevaadom.co.il as fallback. An alert is a warning to a location, not a projectile count: one missile over a dense area can trigger dozens of location alerts, and one salvo can trigger hundreds. Counts here measure how often Israelis were sent to shelters — a civilian-experience metric, not a military one.

Origin attribution is estimated from alert geography and timing (e.g. Confrontation Line alerts during the northern war → Hezbollah; nationwide simultaneous barrages on known attack dates → Iran). Alerts before mid-2023 are largely unattributed ("Unknown"). Treat attribution as analytical convenience, not ground truth.

How to cite

Under Fire — Israel Rocket Alert Dataset (2020–present).
Alfie Rees, under-fire.org. Alert data via RocketAlert.live.
https://under-fire.org/data

Free for journalism, research, and education with attribution. The underlying alert records originate from Israel's Home Front Command public warning system.