The latest published intelligence briefing for each active theater, most active first. Every section links to the live theater view on the dashboard.

All 18 events for the 21–22 July period are single-source and unconfirmed; the most operationally significant pattern is a cluster of unconfirmed reporting on Iranian strikes against U.S.-linked facilities in Jordan, combined with an anomalous spike in activity across Deir ez-Zor, Aleppo, and Hama relative to the 7-day baseline.

Activity spiked across multiple governorates with no prior baseline. Deir ez-Zor recorded six unconfirmed events: two separate reports of civilians firing on unidentified drones over al-Ashara (single-sourced, treated as provisional and potentially duplicative), two drone-movement observations over the western and eastern countryside with no strikes reported, and two tribal clash incidents resulting in at least two killed and additional wounded. Aleppo generated four unconfirmed events: a lethal dispute in Ramala village (one killed, four wounded per SOHR), an Asayish security operation in Kobani resulting in four injured personnel, and two reports of Turkish forces withdrawing from a base in the Afrin countryside village of Jeh — again likely duplicative single-source reports. Hama saw two unconfirmed landmine explosions in the Uqayribat badiya, one fatal. In Jordan — up 900% vs. baseline — two unconfirmed Tasnim News reports allege IRGC missile strikes on Al-Rukban/Tower Base 22, and a U.S. Defense Department announcement reclassified a missing soldier as believed deceased, the third U.S. fatality attributed to an earlier Iranian strike on Muwaffaq Salti airbase. A single unconfirmed report noted an Internal Security Forces member killed north of Daraa, and Coalition drone flights were observed over western Idlib.

The Jordan cluster, though entirely unconfirmed, is the highest-order concern: if the Muwaffaq Salti and Al-Rukban reporting reflects actual IRGC strikes, it represents a significant escalation against U.S. and allied special-operations infrastructure at the Iraq-Syria-Jordan tri-border. The Deir ez-Zor drone activity — unidentified origin, no strikes confirmed — suggests ISR or probing operations in a corridor relevant to both U.S. presence and Iran-aligned networks. Recurring tribal violence in Deir ez-Zor indicates persistent instability outside any single actor's control.

Watch for corroborating sourcing on the Al-Rukban and Muwaffaq Salti strike claims; independent confirmation would indicate a live IRGC-U.S. escalation cycle with tri-border implications. Monitor Deir ez-Zor airspace for further drone activity or first strikes, which would indicate a transition from ISR to kinetic operations. Track Turkish posture in Afrin following the Jeh withdrawal for follow-on repositioning. Watch Daraa for additional Internal Security Forces incidents, which would suggest a deteriorating local security environment. Any escalation in As-Suwayda should be cross-referenced against the July 2025 conflict context flagged in unconfirmed footage.

US CENTCOM conducted its eleventh announced round of strikes on Iranian territory during the period, hitting targets in at least four provinces, while Iranian missile and drone salvos reached Kuwait and the Kurdistan Region of Iraq.

The period saw a significant spike in strike activity across multiple Iranian provinces. US CENTCOM publicly announced the start of its eleventh strike round against Iranian soil (provisional, two sources). Strikes are provisionally corroborated in four locations: explosions and air defense activity were reported near Tehran (three sources, provisional), air defense systems activated in the Tajrish district of northeastern Tehran (single-source, provisional), two strike points on the outskirts of Bushehr city with security and relief units deployed for damage assessment (two sources, provisional), and a US strike on Sirik in Hormozgan Province with casualties and damage still under assessment (two sources, provisional). A single-source provisional report places US strikes near Behbehan Northwest Airport in Khuzestan Province, geolocated to Southern Qalind Village.

Tehran Province activity surged to approximately 567% above its 7-day baseline, while Hormozgan Province fell roughly 70% below baseline — consistent with activity concentrating further northwest. On the Iranian offensive side, Kuwait's army issued an official statement (four sources, provisional) confirming active air defense responses to Iranian missiles and drones, describing interceptions as ongoing. Three explosive-laden drones were shot down near the US consulate in Erbil by Kurdish security forces (two sources, provisional); drone origin remains unattributed.

An eleventh publicly acknowledged US strike round indicates a sustained, named operational campaign rather than episodic action. Simultaneous Iranian drone and missile pressure on Kuwait and near a US diplomatic facility in Erbil suggests Iran is maintaining retaliatory pressure across multiple theaters concurrently. Kuwait's official attribution to "Iranian aggression" marks an explicit public escalation in Gulf state posture.

Watch for official Iranian casualty and damage reports from Sirik and Bushehr, which would indicate the scope of infrastructure or military losses. Monitor Kuwaiti air defense communiqués for indications of salvo volume or trajectory changes. Renewed drone activity near Erbil or other US facilities in Iraqi Kurdistan would indicate widening of the indirect pressure campaign. A CENTCOM announcement of a twelfth strike round would confirm continued operational tempo. Watch for any Hormozgan Province reporting that clarifies the anomalous drop in baseline activity.

Strike activity during the 24-hour period concentrated in Kherson Oblast and Crimea, with a verified civilian-casualty event in Kherson city and a partially corroborated drone strike on Yalta producing 17 injured — both areas running significantly above their 7-day baselines.

Kherson recorded two events against a baseline of 0.6/day (+233%). A verified, two-source report confirms Russian drones struck a civilian bus in Kherson city and a tractor in the suburbs, injuring three people. A separate, single-source partial report describes 13 Ukrainian SBU Alpha-group drones targeting a claimed FSB coordination center near Shchaslyvtseve; the strike location has been geolocated but the claim of target type is unverified.

Crimea saw one event against a baseline of 0.3/day (+233%). Four sources partially corroborate an AFU drone strike on a multi-story building in Yalta, injuring 17 people (three seriously, six hospitalized) and disrupting electrical and water supply networks.

Krasnodar recorded one verified event (7 sources) — reported impacts in Krasnodar city — against a baseline of 0.1/day (+900%). No weapon type, actor, or target details are available.

Odesa fell below baseline at one event vs. 1.7/day (−41%). A partially corroborated report cites a Russian daytime strike injuring four people.

The Yalta strike, if further corroborated, represents a notable escalation in Crimea — civilian infrastructure disruption (power and water) adds pressure beyond direct casualties. The Krasnodar impact, verified across seven sources with no accompanying detail, warrants scrutiny: strikes on Russian Federation territory at this confidence level without disclosed attribution are operationally significant. The Shchaslyvtseve claim, if verified, would indicate continued SBU deep-strike targeting of Russian intelligence infrastructure in occupied territory.

Watch for additional sourcing on the Yalta strike to clarify weapon type and intended target — expanded corroboration would indicate a deliberate infrastructure-targeting mission in Crimea. Monitor Krasnodar for follow-on reporting that establishes actor and weapon type; continued silence would indicate information suppression. Watch Kherson Oblast for further drone activity near Shchaslyvtseve, which would indicate sustained SBU targeting of the assessed FSB node. An uptick in Odesa events toward baseline would indicate return to the prior pattern after today's relative quiet.

Coordinated or near-simultaneous strikes hit Wildberries logistics infrastructure in Moscow and Nevinnomyssk within hours of a separate drone attack on Armavir, marking an unusual clustering of strike activity across southern Russia and the capital on 21–22 July.

Three strike events occurred within a six-hour window, against a 7-day baseline that averages roughly 2.4 events/day across all tracked oblasts combined. Krasnodar recorded its first event of the period — up 233% vs. baseline — when Armavir came under a reported drone attack at 23:43 UTC on 21 July (partial, 3 sources). Stavropol activity ran 67% above baseline: a strike on a Wildberries logistics center in Nevinnomyssk is corroborated across five independent sources and carries a verified rating. Moscow activity fell 29% below its baseline, but the single recorded event is significant in scale: a fire at the Wildberries hub in Moscow reportedly destroyed goods valued at over 270 billion rubles; this is partial-confidence, sourced from Russian reporting only and not independently corroborated. No weapon types, casualties, or claimed perpetrators are confirmed for any of the three events.

The verified Nevinnomyssk strike and the provisional Moscow hub fire, taken together, suggest that major commercial logistics infrastructure — specifically Wildberries distribution nodes — may be serving as a target set. If accurate, the claimed 270-billion-ruble loss in Moscow would represent a significant economic disruption event. The geographic spread (Moscow, Stavropol Krai, Krasnodar Krai) within a single operational period is a departure from the more geographically diffuse baseline pattern.

Watch for additional reporting on the Moscow Wildberries fire that would either corroborate or revise the reported damage figure. Monitor for further strike activity against logistics or commercial infrastructure nodes in southern Russia, which would indicate an emerging target pattern. Any claim of responsibility for the Nevinnomyssk or Moscow strikes would be a significant indicator of the actor set involved. Secondary reporting on the Armavir drone attack that clarifies targets or damage would help resolve its partial status.

Three single-source, unconfirmed reports from the 24-hour period allege high-casualty strikes in North Darfur and North Kordofan alongside a reported SAF force deployment in Northern State; none are corroborated and all must be treated as provisional.

No verified or partial-confidence events were recorded for this period. All three events are unconfirmed and single-sourced, carrying no corroboration.

In North Darfur, an unverified report claims a drone strike struck a water source in Tina, near the Chad border, killing at least 21 civilians and wounding 30. The strike's attribution is unstated in the source. In North Kordofan, the RSF-aligned Sudan Founding Alliance (Tasees) — a party with evident interest in shaping narrative — alleged a Sudanese Armed Forces (SAF) airstrike on Umm Garfa that killed 10 and wounded 18, with an unverified claim of chemical weapons use. In Northern State, a separate single-source report claims SAF deployed large reinforcements into the Sahara desert region with the stated aim of opening a new front and severing RSF logistics lines running from Libya. No baseline data exists for any of these three governorates, so trend comparison is not possible.

If the Tina strike report is substantiated, targeting a water source near an active displacement corridor would carry significant civilian harm and potential IHL implications. The Umm Garfa chemical weapons allegation, even unconfirmed, warrants close scrutiny given historical use patterns in Sudan. A confirmed SAF push into Northern State would represent a meaningful geographic expansion of the conflict's active frontlines toward Libya-linked supply routes.

Watch for independent corroboration of the Tina drone strike via humanitarian actors operating in the Chad border zone, which would indicate an escalation in civilian infrastructure targeting in North Darfur. Monitor for any CBRN-focused reporting or NGO medical assessments from Umm Garfa, which would indicate whether the chemical weapons allegation has factual basis. Watch for additional movement reporting or imagery from Northern State consistent with a large SAF deployment, which would indicate a deliberate operational expansion toward the Libyan supply corridor.

All activity in the 24-hour period is confined to Sagaing Region and remains entirely unconfirmed; no verified or partial-confidence events were recorded for Myanmar in this window.

No verified or partial events were logged for the period. Two single-source, unconfirmed reports from Sagaing Region represent the only available signal — both are treated as watch items only and excluded from assessed findings.

Against a baseline with no prior event-day data for any Myanmar region, the appearance of two unconfirmed reports in Sagaing carries no measurable delta but establishes a reference point for subsequent periods.

The two unconfirmed reports, if corroborated, would carry meaningful operational significance. One concerns alleged military operations along the Kale-Tamu road and the Monywa-Yakcheek-Kale road — both routes associated with the India-Myanmar-China three-country bypass corridor — suggesting potential military pressure on economically and diplomatically significant infrastructure near the Indian border. The second concerns an alleged extrajudicial killing of three individuals near Ekaní village, reportedly linked to civilian humanitarian activity. Neither claim can be assessed at this time.

Watch for independent corroboration of reported military movement along the Kale-Tamu and Monywa-Yakcheek-Kale road corridors; confirmation would indicate an active effort to reassert military control over a strategic border route. Monitor for additional sourcing on the Ekaní village incident; corroboration would indicate targeted action against civilian support networks in Sagaing. Watch for any displacement reporting from towns and villages along the two named road sections, which would serve as a collateral indicator of sustained military operations in the area.

Iran fired ballistic missiles at Aqaba, Jordan on 22 July, with four intercepted by the Jordanian military and two impacting unpopulated areas — marking a direct Iranian strike on Jordanian territory with spillover effects into the Israeli city of Eilat.

The 7-day baseline for Aqaba Governorate averaged 0.1 events per day; the period produced one verified strike event, a 900% spike above that baseline. At approximately 08:45 UTC on 22 July, Iran launched a missile salvo targeting Aqaba. The Jordanian army confirmed it intercepted four missiles; two landed in unpopulated areas. Air-raid sirens activated in Aqaba, and explosions were audible in Eilat, Israel, immediately across the Gulf of Aqaba. Israel publicly denied involvement in any interception effort. This is the sole event in the period and is corroborated by two independent sources.

A direct Iranian missile strike on Jordanian soil is a significant escalatory threshold: it extends Iranian kinetic action beyond Gaza-adjacent fronts and implicates the Red Sea corridor and Gulf of Aqaba as active zones. The audible impact in Eilat underscores the geographic proximity — Aqaba and Eilat share a border and port infrastructure. Israel's explicit denial of interception participation suggests either a deliberate distancing from the exchange or a genuine absence of Israeli air-defense engagement, both of which carry distinct strategic implications for regional deterrence posture. Jordan independently absorbing an Iranian strike without allied coordination, if confirmed by further reporting, would represent a notable shift in how regional states are managing direct Iranian pressure.

Watch for Jordanian government statements clarifying the political attribution and any formal diplomatic response to Iran. Monitor Israeli defense and government channels for any revision of the interception-denial position. Additional missile activity in or near Aqaba or Eilat airspace would indicate an ongoing or widening Iranian strike campaign against Gulf of Aqaba targets. Any Jordanian military posture changes — airspace closures, force deployments — would indicate elevated threat assessment by Amman.

A single-sourced, unconfirmed report of a NATO reconnaissance aircraft operating along Kaliningrad's borders with Poland and its eastern and northern perimeter represents the only recorded activity in the NATO_FLANK theater for this 24-hour period.

No verified or partial-confidence events were recorded in the period. The sole entry — unconfirmed and single-sourced — describes a NATO reconnaissance aircraft flying along the Kaliningrad Region's border with Poland before transiting the region's eastern and northern border areas. No airspace violation of NATO territory is described. No 7-day baseline exists for this theater, so no trend comparison is possible.

Reconnaissance activity along the Kaliningrad enclave is a routinely monitored indicator given the region's geographic separation from mainland Russia and its concentration of A2/AD assets. This report, sourced via TASS citing an unnamed EU air traffic control figure, carries inherent credibility risk and cannot be treated as established fact. Its significance is limited until corroborated.

Watch for independent corroboration of the Kaliningrad border overflight from NATO, EUROCONTROL, or flight-tracking databases; confirmation would indicate elevated ISR tasking against the enclave. Monitor Russian official and state-media channels for follow-on claims of NATO provocation in the Baltic theater, which would indicate an intent to escalate the information dimension. Any new movement events in the Baltic Sea corridor or along the Suwalki Gap should be assessed in conjunction with this report.

A partial-confidence report covering the 24-hour period documents Israeli strikes across Gaza resulting in dozens of fatalities, including children and displaced families — the single recorded event represents a 233% spike above the 7-day baseline for the Gaza Strip.

Activity in the Gaza Strip ran significantly above baseline. One partial-confidence event (two sources, provisional) describes Israeli strikes resulting in dozens of deaths, including children and displaced families, with burial of victims ongoing as of the reporting window. No verified events were recorded in the period. Gaza City, Khan Younis, and the West Bank produced no discrete event reports above baseline thresholds during this window.

The Gaza Strip daily rate for this period sits at approximately 1 event versus a 7-day average of 0.3/day — a 233% increase — driven entirely by this single partial-confidence report.

The partial-sourced strike report, if corroborated, would indicate a continued pattern of lethal strikes on civilian concentrations, including displaced populations. The framing as a "weekly roundup" suggests the casualty figures may aggregate sub-events across multiple strike incidents within the period, compressing multiple engagements into a single report and potentially understating operational tempo. The absence of verified corroboration limits analytical confidence.

Watch for independent corroboration of the reported casualty figures from medical sources, UN agencies, or additional journalistic outlets — confirmation would upgrade the partial event to verified and clarify strike scope. Monitor for discrete strike reports from Gaza City and Khan Younis, which fell below baseline this period; a return to normal rates would indicate reporting lag rather than reduced activity. Any West Bank uptick above its 0.1/day baseline would warrant separate tracking.

Houthis declared a blockade on shipping through the Bab-el-Mandeb strait on 21 July, with multiple tankers carrying Saudi crude reportedly reversing course — a sharp spike against an otherwise near-dormant baseline in that area.

Activity at Bab-el-Mandeb surged from a 7-day baseline of 0.1 events/day to one reported incident — a 900% increase above baseline. At approximately 19:27 UTC on 21 July, Houthi forces declared a blockade of the strait. Two-source reporting — rated partial and provisional — indicates several tankers carrying Saudi crude oil reversed course following the declaration. No equivalent movement incidents were recorded in the strait during the prior 7-day window.

Bab-el-Mandeb is a critical global energy chokepoint: roughly 6–7% of global seaborne oil transits it daily. A credible blockade declaration, even if only partially enforced, is sufficient to redirect tanker traffic and spike insurance and freight costs. The provisional reporting notes this follows reported activity near the Strait of Hormuz, raising the possibility of a coordinated dual-chokepoint pressure campaign targeting Saudi energy exports. The operational and commercial disruption potential is significant even absent confirmed kinetic enforcement of the blockade.

Watch for independent confirmation of the Houthi blockade declaration from additional sources, which would upgrade this event from partial to verified. Monitor vessel-tracking data (AIS) around Bab-el-Mandeb for continued tanker diversions or course reversals, which would indicate active enforcement pressure. Any Houthi communiqués specifying enforcement mechanisms or targeted flag states warrant close attention. Parallel monitoring of the Strait of Hormuz is warranted; renewed incidents there alongside Bab-el-Mandeb activity would indicate a deliberate dual-chokepoint strategy.