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

Reporting over the 24-hour window indicates a direct US–Iran kinetic exchange spanning Hormozgan, Khuzestan, Kuwait, and Bahrain, with strikes on US bases in the Gulf and US strikes on Iranian coastal and refining infrastructure. All 11 events are partially sourced; none independently verified.

Hormozgan activity rose to five events versus a 3.0/day baseline, concentrated on Bandar Abbas, Qeshm Island, Sirik (Taheroi), and two separate engagements in the Strait of Hormuz — one involving Iranian drone and cruise missile fire at commercial shipping intercepted by CENTCOM, the other US strikes on IRGC boats and air defense nodes. Khuzestan jumped to two events (baseline 0.4), with reported US strikes on Abadan — site of Iran's largest refinery — and an agricultural pumping station in Mahshahr (one killed, four wounded per Iranian state media). Kuwait saw two reported strikes on US military facilities, including an IRGC claim of destroyed HIMARS launchers and an Israeli-media claim of US casualties relayed via Tasnim. Bahrain recorded island-wide air raid sirens and reported explosions at a US base. All reporting is partial, much of it single-chain via Iranian or Israeli outlets.

The reported target set — Abadan refining, Strait of Hormuz shipping, and US bases in Kuwait and Bahrain — spans energy infrastructure, maritime chokepoint security, and forward US posture simultaneously. If the Kuwait and Bahrain base strikes are corroborated, this represents the first cross-Gulf horizontal escalation in the period, extending the theater beyond Iranian territory and Hormuz waters.

Watch for independent confirmation of US casualties in Kuwait and damage assessments at Abadan; either would indicate escalation past prior thresholds. Monitor Strait of Hormuz shipping advisories and AIS anomalies — sustained interdiction would indicate a shift from harassment to closure posture. Track whether Bahrain and Kuwait issue follow-on alerts, which would indicate continued inbound threat activity rather than a single salvo.

Russian strikes concentrated on Odesa oblast port and civilian infrastructure over the 24-hour period, while a Ukrainian amphibious UGV insertion on the Kinburn Spit and reported fires at Kavkaz port indicate continued Ukrainian pressure on Russian southern logistics. All reporting is partial-confidence, multi-sourced.

Odesa oblast saw four discrete strike events against Odesa city, Chornomorsk and the Chornomorsk/Illichivsk port complex — roughly a fourfold increase over the 1.1/day baseline. Reported impacts include a car fleet, a sanatorium, a residential building, a bus depot (6 buses destroyed, 11 damaged) and a ferry struck by Geran-4 Seeker UAVs; at least eight civilians were reported injured across Odesa and Chornomorsk. Chernihiv registered a rare strike event knocking out power to more than 61,000 customers, well above its 0.1/day baseline. In Mykolaiv, Ukraine's 123rd Territorial Defence Brigade landed a UGV on the Kinburn Spit via naval drone — a first-of-type action in this dataset. On the Russian side of the Azov, NASA FIRMS thermal signatures at Kavkaz port and railway station suggest strikes on the tank farm and possible shadow-fleet tankers. Ground activity in Zaporizhzhia city (6 wounded) and Kostiantynivka (Russian clearing operations with civilian evacuation) tracked below or near baseline.

The Odesa cluster targets maritime logistics — port infrastructure, a ferry, and transport assets — consistent with sustained interdiction of Ukrainian seaborne trade. The Kinburn Spit UGV landing and Kavkaz port fires, if confirmed, extend Ukrainian unmanned reach into the northern Black Sea littoral and the Crimea rail-ferry corridor. Kostiantynivka clearing operations indicate continued Russian consolidation inside the urban area.

Watch for follow-on strikes on Odesa and Chornomorsk port facilities; repeat activity would indicate a sustained campaign against maritime throughput. Monitor damage assessments at Kavkaz port and any Russian acknowledgement — confirmation would indicate expanded Ukrainian targeting of the Crimea logistics bridge. Track whether the Kinburn Spit UGV landing is followed by additional unmanned insertions along the Dnipro estuary. In Donetsk, watch reporting from Kostiantynivka's northern districts; movement there would indicate the clearing phase is closing.

The NATO eastern flank period is defined entirely by unconfirmed, single-sourced reporting: allied ISR activity over the Baltics and near Kaliningrad, low-confidence "fighting" signals in Estonia, and an alleged Ukrainian drone strike on a Leningrad-region oil terminal mis-geocoded to Pskov. No verified kinetic activity on NATO soil.

There is no 7-day baseline for comparison; all activity registers as new signal rather than a measurable delta. Three separate GDELT "fighting" entries in Estonia (near 59°N, 26°E) on 8 July cluster on the same coordinates and timestamp but rest on 2–3 mentions each with no actor, weapon, or incident detail — likely echoes of a single underlying report, not three discrete clashes. Allied ISR posture shifted westward: a NATO reconnaissance aircraft redeployed from the Black Sea to overfly Lithuania, Latvia, and Estonia at ~10.5 km, and an RAF RC-135W Rivet Joint operated near Kaliningrad without reported intercept. In Lithuania, Vot Tak reporting describes a Russian sabotage recruitment network using mass Telegram posts to task low-level operatives (drone filming, vehicle arson). A drone strike on a port oil terminal is attributed to the Leningrad region in source text but geocoded to Pskov — location unresolved.

The Estonia "fighting" cluster is single-sourced and unverified; treating it as a real clash would be premature. The more operationally meaningful signal is the combination of westward NATO ISR reallocation and reporting of a standing Russian sabotage recruitment pipeline inside Lithuania — consistent with a hybrid, sub-threshold contest rather than conventional escalation. The Leningrad/Pskov terminal strike, if accurate, extends Ukrainian deep-strike targeting into Russia's northwest energy infrastructure adjacent to the flank.

• Watch for any second-source corroboration of the Estonia 8 July coordinates; independent confirmation would indicate a real incident rather than a GDELT artifact.
• Watch for Lithuanian or Latvian security-service statements on sabotage arrests; announcements would indicate the Vot Tak network is being actioned.
• Watch for sustained NATO ISR presence over the Baltics and Kaliningrad approaches; persistence beyond a single sortie would indicate a posture change, not a transit.
• Watch for Russian confirmation or denial of damage at Leningrad-region port oil infrastructure; clarification would resolve the Pskov geocoding ambiguity.

All seven reporting items in the 24-hour window are single-sourced and unverified, but they cluster into a geographically dispersed pattern of small-scale strikes across Syria alongside an unverified IRGC claim of missile and drone attacks on US bases in Jordan, Bahrain, and Kuwait.

Activity broadened beyond the Damascus-weighted 7-day baseline (0.4 events/day) into oblasts with no prior baseline entries: Deir ez-Zor (car IED), Daraa (armed clash in Tafas after an attack on an internal security patrol), As-Suwayda (vehicle-borne IED on the Damascus–Suwayda road, one killed), and Aleppo (armed attack on the Syrian Petroleum Company HQ in the countryside, reportedly following the recent killing of a defense ministry member). Homs registered a reported strike on Iraqi oil tankers on the Homs–Tartus highway. In Rif Dimashq, the toll from the earlier Palace of Justice bombing in Damascus reportedly rose to 14. Separately and outside Syria, the IRGC claimed large-scale missile and drone strikes on Prince Hassan Air Base (Jordan), a US drone command centre (Bahrain), and Ali Al Salem Air Base (Kuwait). All items are single-sourced and unconfirmed.

If corroborated, the Syrian incidents suggest simultaneous pressure on internal security (Tafas), energy infrastructure (Aleppo HQ, Homs–Tartus tankers), and transit routes (Suwayda, Deir ez-Zor), rather than a single front. The IRGC claim, if substantiated, would mark a regional escalation directly implicating US basing in the Gulf and Jordan.

Watch for second-source confirmation of the IRGC claim and any US, Jordanian, Bahraini, or Kuwaiti acknowledgement — official silence or denial would weigh against it. Watch Aleppo and Homs for follow-on strikes on energy infrastructure, Tafas for further security-force clashes, and Damascus/Rif Dimashq for revised casualty figures from the Palace of Justice bombing.

Ukrainian long-range drone activity concentrated on Stavropol Krai oil infrastructure in the last 24 hours, with a corroborated strike at Mikhaylovsk and a partially confirmed hit on a Stavropol city oil depot, alongside continued drone pressure on the Moscow region.

Stavropol Krai saw two strike events in the reporting window against a 7-day baseline of 0.4/day — a fourfold increase. The Mikhaylovsk oil depot incident is verified across five sources, while the Stavropol city oil depot strike, reported with a large fire and secondary explosions, remains partial at three sources with no casualty figures. In Moscow Oblast, a drone reportedly struck a residential apartment building in Solnechnogorsk; this remains partial (two sources), though Mayor Sobyanin's statement that 40 UAVs were downed over Moscow and the region since 22:00 provides context for a broader engagement, modestly above the 0.7/day baseline.

The Stavropol cluster marks a southward extension of strikes against Russian petroleum storage, roughly 500 km from the front and outside the more frequently targeted Voronezh–Saratov belt. Two near-simultaneous oil depot incidents in one krai — one verified — suggest a coordinated targeting effort against fuel logistics rather than an isolated event. The Solnechnogorsk report, if the residential impact is confirmed, would indicate either intercept debris or a terminal-phase failure inside a dense civilian area near the capital.

Watch for: independent imagery or fire-service confirmation of damage at the Stavropol city depot, which would upgrade that event from partial to verified; follow-on strikes elsewhere in Stavropol Krai or the North Caucasus, which would indicate a sustained campaign rather than a single night's tasking; and official Moscow-region casualty or damage disclosures for Solnechnogorsk, which would clarify whether the residential impact was from an interceptor or a leaker UAV.

Three single-sourced reports point to a possible drone-centric escalation in North Kordofan over the past 24 hours, all unverified. No corroborated activity was recorded elsewhere in Sudan during the period.

North Kordofan accounts for all three reported incidents in the period, against a 7-day baseline of roughly 0.1 events/day — a sharp reporting spike, though every item is single-sourced and unconfirmed. Reports describe drone and manned-aircraft attacks around Al-Abyad (El Obeid), the reported fall of a Chinese-made FH-95 heavy drone in the al-Quwayiz area of the Dar al-Rih badlands, and unspecified fighting elsewhere in Kordofan tied to a GDELT-detected reference to ongoing drone attacks. No casualty figures, force attributions, or independent confirmations are attached to any of the three. Blue Nile, the other recently active oblast in the baseline, generated no reported events during the window.

El Obeid is a strategic node on the Khartoum–Darfur axis, and the Al-Abyad report references roughly 100,000 displaced persons in and around the city, indicating elevated civilian exposure if the strike pattern is real. The reported recovery of an FH-95-class heavy drone, if authenticated, would speak to the tier of standoff systems now being employed in the Kordofan corridor. Because all three items are unconfirmed, they should be treated as an emergent signal to validate, not as an established shift.

Watch for second-source confirmation of the Al-Abyad strikes and any casualty or displacement reporting from humanitarian actors — corroboration would upgrade the North Kordofan spike from reporting artefact to genuine escalation. Watch for imagery or wreckage documentation from the al-Quwayiz area; authenticated FH-95 debris would indicate a change in the drone inventory in use. Watch Blue Nile for a return to baseline activity or continued silence.

Two single-sourced, unverified reports from Amran describe an intra-Houthi tribal clash in Khamer and accelerated Houthi force movements from northern Amran toward Marib. Both remain uncorroborated and are treated as watch items, not established facts.

There is no prior 7-day baseline for Amran; the governorate registers two reported incidents in this period, both unconfirmed and single-sourced. In al-Sintayn (Khamer District), a reported clash between tribesmen from Sheikh Dirham Sail's family and a Houthi arrest team over a water-well dispute allegedly left one Houthi operative dead and two wounded, followed by a siege on the sheikh's residence. Separately, reporting describes accelerated Houthi movements along the Harf Sufyan–Hawth–Khamer axis toward Marib, involving personnel, combat vehicles, medium weapons, UAVs, and missile platforms, alongside the reported appointment of a new Central Security Forces commander in Marib tasked with recruiting Sufyan tribes against tribal formations in Matrah al-Karama (Riyan). Neither report is corroborated by a second source.

If accurate, the Khamer incident would indicate friction between Houthi security organs and northern Amran tribal networks in the movement's own heartland. The reported Harf Sufyan–Hawth–Khamer buildup toward Marib, paired with a tribal-recruitment mandate, would suggest simultaneous force generation and internal coalition management along the Amran–Marib seam. Both readings hinge on evidence that does not yet exist in the public record.

Watch for second-source confirmation of the al-Sintayn siege and any casualty figures; sustained reporting would indicate a widening tribal-Houthi standoff in Khamer. Watch northern Amran routes toward Marib for imagery or local reporting of convoys, UAV or missile transporters, and fortification work; corroboration would indicate a genuine posture shift rather than isolated rumor. Watch for named confirmation of the new Central Security Forces appointment in Marib.

Reporting for the 24-hour period is sparse: a single unconfirmed clash signal near the Gaza Strip is the only entry, insufficient to establish a trend.

No verified or partially corroborated activity was recorded across the theater during the window. A single-sourced, unverified GDELT-derived signal indicated fighting in the vicinity of Gaza in the early hours of 13 July. No baseline exists for the prior seven days, so this cannot be characterized as an escalation or deviation — only as the sole data point on file. No operational details, actors, or effects are attached to the signal.

With zero corroborated events, the operating picture for the theater is effectively blank. The lone Gaza-vicinity signal is machine-derived from six mentions and lacks human confirmation, so it should not drive assessments on its own. The absence of baseline data further limits any comparative judgment; analysts should treat the current reporting environment as low-visibility rather than as evidence of quiet on the ground.

• Watch for second-source confirmation of the Gaza-vicinity clash signal; corroboration from local media, IDF statements, or Palestinian factional channels would upgrade it from a machine signal to a substantive event.
• Monitor whether additional GDELT or ACLED entries cluster around the same coordinates; repeat signals in the same grid would indicate a sustained contact rather than a transient artifact.
• Track official Israeli and Gaza-based communiqués for any acknowledgment of activity in the southern coastal strip during the reporting window; silence across official channels alongside continued machine signals would suggest a reporting gap worth flagging.
• Watch for baseline reconstitution as more data ingests; a persistent zero-verified state across 48–72 hours would itself be a notable collection anomaly.

The reporting period is effectively quiet across verified channels. The only signal is a single-sourced, unverified report of Tatmadaw clearance operations in Kani Township, Sagaing Region, tied to the India-Myanmar-Thailand highway corridor.

Against a 7-day baseline showing only marginal activity in Northern Shan State (0.1 events/day) and no prior baseline in Sagaing Region, one unconfirmed clash entry surfaced in Kani Township. The report describes three consecutive days of Myanmar military offensive clearance operations aimed at regaining control of the India-Myanmar-Thailand highway. This report is single-sourced and unverified, and no corroborating activity was logged elsewhere in the theater during the period.

If borne out, activity in Kani Township would indicate a regime effort to reopen a strategic overland trade axis running from India through Sagaing toward Thailand — terrain that has been contested by resistance formations. Because the reporting is unconfirmed and no other events were logged, the operational picture for the period cannot be characterized beyond this single lead. Analysts should treat the Kani signal as a tip, not an established pattern.

• Watch for independent corroboration of Tatmadaw clearance operations in Kani Township, particularly imagery, casualty reporting, or PDF/local statements. Multi-source confirmation would elevate this from a single-source lead to an established operation.
• Watch for secondary reporting along the India-Myanmar-Thailand highway axis in adjacent Sagaing townships; expansion would indicate a broader corridor-clearance campaign rather than a localized sweep.
• Watch for displacement reporting from Kani and neighboring areas, which would indicate sustained ground operations regardless of tactical outcome.
• Watch Northern Shan State for any deviation from its low baseline that could suggest coordinated pressure across fronts.

A partially corroborated Israeli drone strike on Sabra, Gaza City, coincided with a fresh military evacuation order for the same neighbourhood, marking the period's only reported kinetic event and a modest uptick over the Gaza City baseline.

Gaza City recorded one strike in the 24-hour window against a 7-day baseline of 0.4 events/day — a single-event uptick reported by three sources but still labelled partial. The Palestine Red Crescent Society reported at least two Palestinians killed and several wounded in the Sabra neighbourhood. The strike was paired with an Israeli evacuation order covering the same area, linking kinetic action to displacement pressure. No activity was reported in Khan Younis, North Gaza, Central Gaza, the Jerusalem District, Hebron, or Ramallah during the period, all of which remained at or below their low baselines.

The pairing of a strike with a concurrent evacuation order in Sabra suggests a shaping action rather than an isolated targeting event, consistent with prior patterns of ground-force preparation in Gaza City neighbourhoods. Because the event is partial rather than verified, casualty figures and intent should be treated as provisional. The absence of reported incidents elsewhere in the Strip and the West Bank leaves Gaza City as the sole active node in the reporting window, concentrating humanitarian and operational risk in one urban district.

Watch for follow-on strikes or ground movement in Sabra and adjacent Gaza City neighbourhoods; expansion of the evacuation zone would indicate a broader clearance operation. Monitor Red Crescent and hospital reporting for revised casualty counts that could shift the Sabra event from partial to verified. Watch the currently quiet West Bank districts of Hebron and Ramallah, and Khan Younis and North Gaza, for any renewed activity that would indicate the theater is not narrowing to Gaza City alone.

A single unconfirmed report of fighting in Caracas is the only signal for the period; no verified kinetic activity in Venezuela over the past 24 hours.

Against an empty 7-day baseline, one GDELT-aggregated event (CAMEO 19, "Fighting") was logged in Caracas, Distrito Capital, timestamped 13 July 03:00 UTC. The report is single-sourced and unverified, with no specified actors, location within the city, or casualty information. No corroborating open-source reporting is present in the input set. No activity is recorded elsewhere in the country.

The signal is too thin to support any operational assessment. A CAMEO 19 tag in a capital with no prior baseline activity is notable as a data point but, absent corroboration or specifics on parties involved, cannot be distinguished from criminal violence, a security-forces incident, or a reporting artifact. Its relevance is procedural: it establishes Caracas as a monitoring priority until confirmed or dismissed.

• Watch for secondary reporting from Venezuelan outlets or local social media corroborating or contextualising the Caracas fighting report; independent confirmation would indicate a genuine incident rather than an aggregation artifact.
• Monitor for identification of actors (state security forces, colectivos, criminal groups, or opposition-linked elements); attribution would sharply change the significance of the signal.
• Track whether additional CAMEO 18/19 events cluster in Distrito Capital in subsequent aggregation cycles; a repeat pattern would indicate a sustained security event rather than an isolated report.
• Absence of any follow-up reporting within 72 hours would suggest the initial signal was likely noise.