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

Iran conducted a broad offensive across the 24-hour period, striking US military assets in Kuwait, Amazon data infrastructure in Bahrain, and tanker traffic in the Strait of Hormuz, while absorbing a reported tenth consecutive night of US strikes on Iranian territory.

All ten events carry partial confidence (provisional, multi-source but unverified). The period saw Iranian strikes extend to three distinct geographic fronts simultaneously — a notable escalation from the 7-day baseline.

Kuwait recorded two strikes against US facilities, up ~54% vs. baseline. Iran's army announced ground-to-ground missile strikes on US missile systems at Camp Arifjan, framed as the 18th phase of its "Thunder" operation. Separately, explosions were reported at Ali al-Salem airbase in Al Jahra Governorate (up 233% vs. baseline). Kuwait's state TV confirmed air raid sirens and stated its air defences were actively intercepting Iranian missiles and drones.

Bahrain saw the IRGC announce (Announcement No. 39) cruise missile strikes on Amazon's data infrastructure, claiming destruction of the facility — described as retaliation for a prior US strike on Darkhoin, Iran. This is the first event referencing civilian critical infrastructure as a declared target.

Strait of Hormuz / Hormozgan Province recorded two tanker strikes: one attributed to an Iranian drone or missile, causing a catastrophic fire in machinery spaces; a second tanker strike reported by UKMTO with no attacker identified. The IRGC Navy was additionally reported to be coercing vessel transits through Iranian territorial waters. A separate explosion in Bandar Lengeh was reported without attribution.

Shiraz (Fars Province) recorded an explosion — up 900% vs. baseline — with no cause or actor identified.

Iran (unspecified) logged a provisional report of a tenth consecutive night of US strikes, up 150% vs. baseline.

The declared IRGC targeting of Amazon's commercial data infrastructure in Bahrain marks a potential shift toward civilian economic targets. Simultaneous strikes on two US military installations in Kuwait suggest a coordinated, multi-axis operation rather than isolated retaliation. The dual tanker strikes and IRGC coercion of Strait of Hormuz transits indicate active pressure on commercial shipping, with direct implications for Gulf energy flows.

Watch for: independent corroboration of damage to Camp Arifjan and Ali al-Salem, which would indicate the effectiveness of Iran's "Thunder" operation and potential US force posture changes in Kuwait. Monitor UKMTO advisories and AIS gap data in the Strait of Hormuz for further tanker incidents; additional reports would indicate a sustained interdiction campaign. Track Kuwaiti government statements for any diplomatic escalation or base-access restrictions. Watch for official US acknowledgment or denial of strikes on Iran, which would indicate the reported ten-night campaign is entering a public phase. Any further IRGC announcements targeting civilian infrastructure would indicate deliberate expansion of the target set.

All ten events covering Syria for the 24-hour period are single-sourced and unconfirmed; no verified or partial-confidence reporting is available. The most significant watch item is a cluster of unconfirmed Israeli ground and fire activity in western Daraa, alongside an unconfirmed IRGC strike claim against a U.S. facility in Jordan.

Against a 7-day baseline of 0.1 events/day, Daraa recorded four unconfirmed events — a 3,900% spike — all single-sourced, primarily via SOHR. These allege Israeli ground incursions and gunfire in the western Daraa countryside near Maaria, with two children reportedly wounded. A separate SOHR report, also unconfirmed, characterizes dozens of Israeli incursions across Daraa and Quneitra over a 20-day window as an escalating pattern. Aleppo produced three unconfirmed clash reports — grenade-related casualties in the eastern countryside and Manbij — with no attributed actor. Rif Dimashq saw one unconfirmed fatality near Al-Qalamoun on the Syria-Lebanon border. As-Suwayda logged one unconfirmed civilian injury from stray gunfire. Al-Mafraq Governorate in Jordan produced one unconfirmed IRGC claim of striking a U.S. military compound at Al-Rukban, with contested casualty figures — this claim is single-sourced from the IRGC's own announcement and is unverified.

The Daraa activity, if corroborated, would represent a meaningful Israeli ground posture shift in southern Syria. The IRGC Al-Rukban claim, if substantiated, would signal direct kinetic action against U.S. forces in Jordan — a significant escalation threshold. Both remain unverified and should not be treated as established fact.

Watch for independent corroboration of Israeli ground movement in western Daraa — confirmation would indicate a sustained operational posture, not isolated incursions. Monitor for U.S. DoD statements or third-party reporting on Al-Rukban; any acknowledgment would indicate the IRGC claim warrants elevated assessment. Continued grenade incidents in east Aleppo without attribution would suggest an unresolved armed actor presence in the area.

Ukrainian drone strikes on Belgorod's civilian infrastructure—including a passenger bus killing five and wounding 23—dominated the period, while Russian multi-axis overnight strikes hit Kharkiv, Chernihiv, Odesa, Sumy, and Zaporizhzhia, injuring at least 30 across those oblasts.

Belgorod (up 186% vs. baseline): Two corroborated partial-confidence events mark a sharp activity spike. A drone struck a passenger bus in Shebekino, killing five civilians (four women and a child) and wounding 23; a separate strike hit the Belgorod agglomeration's southern zone with additional casualties. State television broadcast shelter-in-place orders, and Russian sources described this as the third consecutive day of mass drone attacks on the region.

Chernihiv (up 900% vs. baseline): A single partial-confidence event—a drone strike on an administrative building in Chernihiv city, wounding one—represents a significant departure from the oblast's near-zero baseline.

Multi-city Russian overnight strikes (verified, 6 sources): Russian forces struck Sumy's Epicenter shopping center with FPV drones, multiple districts in Kharkiv, Odesa port infrastructure and a gas station, and Chernihiv's city center with loitering munitions. Explosions were also reported in Kryvyi Rih, Zaporizhzhia, and Poltava regions.

Odesa (down 41% vs. baseline): Despite the volume reduction, a verified 4-source event confirms eight people injured in a strike on an enterprise, with a separate partial report noting port infrastructure and fuel targets.

Zaporizhzhia: Partial-confidence reporting records one killed and 16 wounded across the day.

Mariupol: A partial, single-detail report of Ukrainian strike drones attacking occupied Mariupol; targets, casualties, and damage remain unspecified.

The Belgorod bus strike is the highest single-incident civilian toll of the period on Russian territory and signals continued Ukrainian deep-strike pressure on Belgorod Oblast's civil transport networks. Simultaneously, the Russian overnight campaign demonstrated multi-axis coordination—FPV drones, UAVs, and loitering munitions deployed concurrently across at least four Ukrainian oblasts—suggesting deliberate targeting of civilian commercial and administrative infrastructure rather than solely military assets.

Watch for follow-on Russian strikes against Odesa port infrastructure, which has now been targeted in two events this period. An increase in Chernihiv strike frequency would indicate the oblast is transitioning from incidental to sustained targeting. Monitor Belgorod for further Ukrainian drone operations and any Russian force-protection responses along civil transport corridors. The Mariupol drone report, currently single-sourced and detail-free, warrants watching for corroboration that would indicate renewed deep-strike activity against occupied southern Donetsk.

A drone strike campaign struck at least four targets across Lipetsk, Vladimir, and Krasnodar oblasts in a single overnight window, with Lipetsk recording a 567% spike above its 7-day baseline and industrial infrastructure confirmed hit.

Lipetsk saw the sharpest departure from baseline, with two events in the period versus a 7-day average of 0.3/day. A verified, five-source report documents a fire in Lipetsk city following an attack early on 21 July; no weapon type or casualty detail was provided. Separately, a single-source provisional report places the Indesit machine plant in Lipetsk on fire around 02:14 UTC — cause unconfirmed, but the temporal proximity to the verified city-wide strike is notable. Vladimir recorded one strike, corroborated across two sources, in which a drone hit a residential apartment building with no reported casualties. In Krasnodar, a three-source provisional report describes drone debris landing on a temple in Sochi's central district, injuring a 7-year-old girl who was hospitalised; regional authorities assessed no threat to life. All four events fall within an approximately eight-hour window (00:52–08:18 UTC), suggesting a coordinated or sequential strike package rather than isolated incidents. No events were recorded in Moscow, Saratov, or other baseline oblasts during this period.

The targeting pattern combines residential, industrial, and civic infrastructure across three geographically separated oblasts simultaneously. The provisional Indesit plant report, if confirmed, would represent a strike on named manufacturing infrastructure — a qualitative escalation beyond the residential and civic hits corroborated in this period.

Watch for official Lipetsk damage assessments that would either confirm or refute the industrial facility report. Monitor Krasnodar Krai authorities for updated casualty figures from Sochi. Any follow-on activity in Vladimir would indicate a shift from isolated strike to sustained pressure on that oblast, which has historically tracked below average.

No verified or partially corroborated events were recorded in the Israel theater during this 24-hour period; two unconfirmed, single-source reports hint at activity in Eilat and southern Syria's Quneitra countryside that warrants continued monitoring.

The 7-day baseline for the Northern District sits at 0.1 events/day. This period produced no confirmed activity there. Two new geographic areas registered activity against a zero baseline: the Southern District (Eilat) and Quneitra. Both events are single-sourced and unverified and are therefore excluded from substantive assessment.

The Southern District entry describes loud explosions reported in the port city of Eilat on 20 July, attributed to Israeli media via Tasnim News, with no detail on casualties, damage, or origin. The Quneitra entry describes Israeli military checkpoint activity in the Sida Golan area of the southern Quneitra countryside, alongside reported arrests and attacks — also single-sourced and unverified.

Because zero events in this period meet the verified or partial threshold, no operational or strategic shift can be assessed with confidence. The geographic spread — from Eilat in the far south of Israel to the Quneitra countryside in southern Syria — would, if corroborated, suggest simultaneous pressure on distinct axes. At this confidence level, no such assessment is warranted.

Watch for independent corroboration of the Eilat explosion reports, which would indicate an active threat to the southern port corridor. Watch for additional sourcing on Israeli military checkpoint and detention activity in the Sida Golan area; corroboration would indicate a structured operational tempo in the southern Quneitra countryside. Monitor Northern District for any deviation above its 0.1 events/day baseline.

Two verified Israeli strikes hit Gaza City and Khan Younis within an 11-hour window, both exceeding their respective 7-day per-location baselines by over 150%.

Activity in Gaza Strip — Gaza City and Gaza Strip — Khan Younis spiked above baseline during the period. At 13:13 UTC on 20 July, Israeli aircraft struck the Mawasi area of Khan Younis near the British hospital — a strike corroborated across two independent sources. At 00:05 UTC on 21 July, Israeli reconnaissance and attack drones struck the Al-Samar intersection in central Gaza City, also corroborated across two sources; local reporting notes this location has been struck previously. Both events are verified. No partial or unconfirmed events are included. Gaza City recorded 1 event against a 7-day average of 0.4/day (+150%); Khan Younis recorded 1 event against a 7-day average of 0.3/day (+233%).

The proximity of the Khan Younis strike to the British hospital in Mawasi raises questions about protected-site buffer compliance and civilian exposure in a designated humanitarian zone. The repeat targeting of the Al-Samar intersection in Gaza City suggests it is being treated as a persistent operational node. The combined spike across two geographically distinct sub-areas — southern and central Gaza — within a single period indicates a broader operational tempo rather than an isolated engagement.

Watch for further strikes on or near the Al-Samar intersection, which would indicate continued ISR-driven targeting of that node. Monitor reporting from the Mawasi area for damage assessments near the British hospital, which would indicate the extent of civilian infrastructure impact. Any activity in the West Bank or broader Gaza Strip would indicate whether the elevated tempo is expanding geographically.

All activity in the 24-hour period is confined to North Kordofan and remains entirely unconfirmed; no verified or partial-confidence events were recorded for Sudan.

No baseline exists for North Kordofan, so no delta can be calculated, but two single-source, unconfirmed reports emerged in the period. First, Radio Dabanga reported drone strikes on Al-Rahad city alongside an alleged Sudanese Armed Forces (SAF) recapture of the al-Muslimiyya area — both claims are single-sourced and unverified. Second, the RSF-affiliated "Tassis" group alleged that the SAF deployed chemical weapons in Umm Qurfa, North Kordofan; no casualty figures or corroborating sources were provided, and the claim originates from a party with a direct interest in the narrative.

If the Al-Rahad drone strike and al-Muslimiyya recapture report are corroborated, they would indicate an active SAF offensive push in North Kordofan — a governorate that has seen contested control throughout the broader Sudan conflict. The chemical weapons allegation, even unverified, carries escalatory significance: such claims, once circulated, attract international scrutiny and can shape diplomatic framing regardless of ground truth. The single-source, adversarial-origin nature of the allegation requires independent verification before any analytical weight is placed on it.

Watch for independent corroboration of the Al-Rahad drone strike and the al-Muslimiyya ground movement, which would indicate a confirmed SAF operational tempo shift in North Kordofan. Monitor whether the Umm Qurfa chemical weapons allegation is picked up by additional sources, humanitarian monitors, or UN mechanisms — any such uptake would indicate the claim is gaining traction and warrant elevated scrutiny. Watch for SAF or official Sudanese government response to the chemical weapons allegation, which would indicate the narrative is being contested at an official level.

A single unconfirmed report from Rakhine State alleges regime airstrikes killed five civilians on 20 July, with the Arakan Army using the incident to challenge the junta's stated 100-day peace posture.

No verified or partial-confidence events were recorded in the 24-hour period. The sole event — a strike in Rakhine State — is unconfirmed and single-sourced (The Irrawaddy), and is treated here as a provisional watch item only. No 7-day baseline exists for comparison, so frequency trends cannot be assessed. The Arakan Army's public framing of the alleged strikes as contradicting Min Aung Hlaing's 100-day peace ultimatum represents a notable rhetorical development, if the underlying incident is accurate.

If corroborated, civilian casualties from regime airstrikes during an active, named peace window would signal that the junta's operational tempo in Rakhine State has not been constrained by its own political messaging. The Arakan Army's invocation of the strikes as evidence of hypocrisy suggests the group is actively building a public narrative to delegitimize the peace ultimatum — a posture that could affect ceasefire dynamics along the western front.

Watch for independent corroboration of the alleged Rakhine State airstrikes from additional sources; confirmation would indicate the incident is being under-reported and warrants escalation in coverage priority. Monitor Arakan Army statements for further rhetorical escalation around the peace ultimatum framing, which would indicate a deliberate information campaign. Any regime response — denial, silence, or counter-narrative — would indicate how the junta intends to manage optics during the 100-day window.

Lithuania has deployed military forces to guard the Klaipėda LNG terminal and other critical infrastructure amid warnings of potential Russian provocations; no kinetic incident has been reported.

Against a period with no established baseline for the NATO_FLANK theater, a single event was recorded: an unconfirmed report of Lithuanian military personnel deployed to the Klaipėda LNG terminal and additional critical infrastructure sites. The deployment follows public statements from Lithuanian President Gitanas Nausėda and other regional leaders citing elevated risk of Russian provocations. This constitutes a shift in force posture at a strategically significant energy node, though the event is single-sourced and unverified.

The Klaipėda LNG terminal is Lithuania's primary non-pipeline gas import facility and a key energy resilience asset for the Baltic states. A precautionary military cordon — even unconfirmed — signals that Lithuanian authorities assessed the threat environment as sufficiently elevated to warrant visible protective action. If corroborated, this would represent a meaningful uptick in Baltic-region security posture at critical infrastructure, consistent with broader NATO flank alertness concerns.

Watch for independent corroboration of the Klaipėda deployment from Lithuanian defense ministry statements, imagery, or additional sourcing, which would upgrade this from unconfirmed to at least partial confidence. Monitor for similar force posture announcements at other Baltic critical infrastructure sites — ports, power interconnects, and undersea cable landing points — which would indicate a coordinated regional protective measure rather than an isolated national decision. Any reported incident at or near the terminal itself would indicate a shift from precautionary to reactive posture.

A Houthi spokesman declared a naval blockade against Saudi Arabia targeting Red Sea shipping lanes, including the Bab-el-Mandeb Strait and Yanbu port — this claim is single-sourced and unverified, but warrants close monitoring given the strategic sensitivity of the waterway.

The 24-hour period produced one recorded event against a near-zero baseline for Yemen (Sanaa: 0.1 events/day), with no prior baseline activity logged for the Bab-el-Mandeb area. On 2026-07-20 at 17:47 UTC, Houthi military spokesman Yahya Sari reportedly declared a naval blockade of Saudi ports, explicitly naming the Yanbu terminal and the Bab-el-Mandeb Strait as targets, and called for public mobilization. This event is single-sourced and unconfirmed; no corroborating vessel interdictions, minelaying activity, or secondary reporting have been recorded in the period.

The Bab-el-Mandeb Strait is a critical global chokepoint; approximately 10–15% of world trade transits the Red Sea corridor. A credible blockade declaration — even unverified — affecting Yanbu, Saudi Arabia's primary Red Sea oil export terminal, carries significant potential implications for energy markets and maritime insurance risk. The call for public mobilization, if confirmed, would suggest an intent to escalate beyond rhetoric. No verified kinetic activity supports the declaration at this time.

Watch for corroborating reports from maritime tracking services (AIS anomalies, vessel rerouting near Bab-el-Mandeb), Saudi governmental response, or secondary Houthi media amplification — any of which would indicate the declaration is being operationalized rather than remaining rhetorical. Monitor Yanbu port traffic for disruption signals. A second independent source confirming the blockade announcement would elevate this event from unconfirmed to partial confidence and warrant reassessment.