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

Ukrainian long-range drone operations against Russian territory dominated the period, with two Russian MoD tallies (144 and 178 UAVs intercepted) spanning at least ten regions and a reported strike on the Nizhnekamsk refinery in Tatarstan — all single-sourced. Deputy PM Novak's public acknowledgement of refinery-driven fuel shortages is the period's most consequential signal.

Reporting volume shifted notably against the 7-day baseline. Dagestan produced five unconfirmed "fighting" signals (including Khasavyurt) from GDELT/Kavkaz-Uzel aggregation with no prior baseline activity — a cluster, but entirely single-sourced and lacking actor, scale, or location detail. Bryansk generated two separate signals (a discrete clash report and inclusion in the overnight drone sweep) versus no baseline. Two consecutive MoD drone-intercept tallies (144 overnight into 10 Jul; 178 overnight into 11 Jul) name Bryansk, Kaluga, Rostov, Smolensk, Tver, Moscow, Krasnodar, Crimea, and adjacent seas — a geographic footprint wider than the baseline distribution. A reported refinery strike at Nizhnekamsk (Tatarstan) and a separately reported strike on an unspecified refinery ~2,500 km from Ukraine (attributed to Zelensky) coincide with Novak's admission of shortages and 20–30% demand surge. St. Petersburg military commissariats began recruiting mobile fire groups for anti-drone defense, and Kronstadt generated a single unverified "fighting" signal.

Every event is unconfirmed, but the refinery cluster is internally corroborated by a Russian official admission, making the economic-effects thread the strongest signal of the period. The St. Petersburg MFG recruitment and Sollers ST6/Katran deployment indicate resource commitment to rear-area drone defense consistent with the reported strike depth.

Watch for second-source confirmation of the Nizhnekamsk fire and identification of the ~2,500 km refinery; either would materially upgrade the strike-depth picture. Watch Dagestan for any non-GDELT reporting clarifying the five clash signals — sustained silence would suggest aggregation noise. Watch for further regional anti-drone procurement announcements beyond St. Petersburg.

Ukrainian maritime drone operations against Russian shipping in the Sea of Azov have forced Russia to suspend traffic through the Kerch Strait and Azov-Don Canal, while Russian strikes continued against Zaporizhzhia, Kyiv, Odesa and Kherson.

The period's defining shift is a corroborated Ukrainian campaign against Russian vessels in the Azov Sea and Taganrog Bay, where at least four ships were reported hit. Russia responded by suspending vessel-passage applications through the Kerch Strait and halting navigation on the Azov-Don Canal — a logistics disruption not present in the 7-day baseline. Ukrainian footage claims cumulative damage to tankers over a three-day window. On the Ukrainian side, Zaporizhzhia (verified) was struck by guided aerial bombs, killing one and injuring three; Kyiv saw at least five explosions overnight (partial, nine sources); Odesa infrastructure was hit with casualties reported; and a drone strike in Kherson wounded a civilian. Donetsk Oblast events (3) ran 50% above baseline, including reported fighting in Kostyantynivka and Ukrainian 237th UAS Battalion FP-2 drone strikes near Donetsk city.

The Azov/Taganrog cluster is the most operationally significant development: it extends Ukraine's demonstrated maritime strike reach into a body of water Russia has treated as a rear area, and the Kerch Strait/Azov-Don Canal suspensions impose measurable costs on Russian military and commercial logistics. Simultaneous strikes on Zaporizhzhia, Kyiv, Odesa and Kherson indicate Russian long-range fires remain undegraded despite the maritime pressure.

• Watch for resumption or continued closure of Kerch Strait and Azov-Don Canal traffic; prolonged suspension would indicate sustained Ukrainian sea-denial effect.
• Watch Taganrog Bay and Rostov coastal areas for follow-on strikes or visible Russian air-defense repositioning.
• Watch Kostyantynivka for confirmation of the reported clash and any line-of-contact movement in Donetsk Oblast.
• Watch Odesa and Kyiv for repeat overnight strike waves, which would indicate a sustained retaliatory tempo.

Reporting this period is dominated by unconfirmed Ukrainian drone strikes against Leningrad Oblast port and range infrastructure, alongside single-sourced signals of NATO ISR repositioning to the Baltic flank. No verified or partially corroborated events were recorded; all claims below remain single-sourced.

Against a null 7-day baseline, the largest cluster is a reported strike wave on 6 July against the Port of Ust-Luga, Vysotsk, and the Luzhsky Polygon in Leningrad Oblast, with the regional governor citing 56 UAVs downed and infrastructure damage at all three sites, plus internet outages in Saint Petersburg — a claim echoed by a second, thinner report the same morning and by a 7 July item geocoded to Pskov but textually referring to a Leningrad port oil terminal. All three remain single-sourced and unverified. Three GDELT-derived "fighting" pings in Estonia on 8 July share identical coordinates (59°N, 26°E) and appear to reflect a single low-confidence signal replicated across sources rather than three distinct incidents. NATO ISR activity is noted via an RC-135W near Kaliningrad on 8 July and a reconnaissance aircraft transiting from the Black Sea to overfly Lithuania, Latvia, and Estonia on 10 July. A Vot Tak investigation separately describes a Telegram-based Russian sabotage recruitment network inside Lithuania.

If the Leningrad cluster is borne out, it would extend Ukrainian deep-strike reach against Baltic-facing Russian logistics nodes. The ISR reposturing and sabotage-network reporting, though unverified, align with a flank increasingly treated as an active intelligence and hybrid environment.

• Watch for second-source corroboration of damage at Ust-Luga, Vysotsk, or Luzhsky Polygon; commercial satellite or shipping-data confirmation would upgrade the Leningrad cluster.
• Watch Estonian official channels for any statement clarifying the 8 July GDELT "fighting" signal; continued silence would indicate a data artefact.
• Watch for sustained NATO ISR presence over the Baltics or additional flights near Kaliningrad, which would indicate a durable posture shift rather than a single sortie.
• Watch Lithuanian counter-intelligence disclosures on the alleged Telegram sabotage recruitment network.

All six reported events across Israel, Gaza, and the Golan periphery in this 24-hour window are single-sourced and unverified. Signal is dominated by GDELT-flagged "fighting" tags in Israel's Northern District and a reported drone strike on a northern Gaza hospital — none independently corroborated.

No 7-day baseline exists for comparison, so every cluster registers as a new signal rather than a delta. Three of six unconfirmed events cluster in the Northern District (two in Al-Ubeidiya, one in Maalot), all derived from GDELT CAMEO code 19 tone/mention counts rather than named field reporting. A reported Israeli drone strike on a hospital in northern Gaza and generic fighting near coordinates 31.5N/34.75E in the Gaza Strip remain single-sourced. Separately, a reported Israeli ground incursion into the southern Quneitra countryside describes a house and fodder-warehouse search with no kinetic engagement or casualties — the only event in the set with tactical specificity, though still uncorroborated.

The Northern District clustering, if substantiated, would represent activity inside Israel's pre-1967 territory rather than the Lebanese or Syrian frontier, which would be operationally significant — but the underlying reporting is GDELT tone-based and should not yet be treated as confirmed kinetic activity. The Quneitra incursion account, if verified, points to continued Israeli ground activity inside Syrian territory absent engagement. The northern Gaza hospital strike claim, if corroborated, would add to the pattern of medical-facility incidents in the strip.

Watch for second-source confirmation of the Al-Ubeidiya and Maalot fighting reports; independent imagery or IDF/local-authority statements would indicate whether these are genuine incidents or GDELT tagging artifacts. Watch for hospital-identification and casualty figures out of northern Gaza. Watch Syrian sources for corroboration of the southern Quneitra search; repeat incursions would indicate a sustained pattern rather than an isolated sweep.

Reporting for the 24-hour window is thin and entirely single-sourced: two unconfirmed incidents in Sagaing and Kayin State suggest continued kinetic activity outside the Northern Shan baseline, but neither can be independently verified.

Both reported incidents fall in areas without a 7-day baseline of activity in this dataset. In Sagaing Region, a single-sourced report describes artillery fired from military-controlled areas striking two villages and wounding five civilians. In Kayin State, resistance-aligned sources claim dozens of regime troops were killed during human-wave assaults on Min Let Pan, with accompanying reporting that Thailand has reinforced its adjacent frontier. Northern Shan State, the only area with a prior baseline (0.1 events/day), generated no events in the period. All items are unconfirmed and single-sourced; casualty figures from the Kayin claim originate with one side of the engagement.

If corroborated, the Sagaing shelling would be consistent with the pattern of indirect fire against non-combatant settlements in the region, while the Min Let Pan claim — combined with the reported Thai frontier reinforcement — would point to a border-adjacent engagement significant enough to prompt a third-state response. Absent second-source confirmation, both remain indicative rather than evidentiary, and the quiet in Northern Shan is notable only against a very low baseline.

Watch for independent confirmation of the Sagaing village strikes, particularly imagery or medical-facility reporting on the five wounded; corroboration would establish a verified indirect-fire incident. Watch for regime or neutral reporting on Min Let Pan casualty counts — convergence with resistance figures would strengthen the claim, while silence would leave it single-sourced. Watch Thai official statements or troop movement reporting along the Kayin frontier; confirmed reinforcement would indicate the engagement is assessed as cross-border relevant. Renewed activity in Northern Shan would signal a return to baseline tempo.

Two partially corroborated explosion events in Homs and Idlib within a 10-hour window, both preceded by reported aircraft activity, mark a departure from a near-dormant 7-day baseline in both governorates.

Homs and Idlib each registered one strike-associated incident against a 7-day baseline of roughly 0.1 events/day per governorate. Near al-Sukhna (Homs), an explosion inside a cave at Jabal al-Dahak followed reported intensive aircraft activity in local airspace; the actor and cause are unidentified. Near Kafrayya and al-Foua (Idlib), explosions were heard alongside reported International Coalition overflights, with no target or casualty detail. Both are two-source PARTIAL confidence; neither is independently verified. Damascus and Rif Dimashq recorded no events in-period.

The Jabal al-Dahak cave location is consistent with the type of subterranean infrastructure previously associated with ISR-cued strikes in the Homs badia, though attribution here remains open. The Kafrayya/al-Foua signature — audible detonations paired with reported coalition aircraft — points to possible external air activity in northwest Syria on the same night as the Homs incident. Two geographically separated, aviation-linked events in a single reporting window is a meaningful deviation from the baseline, but the absence of confirmed actor, target, or battle damage limits what can be inferred about intent or campaign framing.

Watch for follow-on reporting from al-Sukhna that identifies the cave's occupants or recovers ordnance signatures; confirmation would clarify whether Jabal al-Dahak represents a counter-ISIS or counter-militia strike. Watch for imagery or claims tied to the Kafrayya/al-Foua detonations; corroboration of coalition involvement would indicate a shift in western coalition tasking into Idlib. Watch Homs badia airspace reporting for repeat overflights, which would indicate a sustained ISR-strike cycle rather than an isolated event.

Two single-sourced, unconfirmed violence signals in La Guaira (Vargas) during 5–9 July are the only events on record for the period; there is no verified activity to assess and no baseline for comparison.

Against an empty 7-day baseline, two unconfirmed CLASH signals surfaced in La Guaira, Vargas: an assault-coded signal on 5 July derived from a GDELT tone-negative cluster (three mentions), and a fighting report on 9 July. Both are single-sourced and unverified, with no reporting on actors, weapons, or casualties. No corroborating events elsewhere in the country appear in the input set.

Vargas hosts Venezuela's principal maritime gateway and the Maiquetía international air hub adjacent to Caracas, so any confirmed kinetic activity there would carry disproportionate weight. However, with both signals unconfirmed and lacking actor attribution, the current record does not support conclusions about escalation, criminal-versus-state dynamics, or spillover from Caracas. The operative fact for this period is the absence of verified reporting, not the presence of conflict.

• Watch for second-source corroboration of the 5 July assault and 9 July fighting reports in La Guaira; independent confirmation would reclassify the Vargas cluster from noise to a genuine local incident.
• Watch for actor identification (state security, colectivos, criminal groups) in any follow-on reporting; attribution would indicate whether the signals reflect policing action, factional violence, or something else.
• Watch for any reporting from Caracas or port/airport facilities in Vargas; geographic spread would indicate the La Guaira signals are part of a broader pattern rather than isolated GDELT artifacts.

A verified Israeli drone strike on Kamal Adwan Hospital in Beit Lahiya wounded hospital staff, marking a single but significant incident in North Gaza against a low baseline of activity.

North Gaza recorded one verified strike in the reporting period, against a 7-day baseline of 0.1 events/day — a roughly ninefold spike, though from a small base. The incident at Kamal Adwan Hospital in Beit Lahiya involved a drone munition impacting hospital premises and wounding medical workers, according to the Palestinian Health Ministry. No corroborated activity was reported this period in Gaza City, Khan Younis, the Southern District, Jerusalem District, or the West Bank governorates of Ramallah and Hebron, all of which had shown low but non-zero baseline activity.

Kamal Adwan is one of the few partially functional hospitals remaining in North Gaza, and strikes affecting its staff degrade trauma capacity in an area with limited medical redundancy. The Health Ministry's framing of the strike as part of a pattern of targeting health infrastructure — while a claim by a party to the conflict — will shape humanitarian and diplomatic messaging in coming days. The concentration of the period's only verified kinetic event on a hospital, rather than dispersed military targets, is the notable operational signal.

• Watch for follow-on strikes in the Beit Lahiya–Jabalia corridor; repeat incidents near Kamal Adwan would indicate a sustained operational focus on North Gaza rather than an isolated event.
• Monitor statements from WHO, ICRC, and hospital administration for casualty updates and any evacuation orders; announced withdrawal of staff would indicate functional loss of the facility.
• Track whether West Bank governorates (Ramallah, Hebron) and Jerusalem District return to baseline activity or remain quiet, which would suggest displacement of attention toward Gaza operations.

RSF drone activity against El Obeid, North Kordofan is reported to be intensifying, marking the sole reported incident this period and a notable uptick against a thin 7-day baseline. The report is partially corroborated (two sources) with no confirmed damage or casualty detail.

North Kordofan recorded one strike event against the 7-day average of 0.3 events/day, a roughly 233% shift concentrated on El Obeid, where RSF-attributed drone attacks are described as intensifying. Blue Nile, the other tracked oblast in the baseline, produced no reported activity in this window. Targets, munitions, and effects at El Obeid remain unspecified in available reporting, and no casualty figures are corroborated.

El Obeid is the principal SAF-held node linking Khartoum to Kordofan and Darfur, and sustained RSF drone pressure there would extend a pattern of standoff strikes against rear-area garrison towns rather than frontline positions. Even absent confirmed impact data, a second corroborating source elevates this above single-sourced noise and suggests RSF is willing to expend drone stocks on interdicting a logistics hub well behind the immediate contact line.

• Watch El Obeid for follow-on strike reporting with geolocated imagery; recurrence within 72 hours would indicate a deliberate campaign rather than an isolated salvo.
• Watch for identification of targeted infrastructure — airfield, fuel, or command nodes — which would clarify RSF intent against the North Kordofan logistics chain.
• Watch Blue Nile for any resumption of activity; continued silence would suggest the current tempo remains Kordofan-weighted.
• Watch for SAF air-defense or counter-UAS claims around El Obeid, which would indicate the strike volume is straining local defenses.

The 24-hour window produced no verified kinetic activity in Yemen. A single unconfirmed assault report from Jawf area of Abyan governorate is the only item of note and remains uncorroborated.

Reporting volume sits at or below the 7-day baseline of 0.1 events/day for Al Hudaydah, with no activity logged there in the period. The only shift is a single-sourced, unverified report of an assault in Jawf, Abyan — a governorate with no prior baseline activity in the trailing week. Actors, casualties, and weapons are not described in the underlying post, and no corroborating open-source reporting has surfaced within the window.

Absent verification, the Abyan report cannot be treated as a genuine expansion of the conflict geography. However, Abyan sits outside the Houthi–coalition frontline pattern and inside the Southern Transitional Council's area of influence, so any confirmed clash there would carry different implications than Red Sea coast or northern-front activity. Until a second source emerges, the operating assumption should be a quiet reporting cycle rather than a southward shift in tempo.

• Watch for second-source corroboration of the Jawf, Abyan assault report; independent confirmation from local stringers or security-service statements would indicate an actual incident rather than a reporting artifact.
• Watch Al Hudaydah reporting channels for any return to or above the 0.1 events/day baseline; a sustained zero would suggest a genuine lull rather than collection gaps.
• Monitor whether additional Abyan-area reporting appears; a cluster in the south would indicate STC-area internal security friction worth tracking separately from the northern front.

No significant activity in the last 6 hours: Iran.