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

US forces conducted a broad, multi-axis strike campaign across Iran's southern coast and interior on 8–9 July, with reported Iranian retaliation against Bahrain and rare damage footage from Tehran — a sharp escalation past the prior ceasefire baseline.

Hormozgan Province saw four strike events in 24 hours against a 1.7/day baseline, including a verified CENTCOM-announced salvo tied to alleged Iranian attacks on three ships in the Strait of Hormuz, verified strikes on Bandar Abbas and other coastal nodes, and partial reporting of impacts at the Port of Kuhestak and an IRGC naval site near Sarkhur Tahruyi. Chabahar was struck twice — one verified event described as the first US strikes there since a ceasefire, plus a partially sourced follow-on — driving Sistan and Baluchestan activity well above baseline. Partially sourced strikes also hit IRGC barracks in Bushehr and a railway bridge near Aqqala in Golestan, geolocated by open-source analysts. Iranian retaliation is partially sourced: air raid sirens across Bahrain and a reported second strike on the US Fifth Fleet HQ in Manama. Iranian state media released partially sourced footage of damage at the late Khamenei's Tehran compound. Separately, SAF verifiably retook Kurmuk in Blue Nile, and a verified Israeli strike hit near a medical center in Al-Nabatieh al-Fouqa.

The verified CENTCOM strike package and Bandar Abbas impacts confirm the ceasefire referenced in the Chabahar reporting has collapsed. Hormuz-adjacent energy and naval infrastructure — plus the Bushehr and Aqqala nodes — indicate a campaign targeting both coastal military capacity and interior logistics. The Bahrain reporting, while only partially sourced, signals Iranian willingness to strike US Gulf basing directly.

Watch for independent confirmation of the Fifth Fleet HQ and Manama strikes; corroboration would indicate a sustained Iranian counter-campaign rather than symbolic salvos. Watch Bushehr for follow-on strikes near nuclear infrastructure, and Hormuz shipping lanes for closure indicators. Further geolocated damage in Tehran would indicate leadership-targeting expansion. In Blue Nile, watch for RSF/SPLM counterattacks around Kurmuk.

All 11 reported events for the period are single-sourced and unverified, but the concentration of ISIS-attributed activity in Deir ez-Zor and a mortar/VBIED cluster in As-Suwayda mark sharp departures from the 7-day baseline.

Deir ez-Zor rose from a 0.1/day baseline to four reported incidents: simultaneous attacks in the eastern countryside attributed to ISIS, a further eastern-countryside attack by suspected ISIS cells, and an ISIS-claimed killing in the northern countryside. Separately, Syrian and Turkish engineering teams are reported to have completed a temporary military bridge from Deir ez-Zor city across the Euphrates to the eastern bank — a cross-river military connector not present in baseline reporting. As-Suwayda produced three incidents against a 0.1/day baseline: a mortar strike on a National Guard position in the countryside, the seizure of two booby-trapped vehicles inside Sweida city, and a fatal stray shell south of Suwayda. First-appearance governorates include Idlib (mine casualties reported across Idlib–Raqqa countryside), Aleppo (engineering-crew casualties during dismantling near Kobani), Homs (landmine injury in the east), and Daraa (reported intensive Israeli reconnaissance flights over the Yarmouk Basin). All items are single-sourced.

If corroborated, the Deir ez-Zor pattern would indicate a coordinated ISIS tempo increase concurrent with a new Syrian–Turkish military crossing over the Euphrates — two developments that together reshape the eastern-bank access picture. The As-Suwayda cluster combines indirect fire on security forces with VBIED interdiction inside the city, suggesting the threat vector there is not limited to rural skirmishing.

Watch for second-source confirmation of the Deir ez-Zor bridge and any follow-on troop movement across it; further ISIS claims in Deir ez-Zor would indicate a sustained campaign rather than isolated incidents. In As-Suwayda, additional VBIED finds or repeat indirect fire on National Guard positions would indicate an organized cell rather than opportunistic attacks. In Daraa, any transition from Israeli reconnaissance over the Yarmouk Basin to kinetic activity would mark a significant escalation.

Satellite-verified fire at an air defense/radar site near Glazovka (Baksy) in Kerch district, Crimea, is the period's only confirmed strike, occurring alongside partial reporting of fatal Russian strikes on Kyiv and Odesa and an unusual Luhansk air-loss claim.

Only the Kerch-district strike near Glazovka is verified: NASA FIRMS thermal anomalies and satellite monitoring indicate a fire at an air defense position, with additional anomalies over the adjacent Sea of Azov. Crimea activity is up sharply against a 0.3/day baseline. Partially sourced reporting describes ballistic missile and drone strikes on Kyiv (four killed) and a strike on Odesa (four killed, six wounded, infrastructure damage) — both oblasts running above (Odesa) or near (Kyiv) baseline on lethality rather than volume. Ukraine claims 72 drones downed overnight with fighting reported around Kharkiv, though Kharkiv event count is below its 1.9/day baseline. In Donetsk, two geolocated tactical strikes are partially sourced: a Ukrainian 425th "Skala" drone hit on a substation near Volodymyrivka, and a Russian Vandal drone strike on a Ukrainian UGV near Drobysheve. A single-source claim of a Russian Su-35 downed near Mistky, Luhansk — attributed to combined F-16 and Patriot engagement — drives the 900% Luhansk spike but remains uncorroborated.

The Glazovka signature, if it reflects a successful strike on Kerch-area air defense, would degrade radar coverage over the Kerch Strait and northern Azov approaches. Simultaneous lethal strikes on Kyiv and Odesa indicate continued Russian targeting of rear-area urban and port infrastructure. The Luhansk Su-35 claim, if corroborated, would mark a notable manned-aircraft loss deep behind Russian lines.

Watch for second-source confirmation or wreckage imagery from Mistky; its absence would keep the Su-35 claim unverified. Watch for follow-on imagery of the Kerch-district site and any Russian air defense repositioning, which would indicate sustained damage. Monitor Odesa port and Kyiv energy nodes for repeat strikes.

All reporting for the period is single-sourced and unverified, but the reporting clusters around a Myanmar Navy bombardment of coastal Rakhine and a new pro-junta militia raising in adjacent Ayeyarwady — signals worth tracking even absent corroboration.

With no prior 7-day baseline, every reported activity registers as a new signal. The densest reporting is in Rakhine State (three unconfirmed items): naval shelling along Gwa Township's coast — reportedly four warships firing over 80 shells — with a related account of six civilian injuries in Kyeintali, and a broader unverified claim of sustained naval bombardment across Arakan compounded by monsoon flooding. In Ayeyarwady Region, the Southwestern Region Commander reportedly presided over the arming of a new pro-junta militia at Shwe Thaung Yan in Pathein Township, an area previously contested with the Arakan Army. In Sagaing Region, a single source reports 12 PDF fighters from the Monywa District Battalion killed across Indaw and Ayardaw townships over roughly two weeks. In Karenni State, a junta suicide drone reportedly detonated near an IDP camp in Demoso Township, said to be over 30 km from active fighting. None of these are corroborated by a second source.

If the Gwa and Kyeintali shelling accounts hold, they indicate the Navy is being used as a fires platform against coastal populations during monsoon season, when displacement options are constrained. The Shwe Thaung Yan militia raising, if accurate, suggests the junta is substituting irregular forces for regulars along the Rakhine–Ayeyarwady seam facing the Arakan Army.

Watch for second-source confirmation of the Gwa/Kyeintali naval shelling and casualty counts; corroboration would indicate a sustained maritime fires campaign rather than an isolated salvo. Watch Shwe Thaung Yan for follow-on militia deployment reporting, which would indicate the AA–SAC frontline is shifting into Ayeyarwady. Watch Demoso for further strikes on IDP sites, which would indicate deliberate targeting rather than a stray munition.

All five events in this 24-hour window on the NATO eastern flank are single-sourced and unconfirmed; nothing in the reporting rises above watch-item status, and no prior 7-day baseline exists for comparison.

With no baseline available, the period's activity establishes an initial signal rather than a delta. Three unconfirmed GDELT CAMEO "fighting" flags clustered in northeastern Estonia (near 59°N, 26°E) on 8 July carry low mention counts (2–3) and no actor, weapon, or incident detail — they are not corroborated clashes. In Lithuania, a Vot Tak investigation alleges a Russian sabotage recruitment network using mass Telegram posts to hire low-level operatives for arson and drone-filming tasks; single-sourced and unverified. Over the Baltic Sea, a UK RAF RC-135W Rivet Joint was reported operating near Kaliningrad, with no reported airspace violation or intercept.

The Estonia GDELT cluster, even if artefactual, concentrates in one grid cell and warrants disambiguation before it is either dismissed or escalated. The Lithuania sabotage-network reporting, if borne out, would fit the pattern of Russian low-cost hybrid recruitment already flagged across the flank and shifts risk from state operatives to disposable local hires. The RC-135W sortie near Kaliningrad is routine in character but is the only kinetic-adjacent ISR signal in the window.

• Watch for second-source confirmation or official Estonian statements on the northeastern Estonia GDELT cluster; independent local reporting would indicate a real incident rather than a coding artefact.
• Watch for Lithuanian VSD or police commentary on the alleged Telegram sabotage recruitment; arrests or named cases would move the Vot Tak reporting toward corroboration.
• Watch for Russian MoD or Kaliningrad-based reactions to further NATO ISR sorties; a shift to intercept or airspace-violation claims would indicate escalation in the Baltic ISR pattern.

Ukrainian long-range strikes hit Russian energy infrastructure across at least three federal subjects in a 24-hour window, with a verified fuel depot fire in Tver and corroborated multi-source damage at the Nizhnekamsk refinery complex in Tatarstan.

Activity shifted sharply away from the recent Omsk/Moscow-weighted baseline toward the Volga and southern axes. A fire at the TVERNEFTEPRODUKT fuel depot in Tver is verified across four sources, against a 7-day baseline of 0.1 events/day for the oblast. Three partial reports — geolocated from vantage points near Naberezhnye Chelny and a northern-facing angle — converge on multiple simultaneous fires at the Nizhnekamsk refinery in Tatarstan, reportedly involving FP-1 drones; the cluster is mutually corroborating despite each report being single-sourced. A separate partial report describes a Shahed strike on an oil depot in Mikhaylovsk, Stavropol, a 900% deviation from baseline for that krai. No casualty figures are provided in any report.

All four incidents target downstream petroleum infrastructure — refining at Nizhnekamsk, storage at Tver and Mikhaylovsk — rather than upstream or military sites. The geographic spread (Tver in the northwest, Tatarstan ~1,000 km east, Stavropol in the south) indicates simultaneous employment across widely separated axes rather than a single corridor. Nizhnekamsk is among Russia's larger refining nodes; concurrent multiple fires, if damage is confirmed, would carry throughput implications beyond the immediate incident.

Watch for follow-on imagery or thermal data quantifying damage at Nizhnekamsk; sustained fires beyond 48 hours would indicate process-unit rather than peripheral damage. Monitor whether the Mikhaylovsk depot strike is corroborated by additional sources or remains single-thread. Watch Tver for official Rosneft/TVERNEFTEPRODUKT statements on depot status. Renewed activity in the Tatarstan corridor would indicate a sustained campaign rather than a single wave.

The reporting period contains no verified or partially verified events; all four items are single-sourced and unconfirmed, leaving the theater picture indicative rather than substantiated.

Against a 7-day baseline showing activity only in the Northern District (0.1 events/day), four new unconfirmed reports surfaced in districts with no prior baseline. The Syrian Observatory for Human Rights reported an Israeli ground infiltration with aerial overflights in the Daraa–Quneitra countryside, said to coincide with a UNDOF patrol passage — single-sourced and unverified. GDELT-flagged CAMEO "fighting" codes produced two clustered reports near 31.5°N, 34.75°E on the Gaza–southern Israel border, one sourced to the Jerusalem Post and one to WAFA, roughly twelve hours apart; actors, weapons, and casualties are unspecified in both. A separate GDELT-flagged report via Arab News described fighting in Tel Aviv, again without specifics. None of these have corroborating second sources within the period.

The two Gaza-border reports share coordinates and event type across Israeli and Palestinian outlets, which raises their weight as a watch item even though neither is independently confirmed. The Quneitra report, if borne out, would touch the UNDOF separation-of-forces zone and Syrian territory simultaneously. The Tel Aviv "fighting" label is ambiguous — GDELT CAMEO 19 does not distinguish rocket impact, unrest, or armed incident — and should not be read as a kinetic urban clash without corroboration.

Watch for second-source corroboration of the Gaza-border coordinate cluster; convergent Israeli and Palestinian reporting would indicate a real incident rather than a GDELT artifact. Watch UNDOF and Syrian channels for any confirmation of cross-boundary Israeli ground movement in the Quneitra countryside. Watch Israeli domestic media for clarification of what the Tel Aviv report actually describes.

The Sudanese Armed Forces (SAF) retook Kurmuk, the administrative seat of Kurmuk locality in southern Blue Nile State, on the morning of 8 July, reversing prior territorial gains by an RSF–SPLM(-N) coalition along the Ethiopian border.

Blue Nile activity jumped to 2 events in 24 hours, against a 7-day baseline of 0.3/day — a shift driven entirely by developments in Kurmuk. The recapture of Kurmuk town by SAF is verified across four sources. Later the same day, single-sourced footage geolocated to 10°33'28.76"N 34°16'50.71"E showed SAF personnel inside the Kurmuk locality headquarters compound, partially corroborating consolidation of the site. North Kordofan produced no reported events in the period.

Kurmuk sits on the Ethiopian border and is the administrative anchor of its locality; its handover reverses a rare instance of open RSF–SPLM(-N) territorial coordination in the southeast. SAF's presence inside the headquarters compound, if further corroborated, would mark not just a tactical advance but reoccupation of an administrative node, with implications for cross-border movement and for the durability of the RSF–SPLM(-N) alignment on this axis.

• Watch for additional geolocated imagery from central Kurmuk beyond the single-sourced compound footage; multi-source confirmation would indicate consolidated SAF hold rather than a transient entry.
• Watch for reported RSF or SPLM(-N) counter-movements south and west of Kurmuk town; renewed clashes would indicate the coalition retains offensive capacity in southern Blue Nile.
• Watch for any spillover reporting from the Ethiopian border side; displacement or cross-border fire would indicate the engagement is not contained to the locality.
• Watch North Kordofan for a return to baseline tempo after the 24-hour lull.

Israeli military operations across the Gaza Strip continued into the reporting window, with Palestinian health authorities reporting eight killed and 17 wounded over a 24-hour period — a single partial-confidence data point that nonetheless represents a sharp uptick against the 7-day baseline.

One partial-confidence casualty report from the Palestinian Health Ministry covering the Gaza Strip drove a 900% increase over the 0.1 events/day baseline for the enclave outside Gaza City. The figure — eight killed, 17 wounded in 24 hours — is aggregated rather than tied to a single discrete strike, and the ministry noted additional casualties remain unrecovered under rubble and along roadsides, implying the count is a floor rather than a ceiling. No new activity was reported from Gaza City, the Southern District, Hebron, or Ramallah during the window, all of which sat at or below their baseline rates.

The Gaza-wide casualty report indicates operations are sustained and geographically diffuse rather than concentrated on a single axis, consistent with continued clearance activity across the enclave. The ministry's caveat on unrecovered bodies suggests reporting lag and access constraints are shaping the visible tempo, meaning the true operational intensity is likely understated in open sources. The absence of reported West Bank incidents during the window is notable given baseline activity in Hebron and Ramallah.

Watch for follow-on Health Ministry updates revising the Gaza casualty figure upward, which would indicate either recovery of bodies referenced in the current report or continued kinetic activity. Monitor whether discrete strike locations within the Gaza Strip are identified by secondary sources, which would help disaggregate the ministry's rolled-up count. Watch the West Bank — particularly Hebron and Ramallah — for a return to baseline incident reporting; a continued gap would suggest either a genuine lull or a reporting shortfall worth investigating.

The reporting period contains no verified or partially corroborated activity in the Venezuela theater. A single unconfirmed assault signal near La Guaira is the only entry and does not support substantive analytic conclusions.

No baseline exists for the prior 7 days, so no delta can be calculated. The only new data point is a single-sourced, unverified assault signal in La Guaira (Vargas) on 5 July, derived from a GDELT CAMEO-18 tag with three mentions and a mildly negative tone score. No corroborating open-source reporting has surfaced in the event list, and no actor, target, or casualty details are attached. This does not constitute a confirmed incident and should not be read as an uptick in kinetic activity.

With zero verified events, the operational picture for Venezuela this week is effectively dark from the ingest layer's perspective. The absence of corroborated reporting is itself the salient finding: either genuinely low-signal conditions persist, or collection against the theater is thin. The lone La Guaira signal, given its proximity to Caracas and the country's principal port and international airport, would warrant attention if corroborated — but on current evidence it cannot be treated as an indicator.

• Watch for second-source corroboration of the La Guaira assault report; independent local reporting would move it from noise to a data point worth weighting.
• Monitor Vargas-area outlets and port/airport-adjacent channels; any follow-on reporting tied to the same date-location pair would indicate a real underlying event rather than a tone artifact.
• Track whether ingest volume for Venezuela remains at zero verified events; sustained silence would indicate a collection gap rather than a quiet theater.

A partially corroborated maritime attack on a cargo vessel in the Red Sea off Hodeida is the sole reported incident this period, marking a low-volume week that nonetheless registers as a spike against a near-zero baseline.

Al Hudaydah recorded one incident against a 7-day baseline of 0.1 events/day — a nominal 900% increase driven by a single data point. The event, dated 5 July, involves a cargo ship attacked in the Red Sea off the Yemeni coast, referenced via a British military report cited in Indian press. It is rated partial (two sources) and localized to Hodeida governorate waters. No ground clashes, strikes, or interdictions elsewhere in Yemen appear in the event set for this window.

The Red Sea corridor off Hodeida remains the principal friction point in the Yemeni theater, and even a single corroborated maritime attack sustains the pattern of Houthi-linked pressure on commercial shipping that has shaped insurer and router behavior since 2023. With only one partial event in the record, the week does not establish a trend, but the absence of any offsetting inland activity means the maritime domain is currently carrying the entirety of the theater's signal.

• Watch for follow-on claims of responsibility or vessel identification tied to the 5 July Red Sea incident; corroboration would upgrade the event's confidence and clarify targeting patterns.
• Monitor UKMTO, EUNAVFOR Aspides, and CENTCOM advisories for additional incidents in the Bab el-Mandeb–Hodeida approaches; a second event within 72 hours would indicate a resumed tempo rather than an isolated strike.
• Track Hodeida port and coastal areas for retaliatory air activity; new strike reporting would indicate escalation beyond the maritime domain.