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

Russian strikes across Ukraine produced mass civilian casualties in Sumy and Kyiv while Ukrainian operations pressured Russian logistics in the Sea of Azov and occupied Energodar. All 12 events are partially corroborated; none are single-sourced unverified.

Sumy saw a sharp escalation to two strikes versus a 0.4/day baseline: three guided aerial bombs on the Zarechny district killed four (including a child) and injured seven, and a further airstrike hit a busy street in Sumy city. Zaporizhzhia oblast recorded three events, above its 2.3/day baseline: guided aerial bombs injured two in Zaporizhzhia city, a Ukrainian drone strike on a bus stop in occupied Energodar killed a woman and wounded four, and Ukrainian strikes on Russian gasoline tankers in the Sea of Azov reportedly forced closure of some maritime routes. Crimea registered a rare event with a reported strike near Kerch. Kyiv saw a single overnight strike damaging residences, offices, and a seminary with 11 injured — below its 1.4/day baseline but high-severity. Additional partial-confidence strikes were reported in Kharkiv's Shevchenko district (3 injured), Kherson's Korabel microdistrict (1 killed), Odesa, Kramatorsk (gas distribution station), and Slavyansk (1 killed, extensive residential damage).

The Sumy and Kyiv strikes indicate continued Russian targeting of civilian-dense areas with guided munitions and ballistic missiles penetrating air defenses. The Sea of Azov tanker strikes and the Kerch-area report suggest Ukrainian deep-strike focus on Russian fuel logistics and Crimean rear areas, corroborated across multiple sources for Azov but single-sourced for Kerch.

Watch Sumy for whether the two-event day becomes a sustained pattern, which would indicate a shift in Russian aerial bombing geography. Watch Sea of Azov and Kerch reporting for follow-on strikes or Russian route closures, which would indicate a maturing Ukrainian interdiction campaign. Watch Kramatorsk gas infrastructure status for cascading effects on frontline support.

Iran declared the Strait of Hormuz closed and struck a transiting vessel while US strikes hit Bandar-e-Jask and Bushehr Province; IRGC-claimed missile fire reached Jordan and Kuwait, marking a sharp regional escalation over the 24-hour window. All reporting is partial-confidence.

Hormozgan Province saw five events, more than double its 7-day baseline. The IRGC Navy announced closure of the Strait of Hormuz to all traffic pending cessation of US "interference," and Fars reported an IRGC cruise missile struck a ship that allegedly deviated from designated routes with transponder off; a warning shot was also reported. In parallel, over 10 explosions were reported in Bandar-e-Jask following a US-announced strike wave, with further attacks reported on Bushehr, Kangan, Deir, and Asaluyeh in Bushehr Province. Geographic spillover expanded sharply: the IRGC aerospace force claimed missile strikes on Prince Hassan Air Base (H5) in Mafraq, Jordan, targeting US facilities and MQ-9 infrastructure, while Qatar reported intercepting a missile and an explosion was reported in Kuwait attributed by some outlets to strikes on US interests. Israeli airstrikes continued on al-Mansoori in southern Lebanon, described as a third bombardment in an ongoing series.

The Hormuz closure declaration paired with a kinetic attack on shipping moves Iran from rhetorical to enforced interdiction of the world's principal oil chokepoint. Simultaneous IRGC-claimed strikes on US basing in Jordan and reported impacts in Kuwait, alongside the Qatar intercept, indicate a widened targeting set beyond Iranian territory. Continued Israeli strikes in southern Lebanon persist as a parallel front.

Watch commercial AIS traffic and tanker diversions in the Strait of Hormuz; sustained absence would corroborate enforcement of the closure. Watch for further US strike waves following Bandar-e-Jask and Bushehr Province activity, and for additional IRGC claims against bases in Jordan, Kuwait, Qatar, or Bahrain — expansion would indicate a deliberate regional targeting campaign. Watch southern Lebanon tempo for coupling with the Gulf axis.

All nine events in the period are single-sourced and unconfirmed. The most operationally significant signal is a reported large-scale Ukrainian UAV strike on Leningrad Oblast port and range infrastructure (Ust-Luga, Vysotsk, Luzhsky Polygon), alongside heightened NATO ISR activity along the Baltic flank.

With no prior baseline, every cluster represents a new signal rather than a delta. Two Leningrad reports describe an attack on the Port of Ust-Luga and the Luzhsky range on 6 July, with the oblast governor citing 56 downed UAVs, infrastructure damage at Ust-Luga, Vysotsk, and Luzhsky Polygon, and internet outages in Saint Petersburg. A separate 7 July report of a drone strike on a port oil terminal is geolocated to Pskov but textually references a Leningrad-region terminal, suggesting a possible geocoding artefact of the same event set. NATO ISR posture shifted westward: a reconnaissance aircraft previously over the Black Sea was tracked over Lithuania, Latvia, and Estonia, and an RAF RC-135W was observed near Kaliningrad. Three GDELT-derived "fighting" flags in Estonia (59°N, 26°E) on 8 July share coordinates and low mention counts, indicating probable duplicate ingestion rather than three discrete incidents. An investigative report alleges a Russian sabotage recruitment network in Lithuania using mass Telegram posts.

If corroborated, the Leningrad strikes would mark a sustained Ukrainian deep-strike reach against Baltic-facing Russian port and training infrastructure. The concurrent NATO ISR reposturing and the Lithuania sabotage reporting frame a wider hybrid contest along the flank, though none of it is verified.

Watch for second-source confirmation of damage at Ust-Luga and Vysotsk; imagery or shipping data would indicate scale. Monitor whether the three Estonia "fighting" flags resolve into a single identifiable incident or fade as duplicates. Continued RC-135W and multi-country ISR tracks would indicate sustained alliance tasking rather than a one-off sortie. Additional reporting on the alleged Lithuania recruitment network would indicate whether prosecutions or disruptions follow.

All eight events in the 24-hour window are single-sourced and unverified, but the geographic spread — from Quneitra to Gaza and across four Israeli districts — warrants monitoring rather than dismissal. No verified activity is on record for this period.

There is no 7-day baseline against which to measure deltas; every district appears as a new signal. Unverified GDELT-derived "fighting" tags cluster in Tel Aviv, Ashdod (Southern District), Zarit on the northern border, Kiryat Motzkin near Haifa, and coordinates 31.5/34.75 straddling the southern Israel–Gaza boundary, reported twice. Two items carry more specific sourcing: a shooting on Al Quds Street in Tel Aviv reported to have seriously injured one person, with Israeli security forces on alert; and a Middle East Monitor report of an Israeli army incursion into southwest Syria with a checkpoint established in Quneitra. None of the eight items are corroborated by a second source.

The Zarit and Quneitra signals, if borne out, would together suggest simultaneous friction on the Lebanese and Syrian frontiers. The paired Gaza-border coordinates hint at continued kinetic activity along the southern envelope. The Tel Aviv shooting, treated by Israeli responders as a security incident rather than criminal-only, is the most concretely reported item and the one most likely to shape near-term domestic posture. Absent corroboration, none of these should be treated as confirmed engagements.

Watch for Israeli military or police statements on the Al Quds Street shooting; an attribution to a designated actor would elevate it beyond a criminal incident. Watch for second-source confirmation of the reported Quneitra incursion and checkpoint, which would indicate a sustained ground presence in southwest Syria. Monitor Zarit and the Gaza-boundary coordinates for repeat reporting that would distinguish signal from GDELT noise.

Damascus saw a sharp concentration of explosive incidents during a high-profile French presidential visit, with one verified blast near the Four Seasons Hotel and partial reporting of related bombings and an arrest. Parallel unexplained explosions in Homs and Idlib coincided with reported coalition and unspecified aircraft activity.

Damascus governorate recorded three incidents against a baseline of 0.4/day: a verified explosion near the Four Seasons Hotel on 7 July with at least one vehicle burning, a fatal hand grenade incident the same evening, and the announced arrest of a cell tied to "terrorist bombings" during President Macron's visit on 9 July (both partial). In Homs, a partially reported explosion inside a cave at Jabal al-Dahak near al-Sukhna on 11 July followed intensive aircraft activity, with actor unidentified. In Idlib, explosions near Kafrayya and al-Foua on 10 July were accompanied by reported International Coalition overflights. In Rif Dimashq, General Security forces are partially reported to be withdrawing gradually from Esh Al-Wuroud amid unspecified accusations, with no kinetic activity described.

The Damascus cluster, anchored by the verified Four Seasons incident, indicates an urban attack pattern timed to a foreign head-of-state visit — a diplomatic-security exposure the arrests announcement seeks to close. The Homs cave explosion and Idlib overflight-linked blasts, though only partially sourced, suggest renewed external air activity against fixed targets in desert and northwest terrain. The Esh Al-Wuroud withdrawal points to internal friction inside government security posture near the capital.

Watch Damascus for follow-on arrests or claims of responsibility tied to the Four Seasons blast; attribution would clarify whether the cluster is a single campaign. In Homs and Idlib, further overflight reporting or secondary explosions would indicate a sustained air interdiction pattern. In Esh Al-Wuroud, any replacement force or renewed deployment would indicate the withdrawal's political character.

All three events in the period are single-sourced and unconfirmed, but they cluster around two active fronts: North Kordofan (El Obeid and wider Kordofan) and North Darfur (Bir Suleiba/Abu Qamra/Kalbs). No verified activity is available for this window.

North Kordofan activity rose sharply against the 7-day baseline of 0.3 events/day, with two unconfirmed clash reports — one in El Obeid, accompanied by a UNICEF warning that roughly half a million civilians are at risk, and a second broader Kordofan-region fighting report. North Darfur registers a new unconfirmed cluster with no prior baseline: RSF claims of recovering Bir Suleiba, Abu Qamra, and Kalbs, alongside reported SAF–RSF fire exchanges near ceasefire monitoring positions and permanent force locations. Blue Nile shows no reported activity this period despite its baseline presence. All reporting is single-sourced and should be treated as provisional.

If corroborated, the El Obeid reporting would mark renewed pressure on a major Kordofan urban center with a large at-risk civilian population, consistent with UNICEF's flagged concern. The North Darfur reports, if accurate, would combine RSF territorial claims with fire near ceasefire-monitoring infrastructure — a category of incident that historically complicates de-escalation mechanisms. The absence of verified sourcing limits confidence in either read.

Watch for second-source corroboration of fighting in and around El Obeid; independent confirmation would indicate a genuine escalation rather than a reporting artifact. Watch for SAF or third-party statements on the Bir Suleiba/Abu Qamra/Kalbs claims; any confirmation of fire at ceasefire monitoring positions would indicate stress on existing de-escalation arrangements. Watch for humanitarian access signaling from UNICEF or OCHA on Kordofan, which would indicate whether civilian-risk assessments are firming up.

Two single-sourced, unverified incidents dominate the 24-hour window: alleged Myanmar airstrike munitions crossing into Thailand from Kayin State, and the reported arrest and killing of roughly 20 young defense force members in Chauk, Magway Region. Neither is corroborated, and both fall outside the Northern Shan baseline that defined the prior week.

Activity shifted away from the Northern Shan baseline (0.1 events/day) toward two regions with no prior baseline in the period. Democratic Voice of Burma reported that Myanmar airstrikes sent munitions across the border into Thailand from Kayin State, coinciding with a July 11 bilateral foreign ministers' meeting on border security — single-sourced and unverified. Separately, roughly 20 defense force members, described as aged 18–25, were reportedly arrested and killed in Chauk, Magway Region — also single-sourced and unverified. No verified or partially corroborated events were logged.

If confirmed, the Kayin cross-border munitions impact would inject a kinetic incident directly into an active Thai-Myanmar diplomatic track on border security, raising the diplomatic cost of continued air operations near the frontier. The Chauk report, if confirmed, would indicate a mass-casualty detention event targeting young resistance-affiliated personnel deep in the dry zone, well outside the Shan corridor that has anchored recent activity. Both remain unconfirmed and should not be treated as established facts.

Watch for second-source corroboration of the Kayin cross-border strike, particularly Thai military or provincial statements; Thai official acknowledgment would materially raise the incident's diplomatic weight. Watch for independent reporting on the Chauk casualties — identification of victims, unit affiliation, or imagery would move the event toward partial verification. Watch whether activity remains dispersed into Kayin and Magway or reverts to the Northern Shan baseline; sustained dispersion would indicate a broader operational footprint than the prior week suggested.

A verified Israeli drone strike on the Wadi Gaza bridge broke a period of low activity in central Gaza, while updated Ministry of Health figures indicate continued attrition under the October 2025 ceasefire.

A verified Israeli drone strike on the Wadi Gaza bridge in central Gaza hit a civilian vehicle with four missiles, killing one Palestinian and wounding four, per Wafa. This is the only kinetic event in the 24-hour window and represents a sharp deviation from the 0.1 events/day baseline for Central Gaza. Separately, the Gaza Ministry of Health released updated cumulative casualty figures — 73,221 killed and 173,643 wounded since October 2023, with 1,098 killed and 3,535 wounded attributed specifically to violations of the ceasefire in effect since 10 October 2025. That figure is partial-confidence (single-authority sourcing) but consistent with ongoing low-level strike activity. No reported events in Gaza City, Khan Younis, North Gaza, or the West Bank districts that carry non-zero baselines.

The Wadi Gaza bridge strike is a targeted engagement against a vehicle on a key north–south crossing in the central corridor, an area that has seen minimal reported activity in the baseline week. Combined with the Ministry of Health's ceasefire-period casualty tally, the day's reporting reinforces that the October 2025 ceasefire is being contested through discrete strikes rather than sustained operations. Absence of West Bank and Jerusalem District events breaks the low but persistent baseline in Ramallah and Hebron.

Watch central Gaza transit corridors, particularly Wadi Gaza and Salah al-Din Road, for follow-on strikes; a second targeted engagement would indicate a deliberate targeting pattern rather than an isolated incident. Watch for Israeli military statements claiming the Wadi Gaza vehicle as a designated target. Watch for renewed West Bank reporting from Ramallah and Hebron; continued silence would indicate a genuine lull rather than a reporting gap. Monitor Ministry of Health daily updates for acceleration in ceasefire-period casualty deltas.

A verified overnight strike ignited a fire at an industrial facility in Syzran, marking a sharp deviation from the 7-day baseline for Samara Oblast.

Samara Oblast registered one verified strike event in the reporting window, against a 7-day baseline of 0.1 events/day — a roughly 900% shift. Eyewitness footage from Syzran documented a fire at an industrial facility, attributed by local observers to a Ukrainian attack; the incident is corroborated across six sources. No verified activity was reported in the higher-baseline oblasts (Omsk, Moscow, Tatarstan, Tver, Voronezh, Saratov) during this window.

Syzran hosts refining and petrochemical infrastructure well east of the frontier, and a verified industrial-facility fire there extends the observed pattern of long-range strikes into the Middle Volga. The absence of concurrent verified activity in the usually more active western and Volga oblasts makes this single Samara event the defining data point of the period rather than one signal among many.

• Watch for follow-on imagery or official statements identifying the specific Syzran facility and damage scope; confirmation of refinery involvement would indicate a continuation of the energy-infrastructure targeting pattern.
• Watch for secondary reporting from neighboring Saratov and Tatarstan, whose baselines suggest routine activity that was absent this period; a return to baseline would indicate the Samara event was an isolated deep strike rather than part of a broader salvo.
• Watch for Russian air-defense or regional governor statements referencing additional intercepts along the Volga corridor overnight, which would indicate the Syzran strike was part of a wider, partially unreported wave.

No verified kinetic activity in Venezuela during the 24-hour window. A single unconfirmed fighting signal in Guárico is the only reported data point and is not sufficient to establish a trend.

Against a null 7-day baseline, one machine-generated clash signal was logged in central Venezuela, Guárico state (approx. 8°N, 66°W). The report is single-sourced (GDELT, CAMEO code 19) and unverified, with no identified actors, precise location, or operational detail. No corroborating human-sourced reporting has surfaced within the window. There are no other events — verified or partial — across the theater for this period.

Guárico is an interior llanos state that has not featured in the prior week's reporting, so even an unverified signal warrants noting as a possible new geographic data point. However, GDELT CAMEO-19 tags routinely capture policing incidents, criminal violence, and reporting artifacts rather than organized armed activity. Absent a named actor or second source, the signal carries no confirmed operational or strategic significance and should not be treated as evidence of a shift in the Venezuelan security picture.

• Watch for Spanish-language local press or state outlet reporting referencing incidents in central Guárico around 11 July; corroboration would upgrade the signal from artifact to a discrete incident.
• Watch for follow-on GDELT or ACLED entries clustering near 8°N, 66°W; repeat geolocated hits would indicate a persistent event rather than a one-off tag.
• Watch for actor attribution (state security forces, ELN, FARC dissident structures, or criminal groups); any named actor would reframe the incident's significance.
• Watch for silence: absence of further reporting within 72 hours would support treating the entry as a low-value artifact.

Reporting for the 24-hour window is limited to a single unconfirmed projectile impact in western Taiz; no verified activity was recorded across the theater.

A single-sourced, unverified report describes a Houthi projectile striking homes in al-Jubiya, Muqbana district, western Taiz countryside, with two civilian casualties reported (a 14-year-old and a 22-year-old, both wounded by shrapnel and evacuated to al-Fakika Medical Center). Taiz shows one reported event against no baseline activity for that governorate over the prior seven days. Al Hudaydah, which carried the only non-zero baseline (0.1 events/day), produced no reported events in this window.

The Muqbana report, while unverified, is the sole datapoint for the period and the only signal along the western Taiz frontline, an area not represented in the seven-day baseline. If corroborated, it would indicate indirect fire reaching populated villages behind the contact line rather than positional exchanges. Absent corroboration, it cannot support any assessment of a shift in Houthi targeting patterns, and the wider theater otherwise registers as quiet in the reporting stream.

• Watch for second-source confirmation of the al-Jubiya strike (medical facility intake records at al-Fakika, local council statements); corroboration would elevate Muqbana district as an active indirect-fire axis.
• Monitor whether additional impacts are reported elsewhere along the western Taiz countryside, which would indicate a sustained pattern rather than an isolated incident.
• Track Al Hudaydah reporting for a return to baseline; continued silence would suggest a genuine lull rather than a reporting gap.