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

Reporting across Gaza and the West Bank surged well above the 7-day baseline, but every event in the period is single-sourced and unverified. The dominant signals are drone/artillery strikes in northern and central Gaza and a weekend wave of settler violence across the West Bank.

All 11 events are unconfirmed. Gaza Strip reporting rose to roughly 3 events against a 0.3/day baseline, driven by drone strikes near Asqula junction east of Gaza City and Abu Sharkh roundabout west of Jabalia refugee camp, additional strikes in Beit Lahiya, and artillery east of al-Bureij camp in central Gaza. A separate report cites at least seven Palestinians killed across the Strip over 48 hours, with nine bodies recovered from rubble. A single-sourced strike report in Gaza claims two Hamas commanders killed; a parallel entry places the same claim at Nahal Oz inside Israel's Southern District, alongside a reported clash there — the geolocation conflict is unresolved. In the West Bank, settlers reportedly attacked Palestinians and activists at more than a dozen sites (including al-Rashaida, Turmus Ayya, Qusra, Jalud, and Zububa), with over 20 wounded, olive groves uprooted, and a home seizure near Jenin. Settlers also entered Hebron's Old City under IDF escort. A GDELT-only clash signal in Jerusalem lacks any corroborating detail.

The northern Gaza strike cluster and central Gaza artillery indicate continued kinetic pressure on Gaza City, Jabalia, and Deir al-Balah axes. The West Bank settler incidents, if borne out, represent a geographically broad rather than localized escalation, and the Hebron Old City movement suggests coordinated force protection for settler access.

Watch for second-source confirmation of the Hamas commander strike and whether it localizes to Gaza or Nahal Oz. Monitor northern Gaza (Jabalia, Beit Lahiya) for repeat drone strikes, and central Gaza (al-Bureij) for sustained artillery. In the West Bank, watch Hebron, Jenin-area villages, and Ramallah-district hilltops for follow-on settler incidents; renewed activity would indicate the weekend pattern is consolidating rather than isolated.

Russian rear-area strikes on Kharkiv and Sumy cities produced the day's civilian toll, while Moscow's verified claim to have captured Kostiantynivka was publicly refuted by Kyiv and partially contradicted by Russia's own MoD. Ukrainian deep strikes reached Belbek airfield in Crimea.

Kharkiv Oblast activity rose to three logged strikes (baseline 1.4/day): drone attacks in Kharkiv city's Kyiv district injured three, a strike on Bohodukhov killed two and damaged commercial premises, and Ukraine's 41st Brigade struck an apartment block and factory in Russian-held Kupiansk. In Sumy, a KAB glide-bomb hit a central street, killing four (including a child) and wounding 33. Zaporizhzhia city saw a single strike with five wounded, in line with baseline. In Donetsk, Gerasimov and Putin declared Kostiantynivka captured — a verified claim publicly refuted by the AFU General Staff and Zelensky, and undercut by Russia's own MoD telling TASS that fighting continued; geolocated footage separately showed Russian dead near Novotorets'ke. Crimea registered a rare kinetic event: GUR-released video of a UAS strike on a MiG-29 at Belbek.

The Kostiantynivka episode is the period's key signal: a top-level Russian capture claim contradicted within hours by its own defence ministry points to political messaging outrunning the tactical picture. The Kharkiv uptick and the Sumy KAB strike show sustained pressure on northeastern urban centres. The Belbek strike, though single-event, extends demonstrated Ukrainian deep-strike reach against Crimean airbases.

Watch for follow-on Russian statements or independent geolocation from Kostiantynivka; sustained Ukrainian control indicators would contradict the capture claim. Watch Kharkiv Oblast for whether the three-strike day consolidates into a trend. Monitor Belbek for post-strike imagery indicating MiG-29 damage assessment, and Sumy for further KAB employment against urban centres.

All five reports in the period are single-sourced and unverified, but they cluster around a possible Damascus judicial bombing, a reported ceasefire breach on Suwayda's western axis, and PMF-linked brigade movements into Rif Dimashq — none independently corroborated.

Activity dispersed away from the Daraa-heavy 7-day baseline (0.7/day) toward Damascus and its hinterland. Rif Dimashq shows two unconfirmed reports of Popular Mobilization Forces elements — the Derik/Derek Brigade — preparing to relocate to al-Nabk camp for a training course tied to Syrian Army integration, following a reported prior Qamishli Brigade rotation. In central Damascus, a single-sourced update raises the Palace of Justice bombing death toll to 13 with no actor attribution. On the western axis of Suwayda, a reported ceasefire breach is attributed by the source to SOHR, with no details on actor, munition, or casualties. In Idlib, International Coalition aircraft were reported over Maara countryside without engagement. All five items carry UNCONFIRMED confidence.

If the Rif Dimashq movement reports hold, they would indicate continued formalization of former PMF-aligned units into the Syrian Army command structure via a standardized training pipeline at al-Nabk. The Palace of Justice casualty update, if verified, would mark a rare mass-casualty attack on state judicial infrastructure in the capital. The Suwayda breach report, if substantiated, would signal fragility in the local ceasefire framework. Coalition overflight in Maara, absent kinetic activity, is ambiguous but notable given no prior baseline for Idlib in the period.

Watch for second-source confirmation of the Palace of Justice toll and any claim of responsibility. Monitor al-Nabk camp reporting for corroboration of brigade arrivals. Watch Suwayda's western axis for follow-on strike reporting that would indicate a sustained breach rather than an isolated incident. Track Maara-area overflight patterns; a shift to kinetic activity would indicate escalation.

All four reportable items this period are single-sourced and unverified, but they cluster around a single theme: Russian hardening of civilian maritime and rail interfaces along the Baltic flank, alongside a Belarusian claim of a Ukrainian attack on a bus.

With no prior baseline, three of four items concentrate in the Baltic maritime and border domain. Estonian border guards reportedly photographed large-caliber machine guns mounted on the Gazprom LNG tanker Marshal Vasilevskiy in the Baltic Sea, described as the first arming of a Russian civilian vessel with heavy weapons in the region; a parallel report claims at least 24 passengers aboard with Russian military, police, intelligence, or special-service backgrounds. Separately, Russia announced the temporary closure of multiple railway border crossings with Latvia, Estonia, and Finland effective 1 July, suspending movement of persons, vehicles, and cargo. In Belarus, Security Council Secretary Volfovich claimed a bus was attacked by Ukraine, with drivers in serious condition; no location, weapon, or timing was provided. All four events are single-sourced and unconfirmed.

Two clusters, if corroborated, would represent meaningful shifts: militarization of a Gazprom-flagged commercial tanker transiting Estonian-monitored waters blurs the civilian/military line at sea, while a coordinated rail closure with three NATO members compresses a remaining legal transit channel on the eastern flank. The Belarusian bus claim, absent any supporting detail, currently functions primarily as an information item rather than a kinetic indicator.

Watch for independent imagery or second-source confirmation of armament aboard the Marshal Vasilevskiy — corroboration would indicate a deliberate policy shift, not a one-off. Watch for formal Latvian, Estonian, and Finnish responses to the rail suspension; reciprocal measures would indicate escalation beyond a bureaucratic step. Watch for any Belarusian follow-up evidence on the alleged bus attack; continued absence of detail would indicate a narrative rather than an incident.

All four reported events in the period are single-sourced and unverified, but they cluster into two coherent signals: renewed maritime attacks on shipping in the Red Sea approaches to Yemen, and the reported inauguration of Sana'a–Tehran civilian flights under Houthi announcement.

No 7-day baseline exists, so all activity registers as new. Two unconfirmed maritime incidents were reported within roughly one hour: a UKMTO Warning 079-26 citing an attack in the maritime domain off Al Hudaydah, and a British military report of a cargo ship attacked by unidentified assailants in the Red Sea. Both lack actor, weapon, and vessel detail. Separately, al-Masira reported an Iranian civilian aircraft landing at Sana'a International Airport, described as the opening of a Sana'a–Tehran air link, accompanied by a Houthi statement threatening military confrontation with Saudi forces over any interdiction. GDELT also flagged unspecified fighting in Marib via a Xinhua-sourced signal, with no actors, locations, or casualties identified.

The two maritime reports, if corroborated, would mark a resumption of anti-shipping activity in the Red Sea corridor after a quiet baseline. The Sana'a arrival is politically significant regardless of physical scale: it frames Houthi-controlled airspace as operationally linked to Tehran and pre-positions a Houthi casus belli against Saudi or coalition interference. The Marib signal is too thin to weight, but any confirmed ground fighting there would break the recent absence of reported activity.

Watch for UKMTO or EU Aspides follow-on advisories corroborating the Red Sea and Al Hudaydah incidents; multi-source confirmation would indicate a genuine tempo shift. Monitor whether additional Iran–Sana'a flights are logged or challenged, which would indicate the air link is operational rather than symbolic. Watch Marib for named-unit or casualty reporting that would upgrade the GDELT signal beyond noise.

Two partially corroborated maritime incidents in a single 24-hour window — an armed approach on a cargo ship off Al-Hudaydah and reported Iranian coercion of commercial traffic in the Strait of Hormuz — mark a simultaneous uptick at both ends of the Arabian Peninsula chokepoint chain.

Both Red Sea off Al-Hudaydah and Hormozgan Province registered activity roughly 9x their 7-day baselines of 0.1 events/day. UKMTO logged a distress call from a cargo vessel approximately 30 nautical miles southwest of Al-Hudaydah reporting attack by unknown armed men — investigators have not attributed the incident. Separately, reporting cited by ISW describes Iran using threats and force to push commercial vessels into its declared traffic separation scheme in the Strait of Hormuz, with traffic reportedly diverting along Oman's coast. Both clusters are partial (two-source) and unattributed in the Red Sea case. No activity was reported this period in South Lebanon, West Azerbaijan, Kermanshah, Tehran, Quneitra, Bahrain, Erbil, Blue Nile, or Northern District against their baselines.

Concurrent pressure on Bab el-Mandeb approaches and the Strait of Hormuz stresses the two maritime corridors most sensitive to Iran-aligned activity. The Hormuz reporting, if sustained, indicates a shift from transit harassment toward attempted regulatory coercion of commercial shipping — a qualitatively different lever than interdiction. The Al-Hudaydah incident's unknown-armed-men framing leaves attribution open between Houthi elements and criminal actors, which itself complicates insurer and flag-state response.

Watch for UKMTO or EUNAVFOR follow-up attribution on the Al-Hudaydah distress call; a claim of responsibility would clarify whether Houthi targeting has resumed. Watch AIS patterns in the Strait of Hormuz for further diversion toward Omani waters, which would indicate commercial operators are treating Iranian coercion as durable. Watch for any spillover reporting from Hormozgan or Tehran Province tying the maritime posture to onshore signaling.

The reporting period produced no verified or partially corroborated activity in Sudan. Two single-sourced, unconfirmed clash reports — in Al-Fashir (North Darfur) and Al-Obeid (North Kordofan) — are the only signals, and neither meets the threshold for confirmed escalation.

Against a low 7-day baseline (North Darfur 0.4/day, North Kordofan 0.3/day, Blue Nile 0.1/day), the period logged one unconfirmed clash in each of Al-Fashir and Al-Obeid, producing nominal percentage spikes (+150% and +233%) that are artifacts of a small denominator rather than a demonstrated shift. Both reports are single-sourced and unverified. The Al-Fashir item lacks any detail on actors, casualties, or weapons. The Al-Obeid item is derived from a GDELT CAMEO-18 flag linked to a UN warning of a "new human rights catastrophe" in the city, which suggests ongoing armed violence but does not corroborate a discrete engagement. Blue Nile shows no reported activity.

Both flagged locations sit on established SAF–RSF contest lines: Al-Fashir remains the last major SAF-aligned holdout in Darfur, and Al-Obeid is the strategic node controlling approaches into Khartoum and Kordofan. Even unverified signaling around either city is operationally relevant because a genuine escalation at either location would carry disproportionate weight for humanitarian access and frontline geometry. However, on the evidence available in this period, no such escalation is substantiated.

Watch for second-source corroboration of the Al-Fashir clash — imagery, SAF or RSF claims, or humanitarian reporting would upgrade confidence. Watch for follow-on UN or OCHA statements referencing Al-Obeid; further human rights language paired with named incidents would indicate the CAMEO-18 flag reflects a sustained pattern rather than an isolated data artifact. Continued silence from Blue Nile would indicate the baseline holds.

Reporting for the 24-hour window is thin: a single unconfirmed assault-coded signal near Ashkelon is the only item on the wire, insufficient to establish a shift in the operational picture.

Against a 7-day baseline of roughly 0.1 events/day in the Northern District and no prior baseline activity in the Southern District, one single-sourced and unverified report flagged an assault-type incident in the Ashkelon area on 4 July. The item derives from an automated GDELT CAMEO code-18 tag with no actor attribution, casualty figures, or weapon-system detail, and no corroborating open-source reporting has surfaced in the period. The Northern District produced no reported events in the window.

With only an unconfirmed machine-tagged signal to work from, no operational or strategic inference is defensible for this period. Ashkelon sits within historic rocket-threat range of Gaza, so any genuine kinetic activity there would carry escalation weight — but the current reporting does not support that read. The absence of Northern District activity is consistent with, not a departure from, the low baseline.

• Watch for human-sourced corroboration of the Ashkelon-area report (local media, IDF Home Front Command alerts, municipal statements); confirmation would reclassify the signal from noise to a discrete kinetic event.
• Watch for follow-on CAMEO-tagged clusters in the Southern District; repeat signals in the same geography would indicate a genuine uptick rather than an isolated automated artifact.
• Watch for any Northern District reporting above the 0.1/day baseline, which would indicate a broadening of the theater's activity profile.

A partially corroborated PDF attack in Monywa on 30 June killed seven, including a People's Security Force (PSF) leader and two civilians — the sole reported incident this period in Sagaing Region and a signal of intra-resistance factional violence.

Sagaing Region logged one event against a 7-day baseline of 0.1/day, a nominal spike driven entirely by the Monywa clash. The incident is two-source but partial: a People's Defence Force element struck a PSF position, killing the PSF leader and two civilians alongside four other fatalities. No other verified activity was reported in the theater during the period, so the delta reflects a single data point rather than a broader escalation pattern.

Monywa sits in the Sagaing resistance heartland, where PDF and PSF elements have generally operated in parallel against the junta. A lethal PDF-on-PSF strike — if the attribution holds — points to unresolved command, territorial, or legitimacy disputes inside the anti-junta coalition rather than regime action. Civilian casualties in an intra-resistance incident also carry reputational costs for local PDF authority and could complicate NUG-aligned governance claims in central Sagaing.

• Watch for follow-on statements from the NUG, local PDF battalions, or PSF representatives regarding Monywa; public attribution or disavowal would clarify whether this was sanctioned or rogue action.
• Monitor Monywa and surrounding townships for retaliatory clashes between resistance factions; a second incident would indicate the dispute is structural rather than isolated.
• Track junta information operations exploiting the incident; amplification would suggest regime assessment of exploitable resistance fractures.
• Absence of corroborating reporting within 72 hours would warrant downgrading confidence in the current casualty figures.

A partially corroborated cruise-missile strike on Votkinsk (Udmurt Republic) marks the only reported activity in the period and represents a roughly 900% single-day spike over the oblast's 7-day baseline, extending Ukrainian deep-strike reach approximately 1,000 km beyond the frontier.

Compared with the 7-day baseline — dominated by low-tempo activity around Moscow (0.6/day), St. Petersburg and Nizhny Novgorod (0.3/day each) — the reporting window contains a single geolocated event: smoke plumes over Votkinsk following a reported salvo of Ukrainian FP-5 "Flamingo" cruise missiles. The event is single-sourced and rated partial; imagery was geolocated with a northwest-facing vantage, but damage assessment, target identification, and impact count remain unconfirmed. No activity was reported in Moscow, St. Petersburg, Nizhny Novgorod, Penza, Leningrad, or Zaporizhzhia during the window, a quiet baseline against which the Udmurtia spike stands out.

Votkinsk hosts production infrastructure associated with Russian strategic and tactical missile systems, making any credible strike on the town operationally significant regardless of confirmed damage. The reported use of the FP-5 "Flamingo" — if borne out by further sourcing — would corroborate Ukrainian fielding of a long-range cruise missile capable of reaching deep Volga-Ural industrial nodes previously outside routine threat range. The absence of parallel activity elsewhere concentrates analytic attention on this single vector.

Watch for additional imagery or secondary sourcing from Votkinsk that would corroborate impact points, munition type, and any industrial damage. Russian MoD acknowledgement, local emergency-services statements, or commercial satellite passes over the Votkinsk plant area would upgrade confidence. A second strike east of the Volga within the window would indicate a sustained deep-strike campaign rather than an isolated shot; continued quiet across Moscow and St. Petersburg would reinforce that read.

Reporting for the 24-hour period is thin: a single unconfirmed assault signal near La Guaira (Vargas) is the only item on the wire, with no verified or partially corroborated activity elsewhere in the theater.

There is no 7-day baseline to compare against, so any activity registers as a nominal shift rather than a trend. The sole reported item is a single-sourced, unverified GDELT-derived assault signal in La Guaira, Vargas (CAMEO 18, 3 mentions, tone -5.29). No verified or partially corroborated events were recorded in the period. No other oblasts registered activity.

With only one uncorroborated machine-coded signal, the period offers no basis for operational or strategic inference. La Guaira hosts Venezuela's principal port and Simón Bolívar International Airport, so any confirmed security incident there would carry logistical significance — but the current signal does not meet that threshold and should be treated as noise pending human-sourced corroboration.

• Watch for second-source reporting (Venezuelan press, local social media, port authority notices) on the La Guaira assault signal; independent confirmation would upgrade it from a GDELT artifact to a discrete incident.
• Watch for any follow-on security activity around La Guaira port and Maiquetía airport corridors; movement restrictions or additional GNB deployments would indicate the initial signal reflected a real event.
• Watch for whether reporting volume in Vargas remains at one event or expands, and whether new signals appear in adjacent Distrito Capital; a cluster would indicate a localized incident rather than isolated noise.
• Absent corroboration within 72 hours, the La Guaira signal should be discounted.