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

Russian aerial strikes concentrated on Kharkiv and rear cities (Kyiv, Odesa, Zaporizhzhia) while the Kremlin claimed capture of Kostiantynivka in Donetsk — a politically significant assertion that remains single-side sourced.

Kharkiv oblast saw three separate strike events in 24 hours (up ~76% vs baseline), including a Shevchenkivskyi district airstrike that killed one and injured 18 (four children), a Nemyshlianskyi district missile strike damaging ~20 homes, and a broader 24-hour salvo across the city and 12 settlements reported by regional authorities — all partially sourced. Kyiv City registered a verified drone strike injuring two, an outlier against its low baseline. Odesa and Zaporizhzhia each recorded partially sourced strikes with civilian casualties, both above baseline. In Donetsk, activity dropped in event count but included a Kremlin claim via Peskov that Kostiantynivka has fallen; this is attributed to Russian spokesperson statements only and not independently corroborated in the event set. Ukrainian UAV strikes on tankers and dry cargo vessels in the Azov Sea mark a maritime data point framed against Russian Black Sea Fleet protection failures.

The Kharkiv cluster, combined with strikes on Kyiv, Odesa, and Zaporizhzhia, indicates a broad rear-area air campaign rather than front-focused fires. One event set references major mutual strikes on the eve of a NATO summit, situating the tempo in a political window. The Kostiantynivka claim, if substantiated, would mark a significant Donetsk line shift; as presented it is a Russian information operation pending Ukrainian or third-party confirmation.

Watch for Ukrainian General Staff or independent geolocation addressing Kostiantynivka control — silence or contradiction would indicate the Kremlin claim is premature. Monitor whether Kharkiv strike tempo persists past 48 hours and whether Azov Sea maritime strikes recur, which would indicate a sustained Ukrainian interdiction pattern.

A US–Iran kinetic exchange centered on the Strait of Hormuz and Iran's southern coast has spilled into the wider Gulf within 24 hours, with reported Iranian missile/drone salvos against Kuwait and Bahrain and multiple tanker strikes in the Strait.

Hormozgan Province activity rose sharply against the 1.0/day baseline. US airstrikes hit IRGC Navy speedboats at the Port of Sirik (verified) and are reported to have set Shahid Haghani port in Bandar Abbas ablaze (partial, six sources). In parallel, partial reporting describes an unidentified drone striking a tanker near the Strait of Hormuz, a follow-on Iranian strike on three tankers, and a later attack on Saudi- and Qatari-flagged tankers transiting the Strait — condemned by Yemen's foreign ministry. Explosions were reported in Bushehr (partial, cause unspecified), a province typically at 0.1/day. Spillover into the Gulf is new relative to baseline: Kuwait's military said it intercepted a missile and drone attack, and air raid sirens sounded in Bahrain amid reports of Iranian retaliation for US strikes. Origins, weapon types and casualties across the Gulf incidents remain unconfirmed.

Only the Sirik strike on IRGC naval assets is verified; the tanker and Gulf-capital incidents are partial and single-thread in places, but converge on a pattern of Iranian maritime retaliation and Gulf-wide exposure. Repeated tanker strikes in the Strait — the chokepoint for roughly a fifth of seaborne oil — and reported air defense engagements over Kuwait and Bahrain indicate the conflict has moved beyond bilateral US–Iran targeting to threaten Gulf state territory and commercial shipping.

Watch Hormozgan for further US strikes on Iranian naval infrastructure beyond Sirik and Bandar Abbas; sustained activity would indicate a campaign rather than a single salvo. Monitor UKMTO advisories and AIS anomalies in the Strait — additional tanker incidents would indicate Iran is institutionalizing maritime interdiction. Track Kuwaiti and Bahraini official statements and any Saudi or Qatari response to the tanker strikes; attribution claims would indicate widening state involvement. Clarification on the Bushehr explosions would indicate whether that province is now a target set.

All seven reported events in the period are single-sourced and unconfirmed, but cluster around reported Israeli airstrikes in Gaza during a purportedly active ceasefire and a set of GDELT-derived "fighting/assault" flags inside Israel proper that require caution before treatment as conflict activity.

Gaza Strip activity registered three reported events against a 7-day baseline of 0.1/day, driven by unconfirmed reporting of Israeli airstrikes on Khan Younis (Mawasi area), western Gaza City near a displaced-persons tent encampment, and a third Khan Younis location, with three Palestinians reportedly killed. A separate overnight strike report cites three additional Palestinian fatalities in Gaza. Both accounts explicitly frame the strikes as occurring despite an eight-month ceasefire — a notable characterization if corroborated. Two further Gaza items are GDELT CAMEO "fighting/assault" flags with no actor, weapon, or casualty detail. Inside Israel, GDELT-derived flags appeared in Ben Gurion and Tayibe (Central District) and Shifa (Northern District) — locations with no prior baseline. The Tayibe item is tagged as crime-category reporting, suggesting a civil incident rather than conflict activity.

If the Gaza strike cluster is corroborated, it would represent a material breach of the reported eight-month ceasefire and the first meaningful uptick in Gaza kinetic reporting against a near-zero baseline. The Israel-interior GDELT flags are low-confidence and likely reflect automated miscategorization of criminal or civil incidents rather than a new front; treating them as conflict events without corroboration would distort the picture.

Watch for second-source confirmation of the Khan Younis and Gaza City strike reports from medics, health ministry statements, or IDF acknowledgement — corroboration would indicate the ceasefire framing is under active strain. Watch whether Central and Northern District GDELT flags attract any narrative reporting; absence would indicate automated-classification noise. Monitor Hebron and Ramallah, which recorded no events this period against their standing baseline.

All seven reported events in the period are single-sourced and unconfirmed, but the concentration in North Kordofan — five incidents against a 0.4/day baseline — marks a sharp reported escalation centered on drone strikes and fighting around El-Obeid.

North Kordofan reporting jumped to five events versus a 7-day average of 0.4/day. Two overlapping unconfirmed reports describe drone strikes killing roughly 15 civilians in the Kordofan region, and a separate unconfirmed account attributes at least 15 civilian deaths — including women travelling to a wedding — to two drone strikes on vehicles, framed by the Emergency Lawyers group as consistent with a pattern of infrastructure-linked targeting. Fighting was also reported in El-Obeid, where the Arab League warned of a looming humanitarian and security catastrophe, and more generically elsewhere in Kordofan. Outside North Kordofan, single unconfirmed clash reports emerged in Al-Andaraba (White Nile) and West Darfur, both areas without a prior 7-day baseline. All items are single-sourced.

If the North Kordofan reporting holds, it would indicate a shift toward drone-delivered mass-casualty strikes on civilian vehicles alongside ground fighting pressuring El-Obeid, a key state capital and logistics node. The parallel unconfirmed reports in White Nile and West Darfur suggest activity is not geographically contained, though corroboration is absent.

Watch for second-source corroboration of the El-Obeid drone strikes and casualty figures; independent confirmation would elevate these from single-source claims. Monitor whether fighting reports around El-Obeid expand into sustained urban engagement, which would indicate a contested shift at the city. Track whether the White Nile and West Darfur clash reports gain additional sourcing, which would indicate broader front activity rather than isolated incidents.

All four reported incidents across Israel/adjacent zones in this 24-hour window are single-sourced and unverified. No verified activity is available to characterize the operational picture.

Reporting volume rose against a near-zero 7-day baseline, but every data point is unconfirmed. Two GDELT-flagged "fighting" signals reference the Gaza Strip vicinity (coordinates 31.5, 34.75), both single-sourced with no actor, weapon, or casualty detail. A separate GDELT-flagged clash in Sakhnin (Northern District) is sourced to a Jerusalem Post item and represents a nominal 900% spike over the 0.1/day baseline — but off a single event and without corroboration. In Kodna, southern Quneitra countryside, local sources reported Israeli forces establishing a temporary checkpoint with ID inspections, described as a new incursion; also single-sourced.

The clustering of unverified GDELT "fighting" pings around the Gaza Strip, combined with a reported checkpoint push into southern Quneitra and a northern Israel clash signal, would — if corroborated — suggest simultaneous activity across three distinct fronts (Gaza periphery, Golan-adjacent Syria, and Israel's north). At present the evidence base does not support that characterization; the Northern District "spike" is an artifact of a very low baseline and one uncorroborated wire-flagged item.

Watch for second-source confirmation of the Sakhnin fighting report; independent corroboration would move it from GDELT-artifact to a genuine internal-security signal. Watch for follow-on reporting on the Kodna checkpoint — persistence or expansion would indicate a sustained Quneitra-countryside posture rather than a transient inspection. Watch whether the two Gaza-vicinity GDELT pings resolve into named incidents with actors identified; continued anonymous clustering at identical coordinates would indicate automated-feed noise rather than distinct events.

All four reported events in this period are single-sourced and unverified, but they cluster around a possible SAC reinforcement effort at Myawaddy (Kayin) and a parallel repositioning toward Chin State and central Myanmar. Treat as watch items pending corroboration.

No 7-day baseline is available, so all activity registers as new signal rather than measurable delta. Two unconfirmed reports describe fighting at Min Let Pan village in Myawaddy Township, Kayin State, with the later report claiming SAC deployed roughly 3,000 reinforcements against Karen forces and cross-border fire into Thailand prompting Thai border reinforcement and closure of informal crossings. A separate unconfirmed report describes SAC shelling of Shwemaw in Sagaing Region, killing one woman and wounding eight, with residents stating no clashes were ongoing locally. A fourth unconfirmed report cites leaked directives indicating SAC troop repositioning to Chin State and central Myanmar, with police, firefighters, and civil servants reportedly registered as auxiliary forces. None of these reports are corroborated by a second source.

If the Myawaddy reports hold, the scale of reinforcement and cross-border spillover would mark a significant SAC effort to retake a contested border node, with direct implications for Thai border posture. The Chin/central repositioning report, if accurate, would suggest SAC is thinning other fronts and formalising non-military personnel as combatants — a manpower stress indicator. The Shwemaw shelling, if confirmed, fits a pattern of strikes on areas without active engagement.

Watch for second-source confirmation of the 3,000-strong Myawaddy reinforcement and any further Thai border security statements. Independent reporting on Shwemaw casualties would upgrade that incident. Corroboration of the auxiliary-force directive in Chin State would indicate a substantive SAC manpower shift.

All four reported events across the NATO flank this week are single-sourced and unverified, but they cluster around a claimed multi-site UAV attack on Leningrad Oblast port and military infrastructure on 6 July, alongside a separate Belarusian claim of a Ukrainian attack on a bus.

No baseline exists for the prior 7-day window, so all activity is a step-up from a null reference. Two overlapping unconfirmed reports describe a UAV strike on 6 July against Ust-Luga port and the Luzhsky training range, with a wider account extending the target set to Vysotsk and claiming 56 UAVs intercepted plus internet outages in Saint Petersburg. A separate unconfirmed 7 July report attributes a drone strike on a Leningrad-region port oil terminal, though the signal was geocoded to Pskov, suggesting a possible duplicate of the Ust-Luga cluster rather than a distinct Pskov event. In Belarus, Security Council Secretary Volfovich claimed on 2 July that drivers of a bus allegedly attacked by Ukraine were in serious condition; no location, timing, or weapon details were provided.

The Leningrad cluster, if borne out, would represent simultaneous targeting of a major Baltic export node (Ust-Luga), a secondary port (Vysotsk), and a military polygon — a broader Russian rear-area target set than routine strike reporting. The Belarusian statement, uncorroborated and light on specifics, fits a pattern of Minsk-attributed incident claims that shape domestic threat framing. None of this is verified.

Watch for independent imagery or shipping-data confirmation of damage at Ust-Luga, Vysotsk, or the Luzhsky range; corroboration would upgrade the Leningrad cluster from single-sourced. Watch for any Belarusian follow-up specifying location or forensic detail on the alleged bus attack; continued absence would keep the claim in the unverifiable category. Watch whether the Pskov-geocoded oil terminal report resolves as a duplicate or a distinct site.

Ukrainian long-range drone strikes hit at least three Russian regions overnight, with verified impacts on a military airfield in Borisoglebsk (Voronezh) and Nizhnekamsk (Tatarstan), and partially corroborated strikes on the Saratov oil refinery.

Activity shifted eastward and deeper into Russia relative to the 7-day baseline. Tatarstan and Voronezh each recorded one event against a 0.1/day baseline, and Saratov logged two events against 0.3/day. The Borisoglebsk strike (verified, 3 sources) targeted a military airfield reportedly hosting Su-34, Su-35, and Su-30SM airframes. The Nizhnekamsk strike is verified across four sources but details on weapon type, damage, and casualties remain absent. In Saratov, partial reporting describes drone strikes igniting the Saratov oil refinery, alongside separate reports of "arrivals" elsewhere in the city — both single-night, three-source but not independently verified beyond initial claims.

The Borisoglebsk airfield strike, if damage is confirmed, targets frontline tactical aviation assets rather than rear logistics. The Nizhnekamsk and Saratov strikes extend the pattern of reaching petrochemical and refining infrastructure over 700–1,000 km from the border. Together the four events concentrate in a single overnight window across widely separated oblasts, consistent with a coordinated deep-strike package rather than dispersed harassment.

Watch for post-strike imagery from Borisoglebsk indicating airframe losses or runway damage, which would clarify whether the airfield was degraded or merely targeted. Monitor Saratov refinery throughput reporting and fire-duration claims to corroborate the partial sourcing. Watch Tatarstan channels for follow-on detail on the Nizhnekamsk target set; continued silence would itself indicate information control around a sensitive petrochemical node.

A single partially corroborated grenade fatality in Damascus is the only reportable incident for the period, leaving the theater quiet but with the capital marginally above its 7-day baseline.

One partially verified event: a young man died from wounds sustained in a hand grenade incident in Damascus on 7 July. Two sources reported the incident, but perpetrator, target, and circumstances remain undescribed. Damascus recorded one event against a 7-day average of 0.7/day, a nominal uptick of roughly 43% driven entirely by this single data point. As-Suwayda, Deir ez-Zor, and Rif Dimashq produced no reportable activity during the window, consistent with — or below — their low baselines.

The Damascus incident is single-incident and low-fidelity: two sources agree a death occurred, but nothing in the reporting distinguishes criminal violence, a personal dispute, or a low-level attack. With no attribution and no corroborating activity elsewhere in the country, the event does not by itself indicate a shift in the security environment. The statistical rise against baseline is an artifact of small numbers rather than a signal of escalating tempo in the capital.

• Watch for follow-on reporting on the Damascus grenade incident that clarifies attribution or target; identification of a political or factional actor would indicate this was more than isolated street violence.
• Watch for additional small-arms or explosive incidents inside Damascus city; a second event within 72 hours would indicate a possible pattern rather than a one-off.
• Watch As-Suwayda and Deir ez-Zor for any resumption of activity; sustained silence would suggest the baseline itself is softening.

The reporting period contains no verified or partially corroborated activity in Venezuela. A single unconfirmed assault signal near La Guaira is the only item on the board and does not, on its own, indicate a shift in the theater.

No baseline exists for the prior 7 days, so no delta can be established. One unconfirmed clash signal was logged in La Guaira, Vargas, on 5 July, derived from a single GDELT-style assault code with three mentions and a mildly negative tone. It is single-sourced and unverified, with no corroborating open-source reporting tied to the event. No other oblast recorded activity in the period.

With zero verified events and only one uncorroborated signal, the period provides no basis for assessing operational or strategic change in Venezuela. The La Guaira signal is notable only because Vargas hosts Simón Bolívar International Airport and the country's principal Caribbean port complex, meaning any confirmed unrest there would carry outsized logistical implications. Absent corroboration, however, the signal should be treated as noise rather than as evidence of a trend.

Watch for follow-on reporting from Venezuelan or regional outlets that would corroborate or refute the La Guaira assault signal; a second independent source would move it from noise toward a tracked incident. Monitor the Vargas port and airport corridor for any security-force posture changes, which would indicate the initial signal reflected a real disturbance. Watch for the emergence of activity in other states — its continued absence would reinforce that the period represents a genuine lull rather than a reporting gap.

A single unconfirmed counter-terrorism raid in Aden is the only reported activity in the period; kinetic reporting across Yemen otherwise fell to zero, including along the Al Hudaydah corridor that carried the 7-day baseline.

Reporting volume dropped below the 7-day baseline. Al Hudaydah, which had run at roughly 0.1 events/day, produced no reported incidents in the window. The only logged activity is a single-sourced and unverified security raid in the Al-Musaibeen area of Dar Saad district, northern Aden, in which local security agencies reportedly seized SEMTEX, explosive belts, and an artillery shell converted into an IED, attributing the cache to an individual identified by police as "terrorist Amjad Khaled." Aden had no prior baseline activity in the preceding week, so even an unconfirmed report constitutes a shift in where reporting is originating rather than a confirmed escalation.

If the Dar Saad seizure is corroborated, it would indicate that finished IED components — including a military-grade high explosive and ready-to-wear suicide vests — were staged inside greater Aden rather than in contested peripheries. That would speak to urban plotting capacity in the interim capital. Because the report is single-sourced, it currently supports only a monitoring hypothesis, not a confirmed threat picture. The absence of Al Hudaydah reporting does not itself imply de-escalation; it may reflect a reporting gap.

• Watch for second-source confirmation of the Dar Saad raid, particularly imagery of the seized materiel or an official Interior Ministry statement; corroboration would upgrade the Aden urban-threat signal.
• Watch for follow-on detentions or named-network disclosures tied to the "Amjad Khaled" attribution; expansion would indicate a broader cell rather than an isolated cache.
• Watch Al Hudaydah for resumption of baseline-level incidents; continued silence would suggest a reporting gap rather than a genuine lull.