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

A verified overnight combined missile-and-drone barrage struck Kyiv, coinciding with elevated tempo across Donetsk, Zaporizhzhia, and — atypically — Sevastopol. Kostiantynivka remains contested despite Russian claims of near-completed clearance.

The Kyiv strike is the sole verified event of the period: a combined missile/drone barrage overnight into 6 July, corroborated by 14 sources. Partial follow-on reporting cites 12 killed, 49 injured, 30 residential buildings damaged, and Russian MoD claims of hits on seven defense-linked enterprises — casualty and target figures are single-track and unconfirmed.

Donetsk activity rose to 5 events (up 72% vs baseline), concentrated on Kostiantynivka, where partial sources report ongoing urban fighting, Russian infiltration, and attempted envelopment via Illinivka and Novodmytrivka; DeepState still assesses the city under Ukrainian control, contradicting Rybar's "nearing completion" characterization. Additional Ukrainian FPV strikes were geolocated at Novoekonomichne and Berezove, with a further unattributed strike near Kramatorsk.

Zaporizhzhia registered 3 events (up 87%): a Russian drone strike injured three in Zaporizhzhia city, while Ukrainian FPVs destroyed vehicles at Zapovitne and a fuel truck in Berdiansk — a rear-area logistics node. Sevastopol saw a partial-sourced Ukrainian drone attack on a MiG-29, a 900% deviation from baseline off a very low denominator. In Kharkiv, a Russian missile strike on Izyum killed one and injured three.

Two axes of pressure are corroborated: Russian long-range fires against Kyiv and rear cities (Izyum, Zaporizhzhia), and Ukrainian deep/tactical drone reach into occupied Zaporizhzhia and Crimea, including a claimed airframe strike at Sevastopol. Kostiantynivka is the decisive ground contest; competing narratives on its status matter for shaping the Donetsk operational picture.

Watch for independent confirmation of Kyiv damage to named defense enterprises; corroboration would indicate a shift from area to industrial targeting. Monitor Kostiantynivka for movement around Illinivka/Novodmytrivka — consolidation there would indicate encirclement progress. Track Sevastopol imagery for airframe-loss confirmation, and Berdiansk for follow-on strikes on fuel infrastructure.

All eight events in this 24-hour window are single-sourced and unverified. The only structurally notable signal is repeated reporting of Israeli ground movement and checkpoint activity in the Quneitra countryside on the Syrian side of the Golan.

Activity is dispersed across five districts with no verified events. Two unconfirmed reports describe Israeli forces advancing near Sidna Golan and installing a checkpoint on the road to Saida al-Jolan in the Quneitra countryside — a geography absent from the 7-day baseline. Two unconfirmed GDELT-coded fighting signals cluster on identical coordinates (31.5, 34.75) covering the Gaza Strip and Gaza periphery in Southern District; one linked article references roughly 100 Israeli settlers detained, hinting at settler-related unrest rather than cross-boundary combat. Two separate GDELT assault codes were logged in Tel Aviv within a 21-hour span, with no actor or casualty detail. One assault code was logged in Galil (Northern District), nominally a 900% rise against a 0.1/day baseline but resting on a single machine-coded item.

The Quneitra reporting, if borne out, would indicate continued Israeli ground presence beyond the 1974 line and active route control in southern Syria. The paired Gaza-coordinate signals and the settler-detention reference suggest internal public-order friction distinct from militant activity, but the shared coordinates and CAMEO coding limit independent value. Tel Aviv and Galil assault codes are too thin to support interpretation.

Watch for second-source confirmation of the Sidna Golan and Saida al-Jolan checkpoint reports; Syrian state or municipal accounts corroborating either would upgrade the Quneitra signal. Watch for clarifying reporting on the Southern District settler-detention reference — Israeli police statements would indicate a domestic public-order track. Watch whether Tel Aviv and Galil assault codes attract any human-sourced follow-up or remain GDELT-only artifacts.

Reporting over the past 24 hours describes a sharp uptick in activity across North Kordofan and North Darfur, but all seven events are single-sourced and unverified. Signals cluster around al-Abyad/El Obeid and the Tine–Um Baro corridor, and should be treated as leads pending corroboration.

North Kordofan saw five reported incidents against a 7-day baseline of 0.3/day, and North Darfur two against the same baseline. In North Kordofan, single-sourced reports describe unspecified fighting in El Obeid, artillery shelling killing three civilians in al-Dalinj, a village attack in Ambro locality with 10 killed and 6,000 displaced from Kalbus, and a UNICEF statement citing drone strikes and shelling placing roughly 500,000 civilians at risk. Separately, the Sudanese Armed Forces claimed control of all combat axes in al-Abyad, coinciding with a UN Humanitarian Coordinator visit. In North Darfur, reporting describes RSF attacks on six villages near Tine driving cross-border displacement into Chad, and approximately 3,600 people displaced from Wadi Funqu in Um Baro locality. None of these accounts are corroborated in the input set.

If borne out, the North Kordofan cluster would indicate simultaneous SAF consolidation around al-Abyad/El Obeid and continued attritional harm to civilians via shelling and drone strikes. The Tine reporting, if confirmed, would mark a cross-border displacement event with humanitarian implications for eastern Chad. The concentration of unverified reporting itself is notable given the low baseline.

• Watch for second-source confirmation of the SAF claim over al-Abyad; independent verification would indicate a substantive front-line shift in North Kordofan.
• Watch for corroboration of the Tine attacks and Chad border crossings from humanitarian actors; confirmation would indicate widening displacement pressure.
• Watch for follow-on reporting on Kalbus and Wadi Funqu displacement figures; consistency across sources would raise confidence in the scale claimed.

All reporting for the period is single-sourced and unverified, but the geographic center of activity has shifted north to Hama, Idlib, and Homs — oblasts absent from the 7-day baseline — with explosive remnants of war (ERW) and IED incidents dominating the signal.

The prior 7-day baseline concentrated activity in Damascus, As-Suwayda, Daraa, Deir ez-Zor and Rif Dimashq. During this 24-hour window, none of those governorates registered events in the supplied list. Instead, Hama recorded three unconfirmed incidents (an engineering-team injury while defusing an IED in Hama city, a reported dismantling of a seven-member "assassination cell" in the al-Ghab area, and two children injured by war remnants in al-Latamneh), Idlib recorded two (a mine detonation inside the home of a former regime pilot in Kafrnabel, and explosions near Ariha coinciding with drone activity overhead), and Homs recorded one (further reported EOD-team fatalities from mine blasts in Maheen, per SOHR). All six are single-sourced.

Three of the six incidents (Hama city, al-Latamneh, Maheen) involve ERW or demining casualties, suggesting the operational burden on engineering teams is a recurring cost rather than an isolated event. The Kafrnabel mine — targeting a former regime pilot's residence — and the reported al-Ghab cell arrests point to a parallel track of targeted violence and counter-network activity in the northwest. The Ariha explosions with concurrent drone overflight are the only indication of possible aerial action but remain uncorroborated.

Watch for second-source confirmation of the Ariha drone-linked explosions; corroboration would indicate a shift beyond ERW-driven casualties. Monitor whether Hama and Idlib sustain elevated reporting — continuation would indicate a durable northward redistribution rather than a one-day artifact. Watch for follow-on reporting on the al-Ghab arrests and any claim of responsibility for the Kafrnabel mine.

Three single-sourced, unconfirmed reports across Sagaing, Ayeyarwady and Magway suggest simultaneous pressure on regime positions and a mass-displacement airstrike event, but none are corroborated and all should be treated as watch items pending verification.

Reporting volume rose against a near-zero 7-day baseline, with activity appearing in two regions (Ayeyarwady, Magway) that had no prior baseline events. In Indaw Township, Sagaing Region, the regime claimed recapture of Maze and Nanthe villages along the Myitkyina–Shwebo road — a claimed reversal of resistance control, single-sourced and unverified. In Yegyi Township, Ayeyarwady Region, the Arakan Army claimed seizure of two military outposts near the Gwa (Rakhine) boundary, describing it as escalation; also single-sourced. In Chauk, Magway Region, airstrikes and resulting fires were reported to have burned hundreds of homes and displaced roughly 10,000 people from at least ten villages — likewise unconfirmed.

If borne out, the three reports would sit on separate strategic axes: a regime counter-move along the Sagaing rail/road corridor, an AA push westward from Rakhine into the Ayeyarwady delta, and a high civilian-impact air campaign in the central dry zone. Even absent corroboration, the geographic spread — north, southwest coastal fringe, and central Myanmar — is inconsistent with a single localized flare-up and, if verified, would indicate concurrent pressure on multiple regime sectors.

Watch for second-source confirmation of the Indaw village claims from resistance or local monitors; independent confirmation would indicate a genuine regime advance on the Myitkyina–Shwebo axis. Watch for AA follow-on reporting in Yegyi and any spillover toward Gwa. Watch for humanitarian and satellite-derived fire/burn-scar reporting from Chauk; corroboration would indicate the displacement figure is credible.

Single-sourced Russian official reporting describes a UAV attack on Leningrad Oblast port and range infrastructure overnight 6 July, with no independent corroboration at this time.

Leningrad Oblast, which carried no baseline activity over the prior 7 days, saw two unconfirmed reports in the period. Governor Drozdenko announced an attack on the Port of Ust-Luga and the Luzhsky training range at 05:07 UTC; a follow-on statement claimed 56 AFU UAVs were downed across Luzhsky Polygon, Ust-Luga and Vysotsk, with damage at all three sites and reported internet outages in Saint Petersburg. Both reports are single-sourced to Russian regional authorities and remain unverified. No weapon types, imagery, or casualty details have been released.

If borne out, the targets — a Baltic export port, an LNG/oil terminal at Vysotsk, and a major ground-forces range — would represent a notable geographic extension of AFU deep-strike reach into the Leningrad region and against NATO-adjacent energy infrastructure on the Gulf of Finland. The claim of associated connectivity disruption in Saint Petersburg, if accurate, would also point to secondary effects beyond the immediate strike footprint. Absent corroboration, the reporting currently supports only that Russian authorities are publicly acknowledging an incident.

Watch for: independent imagery or vessel-tracking data from Ust-Luga and Vysotsk that would confirm or refute infrastructure damage; Ukrainian General Staff acknowledgement, which would upgrade attribution; NOTAM, port-closure or insurance advisories on the eastern Gulf of Finland, which would indicate sustained disruption; and any repeat Russian air-defence claims over Leningrad Oblast, which would indicate this is a campaign rather than a single event.

A verified refinery strike in Yaroslavl and a partially corroborated drone interception series over Moscow mark a coordinated overnight long-range strike wave against central Russian energy and capital-area targets.

Yaroslavl saw a verified strike on a refinery in the early hours of 6 July, a roughly ninefold jump over the 0.1/day 7-day baseline and the first confirmed refinery impact in the oblast during the observed window; weapon type, casualties, and damage extent are not reported. Over Moscow, Mayor Sobyanin's statement (partial, two sources) reported four additional drones downed with emergency crews at debris sites — a modest uptick against the 0.7/day baseline but consistent with sustained targeting of the capital. No other oblasts registered activity in this period despite recent baseline presence in St. Petersburg, Nizhny Novgorod, Leningrad, Penza, Udmurt Republic, and Zaporizhzhia.

The Yaroslavl refinery hit extends the geographic reach of confirmed strikes on Russian downstream energy infrastructure well north of previously higher-tempo corridors. Paired with the Moscow air-defense engagements the same night, the pattern suggests simultaneous pressure on capital-region defenses and on refining throughput. Because Yaroslavl damage specifics remain unreported, operational impact on refinery output cannot yet be characterized.

Watch for follow-on imagery or official statements quantifying damage at the Yaroslavl refinery; confirmation of processing unit or storage damage would indicate durable throughput loss. Monitor Moscow-region air-defense reporting for repeat overnight engagements, which would indicate a sustained rather than one-off wave. Track whether oblasts absent from this period's list — particularly St. Petersburg, Nizhny Novgorod, and Leningrad — re-enter reporting, which would indicate broadening rather than concentration of the strike axis.

A single partially corroborated Israeli airstrike on al-Nabatieh al-Fouqa in South Lebanon is the only recorded activity in the theater for the period, marginally above the 7-day baseline for that oblast.

South Lebanon registered one strike event at al-Nabatieh al-Fouqa on 6 July, reported by Lebanese outlets via Tasnim and rated partial (two sources). This brings the day's tally to roughly 43% above the 0.7 events/day baseline for the oblast — a single-event delta rather than a pattern shift. No activity was recorded in the other baseline oblasts (West Azerbaijan, Hormozgan, Kermanshah, Tehran, Northern District, Quneitra, Erbil, Blue Nile, or the Red Sea off Al Hudaydah) during the period.

The al-Nabatieh al-Fouqa strike, while single-incident and only partially verified, sustains the pattern of Israeli air activity over South Lebanon at roughly baseline tempo. Its operational significance is limited on its own: sourcing is Lebanese media relayed through Tasnim, target and effects are not independently confirmed, and no follow-on kinetic activity elsewhere in the theater accompanied it during the 24-hour window.

Watch for additional corroboration of the al-Nabatieh al-Fouqa strike from Israeli or Lebanese official channels — confirmation of target type or casualties would upgrade confidence. Monitor whether strikes in South Lebanon cluster over successive days; repeated activity in the Nabatieh area would indicate a deliberate tempo rather than an isolated event. Watch the quiet Iranian oblasts (Tehran, Kermanshah, Hormozgan, West Azerbaijan) for any reporting break, as absence of events is itself a baseline indicator here.

A single partially corroborated Israeli airstrike on a residential apartment in southern Gaza City killed two and injured others, consistent with — and marginally above — the 7-day baseline of scattered strikes across the Gaza Strip.

One partially confirmed strike hit a residential apartment in the southern part of Gaza City in the early hours of 6 July, per Al-Shifa hospital sources cited across two reports. This nudges Gaza City activity to roughly 67% above its 7-day average of 0.6 events/day, though a single event over a 24-hour window is not a statistically meaningful departure. No new activity was reported from Khan Younis, the Southern District, or the West Bank governorates of Hebron and Nablus during the period, leaving their baselines unchanged. Reporting characterizes Israeli operations as continuing "scattered attacks" across the Strip rather than a concentrated escalation.

The strike reinforces a pattern of residential-building targeting in Gaza City with civilian casualties reported by hospital sources — the dominant signature of the current baseline. Because the event is only partially corroborated and hospital-sourced, casualty figures should be treated as provisional. The absence of reported West Bank incidents during the period is notable given Hebron and Nablus each carried a 0.1/day baseline, but a 24-hour gap is within normal variance and not itself indicative of de-escalation.

Watch for: independent confirmation or revision of the Gaza City apartment strike casualty count; whether follow-on strikes cluster in southern Gaza City neighborhoods, which would indicate a localized targeting focus rather than dispersed activity; any resumption of reporting from Khan Younis or the Southern District; and whether the West Bank quiet period extends, as a multi-day absence in Hebron and Nablus would represent a meaningful deviation from baseline.

Reporting for the period is effectively empty: a single unconfirmed assault signal near La Guaira is the only item on the wire, and no verified activity is available to characterize the theater.

Against a null 7-day baseline, one single-sourced and unverified assault signal surfaced in La Guaira, Vargas, on 5 July, derived from a GDELT CAMEO-18 tag with three mentions and a mildly negative tone. No corroborating reporting has emerged, and no other incidents were logged in the period. The "shift" in Vargas reflects the absence of prior baseline data rather than a measurable escalation.

With zero verified or partially verified events, the period offers no basis to assess a change in the Venezuelan security environment. The La Guaira signal is noteworthy only because Vargas hosts Maiquetía international airport and the country's principal Caribbean port complex, so even low-confidence indicators there warrant tracking. Absent a second source, the item cannot support any operational or strategic conclusion.

• Watch for secondary reporting on the La Guaira incident from Venezuelan outlets, local social media, or port and aviation channels; corroboration would upgrade the signal from noise to a discrete security event.
• Monitor for any follow-on activity around Maiquetía airport and the Vargas port corridor; repeat CAMEO-18 signals in the same node would indicate a possible pattern rather than an isolated artifact.
• Track whether the current reporting drought reflects a genuine lull or a collection gap; a sudden influx of backdated items would suggest the latter.

A single partially corroborated maritime incident off Hodeida is the only reportable activity in the period, breaking an otherwise quiet 7-day baseline in Al Hudaydah.

One partial-confidence event was logged in Al Hudaydah governorate on 5 July: a cargo ship reportedly attacked in the Red Sea off the Yemeni coast, referenced via a British military report cited by The Hindu and coded as a clash near Hodeida. This is a 900% deviation from the 7-day baseline of 0.1 events/day, though the absolute count remains one. No ground-based clashes, strikes, or casualty reports are present in the input for this period. The incident is two-sourced but not independently verified as to vessel identity, attacker, weapon type, or precise location.

Red Sea shipping off Hodeida remains the primary vector by which Yemen-based activity generates international effect. Even a single partially confirmed attack resets assumptions built during the quiet baseline week and re-engages naval reporting channels (UKMTO-style advisories reflected in the British military reference). Absent corroborating detail on the vessel or attacker, the event's strategic weight is limited to signaling that interdiction capability off Hodeida is still active rather than dormant.

• Watch for follow-on maritime advisories or claims of responsibility tied to the Hodeida-area attack; attribution to a named actor would upgrade the event beyond partial confidence.
• Watch for identification of the struck cargo vessel and flag; a Western-linked hull would indicate continuity with prior Red Sea targeting patterns.
• Watch for any coastal or airstrike activity in Al Hudaydah governorate in the same window; concurrent land activity would indicate the maritime incident is not isolated.
• Watch for silence across the next 48 hours, which would indicate the deviation from baseline is a one-off spike rather than a resumed tempo.