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

Active U.S.-Iran military exchanges intensified across Hormozgan Province, Sistan and Baluchestan, and Gulf partner states during the 24-hour period, with Iran striking U.S.-associated targets in Bahrain and Jordan while U.S. forces conducted multiple strikes on Iranian territory and reimposed a naval blockade.

Hormozgan Province saw seven events against a baseline of 4.4/day (+59%). Two strikes are verified: a geolocated U.S. Air Force hit on the Telecommunications Regulatory Authority building in Bandar Abbas, and a fire observed near Kish Island's International Passenger Ferry Terminal. Partial-confidence reporting adds strikes near Sirik, on Qeshm and Kish Islands (a projectile near Kish's water and electricity facility), and on Bandar Abbas. The U.S. military reportedly resumed a comprehensive naval blockade of Iranian ports and coastal areas in Hormozgan — partial confidence, no specific incident detailed.

Sistan and Baluchestan Province recorded two events against a 0.7/day baseline (+186%): a partial-confidence large-scale U.S. airstrike on the port of Chabahar, and a partial-confidence strike on Bampur barracks (388th Iranshahr Brigade) in which Iranian Army sources claim 13 missiles were fired, killing seven personnel and wounding others.

Bahrain surpassed its baseline (+82%): Bahrain's interior ministry confirmed activation of air raid sirens and stated multiple Iranian attacks were intercepted — verified. Iranian state media separately reported a missile and drone barrage targeting a U.S. naval support base in Manama — partial confidence.

Al-Zarqa Governorate, Jordan recorded its first event of the period: Iranian Army sources claim the seventh stage of Operation Lightning struck Al-Azraq Air Base, targeting F-8 fighter positions and U.S.-associated infrastructure — partial confidence, single-side sourcing.

Khuzestan Province: Explosions reported in Ahvaz — partial confidence, no confirmed damage. Kuwait: Air defence systems reported intercepting aerial targets — partial confidence, origin unattributed. The IMO condemned attacks on Strait of Hormuz shipping, citing at least two seafarer deaths — partial confidence.

The exchange pattern shows simultaneous kinetic pressure on Iranian territory (Hormozgan, Sistan and Baluchestan, Khuzestan) and Iranian strikes on Gulf partner infrastructure (Bahrain, Jordan). The reimposition of a naval blockade, if confirmed, would significantly constrain Iranian maritime commerce and military logistics. The Bampur barracks strike, if verified, represents a direct hit on a named Iranian Army formation. The IMO condemnation signals civilian maritime casualties in a critical global chokepoint.

Watch for independent confirmation of the Chabahar and Bampur strikes from non-Iranian sources, which would indicate the scope of U.S. targeting has expanded to Iran's eastern coast. Monitor Bahrain's NSA Fifth Fleet facilities for additional Iranian strike attempts following the partial-confidence Manama barrage. Watch for shipping-movement data through the Strait of Hormuz; a measurable reduction in transits would indicate the blockade is operational. Observe Jordanian and Kuwaiti government statements for any acknowledgment of Iranian responsibility, which would indicate regional escalation is being officially attributed. Monitor for an eighth stage of Operation Lightning targeting Jordan or other regional U.S. basing.

A Ukrainian USV destroyed a Russian FSB border patrol vessel at Gelendzhik, and a verified Russian strike on Odesa port killed two crew aboard a civilian flagged vessel — together marking simultaneous escalation on the Black Sea maritime axis.

Maritime — Krasnodar/Black Sea: Two corroborated (partial, 2 sources each) reports confirm the FSB patrol ship *Izumrud* (Project 22460) was destroyed by a Ukrainian unmanned surface vehicle at Gelendzhik harbour, geolocated to 44.599167, 38.032556. Reporting notes the absence of protective booms and target-detection systems at the dock. This represents a 186% spike above Krasnodar's 7-day baseline.

Odesa — civilian vessel hit: A Russian strike on Odesa port infrastructure struck a Marshall Islands-flagged civilian vessel, killing two. This is the sole verified event in the period (6 sources).

Sumy — aerial bombardment: Russian forces conducted six guided aerial bomb strikes on Sumy community, killing three and wounding seven, with civilians confirmed among casualties. A separate drone strike on a residential area the prior evening also caused fires. Sumy activity is up 186% above baseline.

Sevastopol — infrastructure strike: Ukrainian kamikaze drones struck the Balaklava Thermal Power Plant in occupied Sevastopol (partial, 2 sources). Sevastopol activity is up 900% above its low baseline of 0.1 events/day.

Belgorod — cross-border activity: Two partial-confidence events indicate a strike near Belgorod and a Russian MoD claim of 93 Ukrainian drones intercepted across Belgorod, Bryansk, Kursk, and Rostov oblasts overnight. Belgorod is up 567% above baseline.

Donetsk: Activity fell 38% below baseline; one geolocated destruction of a Russian armoured truck near Malynivka was recorded.

The Gelendzhik USV strike demonstrates Ukrainian reach into a non-frontline Russian Black Sea port roughly 20 km from Novorossiysk, targeting FSB border security assets rather than naval combatants. Combined with the verified lethal strike on a civilian vessel in Odesa, both sides are actively contesting Black Sea maritime access. The Sevastopol power plant strike adds a second infrastructure target in occupied Crimea within the same period. The Sumy civilian casualty toll — three killed, seven wounded from guided bombs — underscores continued deliberate targeting of populated areas near the Russian border.

Watch for: damage assessments from the Balaklava TPP to indicate whether power infrastructure in Sevastopol has been degraded. Monitor Gelendzhik and Novorossiysk port activity; additional USV attempts would indicate a sustained interdiction campaign against Russian Black Sea logistics. Track Sumy for further guided bomb sorties, which would indicate a pattern of deliberate civilian area targeting. Elevated Belgorod drone intercept claims warrant monitoring for Ukrainian cross-border strike tempo shifts.

All eight events in this period are unconfirmed and single-sourced; the most acute spike is in Jerusalem District, where two separate Al-Aqsa Mosque incidents drove activity to roughly 30× its 7-day baseline.

Jerusalem District recorded three events against a baseline of 0.1/day. On 14 July, Israeli forces reportedly entered the main Al-Aqsa prayer hall and cleared worshippers — single-sourced and unverified. The following morning, the King Faisal Gate was briefly closed during reported military drills in the courtyards — again single-sourced and unverified. A separate fire at a Jerusalem light rail construction site on 14 July caused infrastructure damage; cause is under investigation per reporting, and the event is unverified.

Gaza Strip saw two discrete kinetic events above baseline. In Rafah and Gaza City, at least 12 reported deaths on 14 July included a child shot in Rafah, a strike near a mosque in western Gaza City, and a tent strike in the Sheikh Ijlin neighbourhood — all unverified. A helicopter strike on a family home in Deir el-Balah on 15 July reportedly killed four, including a six-year-old child — unverified, single-sourced. The Palestinian Ministry of Health's cumulative toll update (73,246 killed since October 2023, with 1,123 deaths since the October 2025 ceasefire) is unverified.

West Bank logged two new-baseline areas. A settler attack in Beita, south of Nablus, reportedly injured two youths and disrupted an ambulance — unverified. Israeli forces searched a building in Qalandiya camp as part of a reported large-scale West Bank operation — unverified, no casualties noted.

Concurrent unverified incidents at Al-Aqsa — forced clearance followed by a gate closure with military drills — represent the highest-tempo Jerusalem District activity in the 7-day window and carry escalation potential given the site's sensitivity. The reported post-ceasefire casualty accumulation in Gaza, if verified, would indicate the October 2025 ceasefire is not holding at a meaningful level.

Watch for independent corroboration of both Al-Aqsa incidents; verified repetition would indicate a pattern of intensified access restrictions at the compound. Monitor for Palestinian Authority or Waqf official statements, which would provide partial verification. In Gaza, watch for additional strike reporting from Deir el-Balah; any corroborating sources would indicate the area has become an active target zone. In the West Bank, monitor for follow-on reporting from the Qalandiya operation and for further settler incident reports near Nablus, which would indicate broadening settler activity. All eight events in this period remain unconfirmed and should be treated as watch items only.

All seven events in the period are single-source and unconfirmed; no verified or partially verified activity was recorded in Syria between 2026-07-14 and 2026-07-15, but the geographic spread and nature of unconfirmed reports — spanning six governorates — warrants close monitoring.

The 7-day baseline recorded marginal activity concentrated in Damascus, Homs, Idlib, and Rif Dimashq (≈0.1 events/day each). The period produced no events in those legacy hotspots at verified confidence, but unconfirmed reports emerged across six governorates with no prior baseline activity.

Notable unconfirmed shifts: Rif Dimashq registered one report of a large explosion in Sahnaya — up sharply against its 0.1/day baseline — with no identified cause, actor, or casualties. In Daraa, two separate unconfirmed SOHR reports describe Israeli ground movement: one withdrawal from a road near al-Jazira barracks (no kinetic contact reported), and a second describing search operations of civilian homes across Daraa and Al-Qunaitrah countryside, characterised as ongoing violations. In As-Suwayda, a single-sourced SOHR report alleges Syrian Ministry of Defense forces entered the city under a tribal-conflict pretext and killed Druze residents — no casualty figures provided. UXO killed two civilians in the eastern Aleppo countryside. A sound bomb injury was reported in Kobani amid a reported security breakdown in Self-Administration areas. Inter-tribal armed clashes were reported in Ghranij, Deir ez-Zor.

If corroborated, the As-Suwayda report would represent a significant escalation: central government forces using inter-communal violence as pretext to enter a historically autonomous Druze area. The Daraa movement reports, if confirmed, indicate continued Israeli ground activity in southern Syria beyond previously observed patterns. The Sahnaya explosion, unattributed, sits adjacent to critical Damascus infrastructure.

Watch for independent corroboration of the As-Suwayda incident; confirmation would indicate a deliberate shift in Damascus's posture toward the Druze community. Monitor Israeli force disposition in Daraa and Al-Qunaitrah — any sustained presence or expansion would indicate a broadening operational footprint in southern Syria. Track follow-on reporting on the Sahnaya explosion; attribution would clarify whether this is an isolated incident or part of a pattern near Damascus. Continued unconfirmed reports from Kobani and Deir ez-Zor warrant aggregation to assess whether security fragmentation in Self-Administration and tribal conflict zones is intensifying.

All six events for the NATO eastern flank this period are unconfirmed and single-sourced; the most operationally relevant is a reported Russian sabotage recruitment network active in Lithuania, which warrants continued monitoring pending corroboration.

No verified or partially verified events were recorded for this period. No 7-day baseline exists for comparison, so all activity represents a net-new observation set.

Six unconfirmed, single-sourced events span the Baltic states and Baltic Sea approaches. Three GDELT-derived "Fighting" (CAMEO code 19) entries place near-identical coordinates at 59°N, 26°E in Estonia; low mention counts (2–3 sources each), minimal corroborating detail, and no identified actors or weapons strongly suggest automated classification noise rather than a discrete incident. These three are treated here solely as a watch item.

A single-sourced Vot Tak investigation reports a Russian sabotage network operating in Lithuania, involving drone filming and vehicle arson, with recruitment conducted via Telegram at scale since early 2026. This remains unconfirmed but is methodologically consistent with documented hybrid-activity patterns in the region.

Two unconfirmed reconnaissance movements were reported: a NATO RC-135W operating near the Kaliningrad approaches over the Baltic Sea, and a NATO reconnaissance aircraft—previously active over the Black Sea—observed repositioning across Lithuania, Latvia, and Estonia at approximately 10.5 km altitude. No intercepts or hostile engagements were reported in either case.

If the Lithuania sabotage network reporting is confirmed, it would represent an active Russian gray-zone effort targeting NATO member territory. The reconnaissance repositioning from the Black Sea to the Baltic theater, if verified, could signal an intelligence collection priority shift. The Kaliningrad-area ISR sortie is consistent with routine NATO monitoring of that enclave.

Watch for corroborating Lithuanian law enforcement or governmental statements on the reported sabotage network, which would indicate the reporting has operational substance. Monitor for additional source coverage of the Estonia "Fighting" entries; independent confirmation would indicate a discrete incident requiring reassessment. Track NATO ISR flight patterns over the Baltic states for sustained tempo changes, which would indicate an elevated collection posture. Watch for any Russian official response to the Kaliningrad-area reconnaissance activity, which would indicate heightened sensitivity to Baltic Sea ISR operations.

All four events from the 2026-07-14/15 period are single-sourced and unconfirmed; no verified or partial-confidence reporting is available, leaving the operational picture for Myanmar fragmentary and requiring corroboration before assessment.

Activity emerged across three regions with no established baseline, a notable geographic spread versus the 7-day baseline, which recorded only 0.1 events/day confined to Northern Shan State.

In Sagaing Region, two unconfirmed events were logged. A single-sourced local media report describes a gyrocopter strike on a village teashop in Ayadaw Township, killing three civilians including a late-term pregnant woman and seriously wounding one man. Separately, the Myanmar military claimed to have "secured" an unspecified road in Sagaing Region; no location detail, casualty figures, or independent corroboration were provided.

In Kayin State, frontline sources — single-sourced and unverified — report junta forces overran a KNLA/PDF outpost at Lay Kay Kaw Yae Kone, south of Myawaddy near the Thai border.

In Rakhine State, residents and local relief workers — again single-sourced — report ongoing airstrikes in Gwa Township, southern Rakhine, compounding severe flood-related displacement.

If corroborated, the Kayin State outpost loss would represent a junta gain on a strategically sensitive corridor near the Thai border. The Sagaing strike pattern, if confirmed, is consistent with documented regime use of aerial assets against civilian infrastructure. Concurrent reported strikes in flood-affected Gwa Township would compound an already acute humanitarian situation.

Watch for independent corroboration of the Ayadaw Township strike, which would indicate a renewed aerial campaign in Sagaing. Monitor the Myawaddy corridor for resistance counter-movement or further junta advances, which would indicate consolidation of the reported outpost gain. Track humanitarian access reporting from Gwa Township; continued strike reports alongside flood conditions would indicate compounding civilian harm requiring aid response.

All four events covering the 24-hour period are single-sourced and unconfirmed; no verified or partial-confidence reporting exists, limiting analytical confidence. Activity is concentrated in River Nile State around Al Dabbah and in Khartoum State, areas with no established 7-day baseline.

The period produced no verified events against a sparse 7-day baseline (Blue Nile: 0.3/day; North Kordofan: 0.1/day). All four events are unconfirmed and treated as watch items only.

Three unconfirmed reports cluster around Al Dabbah / al-Dabaah in River Nile State — a locality with no prior baseline — describing clashes involving armed drug trafficking groups and elements described as a "Joint Force." A Joint Force spokesman, per one single-sourced report, denied official unit involvement and attributed the fighting to rogue elements and local traffickers. A fourth unconfirmed report attributes 30 civilian deaths, 86 injuries, and 56 amputations across conflict-affected areas of Khartoum State to mines and IEDs, with the hazards reportedly obstructing the return of over 4 million displaced persons.

If corroborated, the Al Dabbah cluster would indicate armed non-state actors are active in River Nile State, a corridor previously outside the primary conflict theater. The mine/IED casualty figures, if verified, would represent a significant civilian harm event and a structural barrier to displacement returns.

Watch for second-source confirmation of the Al Dabbah clashes; corroboration would indicate escalating non-state armed activity along the River Nile corridor. Monitor for official Sudanese Armed Forces or Joint Force statements that either confirm or further distance command structures from the reported fighting. Any verified mine/IED casualty reporting from Khartoum State would indicate a deteriorating humanitarian access situation requiring reassessment of displacement return timelines.

Three unconfirmed fighting events were logged across Venezuela during the period; zero verified or partially verified incidents exist, leaving the security picture effectively unassessable from open sources.

No baseline data exists for Venezuela, so period-over-period comparison is not possible. Three GDELT-sourced clash signals — each single-sourced and unconfirmed — appeared across distinct areas: La Guaira (Vargas state, 09 July), a central-region coordinate approximating Guárico state (11 July), and Caracas, Distrito Capital (13 July). All three are CAMEO code 19 (Fighting) machine-coded events. None provide actor identification, casualty figures, weapons, or sub-location detail. Because all three fall below the unconfirmed threshold, they are excluded from analytical findings and carried only as watch items.

The geographic spread — coastal La Guaira, rural Guárico, and the capital Caracas — would, if corroborated, suggest activity across multiple distinct zones rather than a single localized incident. However, with zero verified or partial-confidence events, no operational or strategic conclusions can be drawn. The absence of corroborating sources is itself notable given the period's breadth.

Watch for any secondary sourcing on the three unconfirmed signals; independent corroboration from local media, NGO monitors, or official statements would indicate whether these represent genuine incidents or GDELT noise. Monitor Caracas specifically, where any confirmed follow-on reporting would indicate an elevated urban security situation. Watch for pattern clustering — additional signals in Vargas or Guárico within the window would indicate sustained rather than isolated activity.

A single unconfirmed report of a delayed fatality from a prior Iranian missile strike in Haifa marks the only event in the 24-hour period; no verified activity was recorded in the Israel theater.

No verified or partial-confidence events occurred during this period. One unconfirmed, single-sourced report — attributed to Israeli Army Radio — states that an individual wounded in an Iranian missile strike on Haifa approximately three months ago has died from those injuries. No baseline data exists for the Northern District against which to contextualize this report. The event represents a lagged casualty rather than a new kinetic incident.

If confirmed, the death would elevate the known human cost of the earlier Haifa strike and could have legal and diplomatic weight regarding attribution of Iranian strike consequences. However, with a single source and no corroborating reporting, no operational conclusions can be drawn. The absence of any verified activity across the theater during this period is itself notable given recent regional tensions.

Watch for corroborating Israeli official statements, hospital records, or secondary reporting that would confirm or refute the Haifa fatality. Confirmation would indicate a revised casualty count for the prior Iranian strike. Monitor Israeli government and military channels for any formal acknowledgment, which would indicate political intent to publicize the death. No verified kinetic activity to track at this time.

The FSB reports foiling a sabotage plot targeting oil infrastructure in Nyagan, Khanty-Mansiysk Autonomous Okrug — the sole event of the period and a statistically significant spike for the region, though the claim remains partially corroborated.

Activity in Khanty-Mansiysk Autonomous Okrug reached 1 event for the 24-hour period against a 7-day baseline of 0.1 events/day — a tenfold increase. The single partial-confidence event involves an FSB claim that a Russian national was detained in Tyumen Oblast while allegedly fleeing after retrieving a 1.5 kg improvised explosive device from a cache. The FSB further asserts the suspect was acting under direction from Ukrainian special services and had transmitted reconnaissance on regional fuel and energy infrastructure to Ukraine. The claim is sourced from two outlets but originates with the FSB and is assessed as partial confidence; no independent corroboration of the device, detention, or intelligence-transfer allegation has been confirmed.

If partially accurate, the incident points to an emerging or continuing effort to extend sabotage pressure into deep-rear energy infrastructure in western Siberia — well beyond the frontline and previously active interior oblasts. Nyagan hosts significant oil extraction and processing capacity. FSB interdiction claims of this type, even when unverified in full, historically precede heightened security postures around regional energy nodes.

Watch for independent confirmation of the detention and device recovery in Tyumen Oblast, which would indicate the FSB account has substantive basis. Monitor Khanty-Mansiysk and adjacent energy-producing regions for additional security announcements or infrastructure disruptions, which would indicate a broader pattern rather than an isolated incident. Any official acknowledgment from Tyumen Oblast law enforcement would help resolve the current partial-confidence assessment.

A partially corroborated strike on Sanaa Airport on 14 July marks the sole recorded event in the theater over the 24-hour period, representing a sharp spike above the 7-day baseline and occurring in the context of a diverted Iranian aircraft and associated retaliation threats.

Sanaa recorded one event against a 7-day average of 0.3 events/day (+233%). At 13:17 UTC on 14 July, a strike was reported at Sanaa Airport, sourced from two outlets and rated partial confidence. No actor, weapon type, or casualty figures are specified. The event is framed around a diverted Iranian plane, with retaliation language noted in sourcing. No verified events were recorded in Yemen during this period.

Sanaa Airport is the sole functioning major air entry point into Houthi-controlled territory. A strike on that facility — even one lacking full corroboration — carries disproportionate logistical and symbolic weight. The linkage to a diverted Iranian aircraft introduces a cross-actor dimension: if substantiated, it would suggest the strike was tied to Iranian supply or personnel movements, with potential escalatory implications involving Iran-aligned networks in the theater. The partial-confidence rating limits analytical weight, but the airport's strategic value means the event warrants close monitoring regardless.

Watch for additional sourcing that would corroborate or refute actor attribution and weapon type for the Sanaa Airport strike. Any claim of casualties or infrastructure damage at the airport would indicate a more significant disruption to air access than current reporting suggests. Monitor for Houthi or Iranian statements referencing the diverted aircraft, which would indicate this event is part of a broader signaling exchange. A follow-on strike or retaliatory action in or around Sanaa in the next 72 hours would indicate escalation beyond an isolated incident.