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

The 24-hour period produced zero verified or partial-confidence events; all seven recorded events are single-sourced and unconfirmed, preventing substantive assessment of ground conditions across the Palestinian theater.

Activity volume in the period is consistent with the 7-day baseline across all sub-areas (Gaza Strip, West Bank). No notable shifts were recorded. All reported activity is unconfirmed and should be treated as provisional pending corroboration.

Unconfirmed reports describe Israeli military operations across multiple West Bank districts — including raids, detentions, and house occupations repurposed as military barracks in the Nablus area (Tal town and Jaloud village) — as well as a reported strike east of Deir al-Balah in central Gaza. A separate unconfirmed report cites a U.S. military reduction of refueling aircraft at Ben Gurion Airport toward ceasefire-period levels. None of these reports are corroborated across independent sources.

The complete absence of verified or partial-confidence events means no operationally reliable picture of the theater can be drawn for this period. The cluster of unconfirmed West Bank reports, if corroborated, would indicate a sustained multi-district arrest and property-seizure tempo. The unconfirmed U.S. aircraft drawdown report, if verified, would carry significance for regional force posture assessment.

Watch for independent corroboration of the reported West Bank raids across Nablus, Jenin, Qalqilya, Bethlehem, Ramallah, and Hebron — confirmation would indicate an elevated operational tempo above baseline. Monitor for casualty or damage reporting from east Deir al-Balah that would substantiate the unconfirmed Gaza strike. Track U.S. military asset levels at Ben Gurion Airport; any verified reduction would indicate a meaningful shift in American force presence supporting regional operations.

Lithuanian authorities issued repeated warnings this period about a potential Russian false-flag drone operation against NATO's eastern flank; all six events in the period are unconfirmed and single-sourced, limiting analytical weight.

No verified or partial-confidence events were recorded for the NATO eastern flank this period, and no 7-day baseline exists for comparison. The six unconfirmed events cluster around three themes in Lithuania:

False-flag drone warnings: Three single-sourced, unconfirmed reports — including a named statement attributed to Lithuanian Defense Minister Robertas Kaunas on 6 August — describe Lithuanian officials warning that Russia may employ seized Ukrainian-manufactured drones to stage a provocation against NATO's eastern flank. The repetition across separate reports over 6–7 August suggests a sustained official messaging effort, though the underlying threat assessment remains unverified.

NATO air-intercept tempo: A single-sourced, unconfirmed report states NATO disclosed a 250% year-on-year increase in fighter scrambles along its eastern border in July 2026, attributed to Russian aircraft operating near Alliance airspace without flight plans. No corroborating NATO press release is cited.

Border incidents: Two low-level incidents were reported — a Lithuanian national briefly crossing the Russian border after breaching a checkpoint (timing uncertain per the source), and a migrant group reportedly assaulting Lithuanian border guards after entering via a tunnel from Belarus near the Vilnius/Alytus region. Both are single-sourced and unverified.

If the false-flag drone warning reflects genuine intelligence, it would represent a deliberate escalation mechanism designed to trigger an Article 5 ambiguity scenario. The reported surge in NATO scramble activity, if accurate, indicates a sustained pattern of Russian airspace pressure rather than isolated incidents.

Watch for corroborating official statements or NATO communiqués on the drone false-flag warning — independent verification would substantially elevate the threat assessment. Monitor Lithuanian, Latvian, and Estonian defense ministry channels for coordinated messaging, which would indicate the warning has alliance-wide backing. Watch for any reported drone incidents near NATO territory that lack clear attribution. Track Baltic border crossing incidents for pattern changes that would indicate coordinated hybrid pressure. Any NATO press release confirming the scramble-rate figure should be treated as a baseline shift indicator.

All six Sudan events in the period are single-source and unconfirmed; no verified or partially corroborated reporting is available, but the pattern — mass-grave discoveries, drone strikes, and large-scale displacement across Darfur, Kordofan, and Blue Nile — warrants close monitoring.

No verified or partial-confidence events were recorded for the 24-hour window, and no 7-day baseline is available for comparison. All reporting is provisional and single-sourced.

Six unconfirmed events span four states. In West Darfur, clashes between RSF and joint forces north of al-Junayna near the Chad border have reportedly displaced thousands, with relief aid described as halted; separately, approximately 5,975 individuals are reported displaced from Sirba to internal camps, cause unspecified. In North Darfur, SAF drones are reported to have struck positions in al-Fasher and Kabkabiya, drawing de-escalation calls from civil society. In South Kordofan, humanitarian aid warehouses near Kauda airport were reportedly looted, while a local organization distributed supplies to 900 women at a separate shelter site. In Blue Nile, a mass grave of 25 bodies — including women and children — was reported in Kurmuk following an SAF retaking of the town, with officials attributing the killings to RSF. A second report of 25 civilian bodies in mass graves in al-Karnak, Khartoum State, provides no attribution or further detail.

If corroborated, the Kurmuk and al-Karnak mass-grave reports would constitute significant atrocity documentation. Simultaneous unconfirmed strikes in North Darfur and displacement pressure near the Chad border suggest potential multi-front stress on an already constrained humanitarian corridor.

Watch for independent corroboration of the Kurmuk and al-Karnak mass-grave reports, which would indicate atrocity accountability obligations. Monitor humanitarian access routes north of al-Junayna and around Sirba; any further aid suspension would indicate deepening civilian harm. SAF drone activity near al-Fasher warrants tracking — additional strikes would indicate an escalating air campaign in a UN-designated protection zone. Looting at Kauda airport should be watched for pattern recurrence, which would indicate systematic targeting of aid infrastructure.

Ukraine struck three Russian energy and petrochemical facilities across Orenburg, Tyumen, and Khabarovsk in a single 24-hour period, while Moscow's air defenses intercepted a 19-drone overnight salvo — marking a significant geographic spread of deep-strike activity.

All five events are provisional (partial confidence, no verified items). Activity spiked sharply above baseline in four oblasts.

Orenburg saw two correlated reports of a drone strike on the Orsk Refinery (Orsknafte-orgsintez), one of the region's largest — 600% above its 7-day baseline. One report attributes the strike to Ukrainian attack drones that traversed approximately 1,000 miles of Russian airspace; a second OSINT-sourced assessment indicates probable damage to an ELOU-AVT distillation unit. Both are provisional.

Tyumen recorded a confirmed-by-governor strike on the ZapSibNeftekhim petrochemical complex in Tobolsk — Russia's largest petrochemical facility, part of the SIBUR holding — where drones ignited a fire at the Central Gas Fractionation Unit. No casualties were reported. This is 600% above baseline.

Khabarovsk logged a reported fire at a refinery in Komsomolsk-on-Amur, single-sourced and provisional. No explicit attack claim is made; sabotage is implied but unconfirmed. Also 600% above baseline.

Moscow saw 19 drones intercepted overnight per a mayoral statement, with emergency services responding to debris-fall sites — 133% above baseline.

Simultaneous targeting of refining and petrochemical infrastructure across three geographically dispersed regions — Orenburg (~1,800 km from Ukraine), Tyumen (~2,100 km), and Khabarovsk (~6,400 km) — suggests a deliberate campaign to stress Russian air defenses across depth and attack high-value energy nodes outside previously struck corridors. ZapSibNeftekhim's scale makes the Tobolsk strike particularly significant for downstream chemical supply.

Watch for official Russian damage assessments or production disruption reports from Orsk and Tobolsk, which would indicate operational impact on refining capacity. Monitor Khabarovsk for additional sourcing that would clarify whether the Komsomolsk-on-Amur fire was strike-related. Any follow-on drone activity in Tyumen or Orenburg would indicate persistent targeting of Ural-region energy infrastructure. Debris-fall injury or damage reports from Moscow overnight sites would indicate intercept efficacy limits.

ATESH partisans conducted a verified sabotage of Russian military rail logistics near Voronezh, while near-simultaneous strikes hit Kyiv and Zaporizhzhia city, marking a compressed multi-axis activity window in the 24-hour period.

Voronezh saw a sharp spike — 2 events against a 7-day baseline of 0.3/day (up ~600%). The first, verified and corroborated across four sources, was a sabotage operation by ATESH partisan agents near Voronezh city: they destroyed the cab of an electric locomotive supporting Russian military supply runs toward the Kupiansk direction, disrupting rail operations. The second Voronezh event — partial, two sources — was a strike on a Wildberries logistics warehouse in Aleksandrovka, Novousmansky District, wounding at least two people; local authorities had not confirmed the cause at time of reporting.

In Zaporizhzhia, a Russian combined strike on the city wounded two people, damaged residential and non-residential structures, caused fires, and triggered power outages, per the Oblast Military Administration. This event is partial, corroborated across six sources. Zaporizhzhia recorded a modest 40% uptick over its 7-day baseline.

In Kyiv, a verified, three-source report confirmed Russian ballistic missiles struck the city, wounding one person, per the city military administration. Activity in Kyiv remained within baseline norms.

The ATESH rail sabotage near Voronezh is operationally significant: the Kupiansk direction has been an active front, and disruption to logistics rail in Voronezh Oblast — deep within Russian-controlled territory — indicates partisan reach into rear-area supply infrastructure. The clustering of strikes on Kyiv and Zaporizhzhia within minutes of each other on the night of August 10–11 is consistent with coordinated multi-axis strike packages intended to strain air defense coverage.

Watch for Russian official acknowledgment or denial of the Voronezh locomotive sabotage, which would indicate intelligence value assessment. Monitor Kupiansk axis reporting for any logistics delays that could correlate with the rail disruption. Track Zaporizhzhia OVA updates for casualty revisions and infrastructure damage assessments following the combined strike. Watch for further nocturnal strike activity on Kyiv, which would indicate sustained pressure on capital air defenses.

Israeli forces conducted two drone/airstrike actions in southern Lebanon and advanced into the Quneitra southern countryside within a 24-hour window, marking elevated tempo across both the Lebanese and Syrian fronts.

South Lebanon activity ran at approximately 2.0 events/day, up roughly 75% against the 7-day baseline of 1.1/day. Two partial-confidence strikes were recorded: Israeli airstrikes hit the town of al-Mansoori in the evening, with no casualty figures reported, and a separate Israeli drone struck a vehicle near Nabatieh the following morning — both sourced from regional outlets and rated provisional at two sources each. Separately, Israeli forces moved into the southern countryside of Quneitra in southern Syria, with drones simultaneously observed over Quneitra and Daraa; this movement report is also partial-confidence, corroborated across two sources. No verified events were recorded in the period.

The concurrent pressure on South Lebanon and Quneitra suggests coordinated or at minimum parallel Israeli operations on two geographically linked fronts within a single operational day. The vehicle strike near Nabatieh is consistent with targeted interdiction activity; the Quneitra ground advance, if sustained, would represent a shift from the area's baseline of low-intensity observation activity. All three events remain provisional — no independent corroboration elevates them to verified status.

Watch for casualty or damage assessments emerging from al-Mansoori and Nabatieh that would indicate strike scale and targeting intent. Monitor Quneitra and Daraa for additional movement reports or drone activity that would indicate whether the southern Syria advance is an isolated probe or a sustained repositioning. Any activity in Bushehr Province or the Red Sea corridor should be tracked against their low baselines, as a single event would represent a notable deviation.

Activity in the Israel theater during this 24-hour period is minimal, with a single unconfirmed report of Israeli ground movement in the Quneitra countryside warranting continued monitoring.

No verified or partial-confidence events were recorded in the period. The sole entry — a movement report placing Israeli tanks and soldiers at Tal Abu Qubais in the Quneitra countryside — is single-sourced, drawn from Syrian state media, and remains unconfirmed. No casualties or clashes were reported. Against a 7-day baseline of 0.1 events per day in Quneitra, this period shows no statistically notable departure.

Because the Tal Abu Qubais report is unconfirmed and single-sourced, it carries no verified operational weight for this period. Quneitra's baseline activity is already very low, and the absence of corroborating sources means no confirmed change in Israeli ground posture can be assessed. The report's origin in Syrian state media adds an additional layer of uncertainty regarding impartiality and accuracy.

Watch for independent corroboration of the Tal Abu Qubais movement report from non-state or satellite sources; confirmation would indicate a ground presence beyond established Israeli activity patterns in the Quneitra area. Monitor Syrian and Israeli military channels for any follow-on reporting of clashes, casualties, or additional movement. Absence of corroboration within 48 hours would support treating the report as unsubstantiated.

A provisional report of a Tatmadaw airstrike on Kyaukkyi Village in Thandwe Township, Rakhine State represents a significant civilian casualty event and a sharp spike above the 7-day baseline for the area.

Rakhine State recorded one event in the 24-hour period — a 600% increase over its 7-day average of 0.1 events/day. The sole event, rated partial confidence, describes a Tatmadaw fixed-wing strike on Kyaukkyi Village, Thandwe Township, at approximately 04:22 UTC on 11 August 2026. The report, sourced from the Arakan Army's Information Desk and corroborated by a second source, states 14 civilians killed — including children and elderly — and 11 injured. Photographic material was released by the AA. Because the reporting originates primarily from a party to the conflict and has not been independently verified, the casualty figures are provisional.

Thandwe Township sits in southern Rakhine State, an area where the Arakan Army has consolidated significant territorial presence. A confirmed strike on a civilian settlement — if corroborated — would represent one of the higher single-incident civilian death tolls reported in the theater recently. The AA's rapid public information release, including photographs, signals an intent to generate international visibility around the incident. Tatmadaw air operations against populated areas in AA-controlled zones have previously drawn humanitarian and diplomatic attention.

Watch for independent corroboration of the Kyaukkyi Village casualty figures from humanitarian monitors, local media, or third-party journalists — confirmation would indicate a mass-casualty strike on civilians. Monitor Tatmadaw official channels for any response or counter-narrative. Any follow-on strikes in Thandwe Township would indicate an escalating air campaign in southern Rakhine State.

A provisional report of 19 HTS-linked government forces wounded near Ain al-Arab (Kobani) in Aleppo marks a notable spike in activity in a governorate that has averaged just 0.1 events per day over the past week.

Activity in Aleppo jumped to 1.0 events in the 24-hour period — a 600% increase against the 7-day baseline of 0.1 events/day. The sole event driving this shift is a partial-confidence report from Ain al-Arab (Kobani): the HTS-led transitional government ("Jolani government") disclosed that 19 of its personnel were wounded in the area. The announcement is sourced across three outlets but carries no corroboration on the nature of the engagement, the opposing actor, or the precise location of contact. All other tracked governorates — Rif Dimashq, Daraa, and Deir ez-Zor — remained within their established baseline ranges.

Ain al-Arab (Kobani) sits in a historically contested corridor along the Syrian-Turkish border with a significant Kurdish population and longstanding SDF presence. Casualties among HTS-affiliated forces in this zone, if confirmed, would suggest renewed friction between the transitional government and armed actors in the northeast — a dynamic with potential escalation pathways involving Turkish-backed factions and Kurdish self-administration forces. The absence of any identified opposing actor is a meaningful intelligence gap at this stage.

Watch for follow-on HTS statements that name an opposing actor or describe the engagement type, which would indicate whether this is an isolated incident or an opening of a broader confrontation. Monitor SDF and Turkish-backed faction channels in the Kobani corridor for any claims of contact. A second incident in Aleppo within 72 hours would indicate a sustained shift rather than a single outlier event.

Houthi forces conducted a provisional-confidence missile strike on Al-Mokha port in Taiz Governorate on 10 August, marking a spike above the 7-day baseline for that area.

Taiz registered one event in the 24-hour period — a 250% increase over the 7-day average of 0.3 events/day. At approximately 01:25 local time on 11 August (22:25 UTC, 10 August), three missiles were reported launched from Ibb Governorate toward Al-Mokha city; one reportedly struck the port facility. This is the sole event in the period and is rated partial — corroborated across three sources but not fully verified. No damage assessments or casualty figures are available. Marib and the Gulf of Aden recorded no events, both below their respective baselines.

Al-Mokha port is a strategically significant Red Sea coastal node with historical relevance to fuel and humanitarian commodity flows into western Yemen. Resumed missile targeting of the port — if confirmed — would represent a deliberate effort to constrain logistics throughput at a non-Houthi-controlled entry point. The launch origin reported as Ibb Governorate is notable: Ibb sits well inland and its use as a firing position, if substantiated, would indicate operational reach into central Yemen for coastal interdiction missions.

Watch for independent damage assessments of Al-Mokha port infrastructure, which would indicate the operational impact on cargo handling capacity. Monitor for follow-on strikes along the Red Sea coast or additional launches attributed to Ibb Governorate, which would indicate a sustained interdiction posture rather than an isolated incident. Any Houthi official statement claiming the strike would elevate confidence on the sourcing.