Daily intelligence

UAF Deep Strikes Breach Belgorod Reservoir Dam; RF Claims Maritime Interdiction in Black Sea

Published Intelligence Summary & Geospatial Analysis
Report number
747

At a glance

Counts of the stored claim records and follow-up, not a summary of the narrative. How to read these labels

Coverage window
Not stored for this report.
Follow-up investigation
None stored for this report.
Claim records by status
This report has no claim records.
Claim records by confidence
This report has no claim records.
SAR measurements
None supplied to this report. No SAR measurements for this period does not mean that monitored sites were unchanged.
Frontline map data
Newest map data is 21.0 h older than this report.

Read with these limits in mind

  • This report is machine-generated from open sources and may contain errors.
  • A source’s publication time is not the time of the event it describes.
  • Frontline map data can lag the reporting period; map dates do not establish when territory changed.
  • No SAR measurements for this period does not mean that monitored sites were unchanged.

Intelligence Summary

Machine-generated narrative. Labels inside it are written by the model. How to read these labels

Strategic Overview

The most significant operational development of the last 24 hours is the confirmed structural breach of the Belgorod reservoir dam (Shebekinsky district) following Ukrainian Armed Forces (UAF) drone strikes, causing uncontrolled water discharge and localized flooding. This event marks a tangible escalation in UAF interdiction of critical rear-area infrastructure, compounding existing logistical friction for Russian Federation (RF) forces in the border region. Concurrently, RF forces intensified aerospace saturation strikes against Ukrainian urban centers, inflicting confirmed casualties in Zaporizhzhia and damaging mobilization infrastructure in Chernihiv, while claiming successful maritime interdiction of commercial vessels in the Black Sea.

Ground operations remain characterized by high-tempo attritional assaults in the Pokrovsk and Sloviansk directions, with no verified territorial changes despite RF claims of advances in Volokhovske (Kharkiv Oblast). The RF reliance on massed guided aerial bombs (KABs) and loitering munitions continues to offset frontline stagnation, while UAF deep-strike campaigns increasingly target dual-use logistics nodes, including railway bridges and warehouse complexes in RF interior regions.

Operational Updates

  • Eastern Sector (Donetsk): RF maintained intense pressure with sustained assaults in the Pokrovsk and Sloviansk directions. UAF General Staff reported repelling numerous attacks, with heavy fighting concentrated around Kostiantynivka and Chasiv Yar. No independent geospatial verification confirms RF territorial gains despite milblogger claims of localized advances near Rai-Oleksandrivka.
  • Northern Sector (Kharkiv/Sumy): RF claimed the capture of Volokhovske (Kharkiv Oblast) by the 127th Motorized Rifle Regiment, setting conditions to encircle Bilyi Koloziy; this claim remains unverified by independent OSINT. UAF Air Force tracked multi-vector UAV threats towards Kharkiv, Sumy, and Chernihiv, with KAB strikes reported in eastern Kharkiv Oblast and Sumy.
  • Southern Sector (Zaporizhzhia/Odesa/Kherson): RF struck residential areas in Zaporizhzhia city with KABs, resulting in 3 dead and 13 injured. In Odesa, RF launched Onyx missiles and Shahed drones towards port infrastructure, with explosions reported in the port area and unverified claims of a ship being hit. UAF conducted drone strikes on occupied Tokmak, damaging residential buildings.
  • Central Rear (Kyiv/Chernihiv): A "reactive Shahed" loitering munition struck a Territorial Recruitment Center (TCC) building in Chernihiv city, causing severe structural damage. UAF Air Force tracked jet-powered UAVs approaching Poltava Oblast from the northeast.

Deep Strikes & Air Defense

  • UAF Deep Strikes:
    • Belgorod Oblast: Visual evidence confirms a 35-meter breach in the Belgorod reservoir dam following earlier UAF drone strikes, causing flooding in Bezlyudovka and Grafovka. Updated casualty figures from 153 drone attacks in the region stand at 9 dead and 80 injured.
    • Logistics Interdiction: UAF Special Operations Forces (SSO) announced Operation "Conductor," claiming the destruction of 13 railway bridges targeting RF logistical arteries, supported by thermal footage.
    • Kursk Oblast: UAF 15th Separate Artillery Reconnaissance Brigade claimed a drone strike on Khalino airfield, reporting the destruction of a MiG-29 fighter jet and a Pantsir-S1 air defense system; RF MoD acknowledged the strike but did not confirm equipment loss.
    • RF Interior: Fires reported at industrial facilities in Lipetsk and St. Petersburg ("Ladoga" industrial park), and a Wildberries warehouse in Elektrostal (Moscow Oblast).
  • RF Aerospace Campaign:
    • Maritime Interdiction: RF MoD claimed strikes on port infrastructure in Odesa and Chornomorsk, and on a bulk carrier in Mykolaiv port. The Liberian-flagged gas carrier Gas Lisbon sustained damage from a suspected sea mine explosion off the Romanian coast; all crew evacuated.
    • Urban Strikes: Sustained KAB and drone strikes on Zaporizhzhia, Chernihiv, and Kharkiv oblasts. RF MoD claimed interception of 209 UAF UAVs overnight across multiple regions.

SAR Intelligence (Satellite Data)

  • High Priority:
    • 16th Separate EW Regiment (Belarus): A critical anomaly (Score 6.66) was detected at this facility, indicating significant activity deviating from historical baselines. This requires monitoring for potential regional spillover or force generation activities.
    • Air Force Equipment Storage Base (1060th Logistics Center): Anomaly score of 0.65 indicates notable activity, though below critical thresholds.
  • Analysis: The high anomaly score at the Belarusian EW regiment suggests increased electronic warfare posture or training activities, contradicting public narratives of de-escalation. No significant changes were detected at frontline RF logistics hubs, suggesting stable baseline activity there despite rear-area disruptions.

Equipment & Losses

  • RF Losses:
    • Infrastructure: Belgorod reservoir dam breached; fires at "Ladoga" industrial park (St. Petersburg), Lipetsk CHP, and Wildberries warehouses in Tambov and Moscow Oblasts.
    • Equipment: UAF 15th Brigade claimed destruction of a MiG-29 and Pantsir-S1 at Khalino airfield (Unconfirmed: requires satellite verification). UAF 68th OAMBr destroyed a RF BM-21 Grad MLRS via FPV drone.
    • Maritime: Gas Lisbon gas carrier damaged by suspected mine (Unconfirmed: cause pending investigation).
  • UAF Losses/Damage:
    • Civilian Casualties: 3 dead, 13 injured in Zaporizhzhia KAB strikes; structural damage to TCC in Chernihiv.
    • Infrastructure: Water supply disruption in Dniprorudne (Zaporizhzhia Oblast) due to reported accident.

Confidence Check

  • Belgorod Dam Breach: HIGH (Confirmed by visual evidence and local reporting).
  • Zaporizhzhia/Cernihiv Strikes: HIGH (Confirmed by local oblast administrations and emergency services).
  • Khalino Airfield Strike: MEDIUM (Strike acknowledged by RF; specific equipment destruction claims by UAF remain unconfirmed).
  • RF Advances in Volokhovske: LOW (RF claims only; lacks independent geospatial verification).
  • Maritime Vessel Damage: MEDIUM (Incident confirmed by Romanian media; attribution to mine vs. strike remains under assessment).

The Bottom Line

The conflict trajectory continues to feature asymmetric UAF deep strikes degrading RF strategic infrastructure (Belgorod dam, railway bridges), while RF forces rely on massed aerospace attacks against Ukrainian civilian and mobilization infrastructure to offset frontline stagnation. In the next 24 hours, monitor:

  1. Belgorod Flooding Impact: Assessment of the operational impact of the reservoir breach on RF logistics and troop movements in the Shebekinsky district.
  2. Maritime Logistics: Verification of damage to the Gas Lisbon and any subsequent disruptions to grain/fuel imports via Reni/Odesa ports.
  3. RF EW Posture in Belarus: Further intelligence on the activity spike at the 16th Separate EW Regiment to determine if it signals imminent cross-border operations or enhanced defensive posturing.

Legacy provenance

This archived report predates claim-level evidence records. Treat its confidence labels as editorial assessments rather than independently verifiable citations.

Frontline context

Territorial control and recent changes shown by DeepState.

Report 21 Jul 2026, 15:06 UTCLagged by 21.0 h
Map revision comparison

Against the previous report from 20 Jul 2026, 15:07 UTC, bright red is newly marked Russian-occupied and green is no longer marked occupied. For the infiltration area, yellow is this report and cyan is the previous report.

Compare on map

The latest control-map interval ended 21.0 hours before this report. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+2.4 km²
24 h ending 20 Jul 2026, 18:05 UTC
Daily net
+2.4 km²
24.3 h comparison
Seven-day net
-25 km²
173.8 h comparison
Largest changes in the latest measured interval
Near Siversk
2.4 km² changed · RF-held gained 2.4 / lost 0.0 km²

Positive values indicate an increase in Russian-occupied area; negative values indicate a decrease. Yellow marks DeepState's infiltration area (gray zone), which is not included in occupied-area totals.

Report Visuals

5 visuals
Open full size
Nightwatch daily report #747: Pokrovsk area

Geospatial Analysis

16 locations identified

Historical reconstruction from source editions available by report time.

Places and data export

Coordinates come from geocoding place names found in the report. They locate the named place, not the event described there. Latitude and longitude are WGS 84 decimal degrees.

Show 16 places with coordinates
Geocoded places in report 747
PlaceCountryLatitude, longitudeCopy
Belgorod Reservoir DamRU50.4482688, 36.7224818
PokrovskUA48.282193, 37.1847804
SlovianskUA48.8532, 37.6053
KostiantynivkaUA48.52394289999999, 37.7075811
Chasiv YarUA48.5884808, 37.8354218
VolokhovskeRU0, 0
Bilyi KoloziyUA0, 0
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
ChernihivUA51.4982, 31.28935
Odesa PortUA0, 0
TokmakRU47.2464085, 35.7098364
Khalino AirfieldRU51.7522919, 36.3142632
Ladoga Industrial ParkRU0, 0
ElektrostalRU55.7835532, 38.4551611
16th Separate EW RegimentBY0, 0
Gas LisbonRO38.7222524, -9.1393366

How to read the labels

Labels on this page come from three separate mechanisms. A label from one does not mean the same as a similar word from another.

1. In the narrative

Machine-generated narrative. Labels inside it are written by the model.

Unconfirmed:
Written by the model. Its instruction is to mark claims that rest on a single source.
Confidence: HIGH / MEDIUM / LOW
Written by the model. The report stores no definition of these levels, and they are not computed from the claim records. Do not read them as the record confidence above.

2. On claim records: confidence

Record confidence is a threshold on a number stored with the source observation. It is not a probability that the event happened. The follow-up investigation may lower it and never raises it.

HIGH confidence
The status is Independently corroborated, Geolocated or Imagery corroborated, and the stored confidence of the supporting observation is at least 0.75.
MEDIUM confidence
The stored confidence of the supporting observation is at least 0.5 and the rule for HIGH is not met.
LOW confidence
The stored confidence of the supporting observation is below 0.5.

2. On claim records: status

Machine-selected records from the source ledger, labelled by fixed rules. They are a separate selection and are not a list of the sources behind the narrative above.

Single-source claim
One retained source observation supports the record, from a sender that is not on the list of official bodies.
Official claim
One retained source observation, from a sender whose name matches a keyword list of official bodies. It says who made the claim, not that the claim is verified.
Multiple reports, same origin
Several retained observations that do not meet the rule for independent corroboration. They are treated as one origin.
Independently corroborated
At least two distinct source documents from at least two differently named senders. The rule compares sender names and document fingerprints. It does not establish that the senders had separate access to the event, and a repost under another name can satisfy it.
Geolocated
One retained observation carrying coordinates with a geolocation confidence of at least 0.5. It concerns the location only, not the cause or the outcome.
Imagery corroborated
Imagery supports the observation. It does not by itself establish cause or intent.
Analyst assessment
A Nightwatch assessment rather than a directly observed fact.
Contested
Set by the follow-up investigation: material source accounts remain in conflict.
Corrected
Set by the follow-up investigation: the record was changed after the investigation reached a definitive answer.
Insufficient evidence
Set by the follow-up investigation: the available evidence does not support the record as first labelled.

3. In the follow-up investigation

Machine-run follow-up on one selected claim record. Sources listed include material that was retrieved and not used.

Confirmed
The investigation reached a definitive answer supporting the selected claim. The report was rewritten after it.
Refuted
The investigation reached a definitive answer against the selected claim. The report was rewritten after it.
Materially refined
The investigation reached a definitive answer that changes the selected claim in a material way. The report was rewritten after it.
Inconclusive
The investigation did not reach a definitive answer. The report text was kept; the investigation could only attribute, hedge or lower confidence. Individual findings inside it can still carry their own outcome.

Each finding has its own outcome and a confidence written by the model. That confidence is in the finding as worded, which may itself be a statement that something is unknown.

Kinds of investigation source

External web page
A web page retrieved during the follow-up investigation. Its address is stored and linked.
Source observation behind a claim record
A source observation the claim records were built from. No address is stored for it.
Nightwatch archive item
An item found by searching the Nightwatch archive during the investigation. It may be unrelated to the question. No address is stored for it.