For reference when drafting or reviewing an alert: the past event closest in hazard type and severity to the current situation.
Click a point on the map above, or a record below, to expand its full detail.
| Magnitude / intensity | 6.3m peak river level |
| Spatial extent | 3 districts |
| Frequency | 4th occurrence in 10 years |
| Impacts | 1,200 households affected, 3 schools closed temporarily, ~40km road damaged. |
| Response | BNGRC emergency response deployed; 2 evacuation centers opened. |
| Magnitude / intensity | Category 3 (cyclone) / 5.8m peak river level (flood) |
| Spatial extent | 5 districts, Atsinanana region |
| Frequency | 2nd combined occurrence in 10 years |
| Impacts | 18 deaths, ~45,000 displaced, significant crop damage across Atsinanana; 3 health facilities temporarily out of service. |
| Response | National state of emergency declared; BNGRC-led evacuation of low-lying communes; international humanitarian appeal launched 2025-01-18. |
Hazard chain
Interaction labels use the same vocabulary as Risk Dashboard's Multi-hazard risk assessment (Gill & Malamud 2014) — this chain and that workspace read the same typology.
| Magnitude / intensity | SPI −1.8 |
| Spatial extent | Region-wide |
| Frequency | 3rd occurrence in 10 years |
| Impacts | IPC Phase 3 (Crisis) across Grand Sud; food assistance required for ~500,000 people. |
| Response | WFP food distribution scaled up; cash transfer program activated. |
| Details | Localised flooding, 2 communes, ~1,400 displaced. |
| No-alert reason(s) | Basin below the 1,000 km² upstream area the forecast product covers — no reporting point exists for it. |
| Logged by | Field officer report, verified |
| Reviewed and approved by | Regional DRM coordinator, 2026-03-15 |
A miss with a stated reason is a threshold finding, not a failure record — this row is evidence for whether the covered-basin-area assumption needs revisiting, and surfaces as a calibration note on Thresholds.
| Details | River overtopped, road crossing lost. |
| No-alert reason(s) | Forecast breach reached 24% ensemble exceedance — below the 30% at which a reporting point is raised. |
| Logged by | Community report, verified |
| Reviewed and approved by | Regional DRM coordinator, 2025-11-20 |
The evidence for whether the 30% exceedance threshold is set too high — surfaces as a calibration note on Thresholds.