Tigray Monitor

Tigray Monitor · monthly report

Tigray, December 2025

Generated 2026-10-06 13:33 UTC · dataset version dev · schema 2026-09-25.1

Cite as: Tigray Monitor (2026-10-06). monthly-report-tigray-2025-12 dataset, version dev, schema 2026-09-25.1. https://tigraymonitor.org/reports/monthly/tigray/2025-12

1. Incident summary

1 published incident dated within the month, drawn from 7 attributed claims by 4 publishers.

TypeIncidents
displacement1
Event confidenceIncidents
corroborated1
  1. TIG-2025-000060 2025-12-25: displacement near Tigray — corroborated, 3 independent lineages, location medium.

2. Civilian harm reported by sources

No casualty figures were reported by sources for published incidents this month.

Figures are what named sources reported. They are not platform findings unless the casualty confidence reads verified.

3. Humanitarian and conflict indicators

IndicatorValueAs ofSourceType
Civilian-targeting events (month)12025-12-31HDX HAPIreported
Conflict events (month)62025-12-31HDX HAPIreported
Reported conflict fatalities (month)142025-12-31HDX HAPIreported
Internally displaced people749,5092024-08-31HDX HAPIestimate

4. Pretoria Agreement

  • Permanent cessation of hostilities: insufficient verified data
  • Unhindered humanitarian access: insufficient verified data
  • Protection of civilians: insufficient verified data
  • Disarmament, demobilisation and reintegration of TPLF combatants: insufficient verified data
  • Restoration of essential services and federal authority: insufficient verified data
  • Return of internally displaced people and refugees: insufficient verified data
  • Withdrawal of foreign and non-ENDF forces: insufficient verified data
  • Political dialogue and transitional measures, including on contested areas: insufficient verified data
  • Transitional justice and accountability: insufficient verified data
  • AU monitoring, verification and compliance mechanism: insufficient verified data

5. Verification caveats

  • Corroboration counts independent evidence lineages; copies of one wire story or one statement count once.
  • Event, location, casualty and attribution confidence are separate dimensions; approval by a reviewer does not make an event verified.
  • Incidents at region or zone precision are placed at the unit centre on maps.
  • Coverage depends on connected sources; absence of an incident is not evidence of absence.
  • Boundaries follow the pre-2018 administrative configuration; disputed control is never resolved by the platform.

6. Source appendix

4 publishers cited in this month's incidents. Full claim list with document hashes: claims dataset.

  • Addis Standard
  • Borkena
  • addisstandard.com
  • borkena.com

Licence: Platform records (incidents, claims, assessments): CC BY 4.0 with attribution to Tigray Monitor and to each named source. Third-party data keeps its own licence (see attribution and restrictions).

  • ACLED-derived aggregates require attribution to ACLED and are subject to ACLED's terms; not for redistribution as a standalone dataset.
  • Items discovered via Google News RSS are subject to Google's feed terms, which restrict commercial use; titles and links only are included.
  • IOM DTM, OCHA and UNHCR figures via HDX carry their dataset licences (typically CC BY or CC BY-IGO).
  • Casualty figures and attribution are claims by named sources unless the casualty or attribution dimension reads VERIFIED.