UAF Deep Strikes Cripple RF Energy Grid and Shadow Fleet; Fuel Crisis Triggers Domestic Rationing
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 42.4 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
Analyst briefMachine-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 degradation of Russian Federation (RF) strategic energy and maritime logistics by Ukrainian Armed Forces (UAF) deep strikes. President Zelensky confirmed strikes on an oil refinery in Omsk (~2,500 km), alongside facilities in Rostov, Tver, Stavropol, Krasnodar, and Moscow. Concurrently, UAF Special Operations Forces (SBS) struck 13 RF shadow fleet vessels in the Sea of Azov and five electrical substations in occupied Crimea, causing a total blackout across occupied Kherson Oblast.
These kinetic actions have precipitated a systemic domestic fuel crisis within the RF. Regional authorities in Kirov, Novosibirsk, and Tomsk have implemented fuel rationing, remote work advisories, and "high readiness" modes to conserve supplies. This marks a transition from localized infrastructure damage to broad logistical strain, forcing RF civil defense resources to divert from frontline support to rear-area security.
On the ground, RF forces maintained high-tempo assaults, particularly in the Sloviansk and Pokrovsk directions, but achieved no verified strategic breakthroughs. RF Information Operations (IO) continue to claim advances in Kostiantynivka and Sumy, though geolocated evidence remains absent. The frontline remains largely static despite intense aerospace pressure involving Guided Aerial Bombs (KABs) and drone swarms.
Operational Updates
- Eastern Sector (Donetsk): RF launched 81 attacks across the front since morning. Highest intensity recorded in the Sloviansk direction (26 attacks) targeting Kryva Luka and Rai-Oleksandrivka, and the Pokrovsk direction (21 attacks) targeting Toretske and Hryshyne. UAF repelled the majority of assaults. RF IO claims small-team infiltration in Kostiantynivka, but independent verification indicates contested clearing operations rather than full control.
- Southern Sector (Zaporizhzhia/Kherson): RF conducted KAB strikes on Zaporizhzhia city center, resulting in one civilian death and multiple injuries. In occupied Kherson Oblast, a total power blackout persists across 426 settlements following UAF strikes on energy infrastructure. RF-installed governor Saldo confirmed the outage. UAF SBS also struck 13 shadow fleet vessels in the Sea of Azov.
- Northern Sector (Kharkiv/Sumy): RF Aerospace Forces used FAB-500 guided bombs to strike positions near Mayaki (DPR) and Zakharovka (Kharkiv Oblast). In Sumy Oblast, RF milbloggers claim advances near Bochkove and Volokhivske, threatening the road to Prykolotne; however, these claims lack independent geolocated confirmation and are assessed as IO exaggeration.
- Kursk Direction: No significant change in ground contact lines. UAF "Kursk" Group continues defensive operations. RF 32nd Air Defense Division Mobile Fire Groups (MOG) report non-payment of combat allowances, indicating growing friction within rear-area defense units.
Deep Strikes & Air Defense
- UAF Strategic Interdiction:
- Energy Infrastructure: President Zelensky confirmed strikes on the Omsk oil refinery, plus facilities in Rostov (Taganrog, Azov), Tver, Stavropol, Krasnodar, Saratov, Tatarstan, Bashkortostan, Voronezh, Moscow, Leningrad, and Bryansk. Fires confirmed at Taganrog and Azov oil depots.
- Crimea & Maritime: UAF SBS struck five 110/35 kV electrical substations in occupied Crimea (Berehove, Saky, Mainaky, Novoozerne, Medvedeve), causing widespread outages. SBS also destroyed 13 RF shadow fleet vessels (10 tankers, 1 dry cargo, 1 ferry, 1 tugboat) in the Sea of Azov.
- RF Aerospace Campaign:
- Civilian Targeting: RF launched multiple KAB strikes on Zaporizhzhia city center and Sumy Oblast. A jet-powered UAV struck Trostianets (Sumy Oblast). Smoke plumes reported in Kyiv region.
- Intercepts: RF MoD claimed interception of numerous UAVs, including four near Moscow. Flight restrictions at Zhukovsky Airport were lifted after overnight intercepts.
SAR Intelligence (Satellite Data)
- High Priority: SAR anomaly detection identified critical activity deviations at several locations. Notably, the 16th Separate EW Regiment (Belarus) showed a critical anomaly score (7.00), suggesting significant electronic warfare posture adjustments or equipment movement. The Western Operational Command HQ also showed elevated activity (Score: 2.47).
- Analysis: Elevated diff_scores at internal security (FSB) and communications nodes in RF rear areas correlate with the reported fuel crisis and deep strike impacts. No significant changes were detected at frontline command posts, confirming the static nature of ground contact lines. High noise indices in some acquisitions require cautious interpretation, but the consistency of anomalies at specific rear-area sites warrants monitoring.
Equipment & Losses
- RF Losses: UAF General Staff reports cumulative RF personnel losses reached ~1,412,250 (+1,200 in 24h). Specific equipment losses include 13 shadow fleet vessels in the Sea of Azov and multiple oil storage facilities in Rostov Oblast.
- UAF Losses: Confirmed loss of a UAF Mi-8 helicopter in Poltava Oblast (June 30 incident confirmed). Unconfirmed reports of Su-35 loss remain under verification.
- Corruption Disruption: NABU exposed a former Energoatom security director for laundering over 30M UAH via cryptocurrency. Separately, the Prosecutor General’s Office busted a UAF serviceman taking a $20,000 bribe to help an AWOL soldier avoid criminal liability.
Confidence Check
- UAF Deep Strike Confirmation: HIGH (Confirmed by President Zelensky and visual evidence of fires in Omsk, Stavropol, Tver, and Rostov).
- RF Fuel Crisis Impact: HIGH (Corroborated by Kirov, Novosibirsk, and Tomsk regional emergency declarations and fuel rationing measures).
- Kostiantynivka Control: LOW (RF claims of full capture or small-team infiltration lack independent geolocated confirmation; likely IO exaggeration).
- Su-35 Shootdown: LOW (Claimed by UAF 3rd Army Corps, but lacks visual verification).
The Bottom Line
The conflict continues to be defined by UAF strategic deep strikes degrading RF energy logistics at ranges exceeding 2,500 km, forcing Moscow to implement emergency domestic fuel security measures and rationing. In the next 24 hours, monitor:
- RF Fuel Logistics: Expansion of civilian fuel blockades and rationing in additional RF regions, and the impact on military supply chains.
- Crimean Grid: Verification of power restoration efforts in northern Crimea (Dzhankoi, Armyansk) to assess the durability of UAF interdiction.
- RF EW Deployment: Monitor for operational deployment of the alleged "Volna Kupol Garant" EW system claimed to target Starlink communications in the south, and verify RF advances in Sumy Oblast.
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.
Against the previous report from 09 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.
The latest control-map interval ended 42.4 hours before this report. These map dates may differ from the reporting period and do not establish when territorial changes occurred.
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 visualsGeospatial 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
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Omsk | RU | 54.9913545, 73.3645204 | |
| Rostov-on-Don | RU | 47.2357137, 39.701505 | |
| Kherson Oblast | UA | 0, 0 | |
| Sloviansk | UA | 48.8532, 37.6053 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Zaporizhzhia | UA | 47.83928419999999, 35.13870970000001 | |
| Crimea | RU | 45.3453029, 34.4997274 | |
| Sumy Oblast | UA | 0, 0 | |
| Kostiantynivka | UA | 48.52394289999999, 37.7075811 | |
| Tver | RU | 56.85872140000001, 35.9175965 | |
| Stavropol | RU | 45.0390116, 41.9631954 | |
| Kirov | RU | 58.6030012, 49.6679437 | |
| Novosibirsk | RU | 54.9832693, 82.8963831 | |
| Tomsk | RU | 56.4884295, 84.9480469 | |
| Sea of Azov | UA | 0, 0 | |
| Belarus | BY | 0, 0 |
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.
