Live Conflict and War Monitoring Map

Reporting plus physical signal

Conflict news alone is slow and contested. The first hours of any escalation produce claims, denials and low-confidence reporting. What raises confidence quickly is corroboration from independent physical signals: a spike in military airlift into a nearby base, warships repositioning, airspace closures pushing civil traffic into new corridors, a humanitarian agency declaring an emergency.

Tengri puts the reporting layer and those physical layers on the same map so a claim can be checked against observable movement rather than against another claim.

What the conflict layer aggregates

• Continuous headlines from major international wire and broadcast sources.
• Humanitarian emergency reporting via ReliefWeb, including displacement and access constraints.
• GDACS disaster alerts, which cover conflict-adjacent emergencies as well as natural hazards.
• Military aviation activity flagged from ADS-B broadcasts.
• Maritime traffic, including naval movements and merchant re-routing around risk areas.
• Live public cameras in cities where such feeds are lawfully available.

Using the map responsibly

Open source conflict monitoring carries real risk of amplifying bad information. Tengri aggregates published reporting; it does not verify individual claims, and the presence of a headline on the map is not an endorsement of its accuracy. Source names are shown so provenance stays visible.

The physical layers are more reliable than the reporting layer because they are machine-generated, but they are also incomplete — military transponders get switched off, AIS goes dark, and coverage varies by region. Strong conclusions need more than one independent signal.

Related