Daily intelligence

Maersk Suspends Odesa Operations; UAF Leadership Consolidates Amidst Deep Strike Campaign

Published Intelligence Summary & Geospatial Analysis
Report number
748

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 24.5 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 suspension of Maersk shipping operations at Chornomorsk and Odesa ports, with vessels redirected to Constanta, Romania. This decision follows sustained Russian Federation (RF) aerospace strikes on port infrastructure and maritime logistics, including the confirmed strike on the bulk carrier GOLDEN LEO. This marks a tangible degradation of Ukraine’s primary maritime export corridor, forcing a shift to overland and Danube riverine routes.

Concurrently, the Ukrainian Armed Forces (UAF) have stabilized their command structure following recent transitions. President Zelenskyy appointed Maj Gen Igor Skibyuk as Chief of the General Staff, while Acting Defense Minister Yevhen Khmara and new Commander-in-Chief Mykhailo Drapatyi formalized their joint strategic priorities, emphasizing technological pressure and air defense integration. Despite this internal consolidation, RF forces intensified ground claims in Kharkiv and Zaporizhzhia oblasts, though independent verification remains lacking.

In the deep rear, UAF drone campaigns continued to disrupt RF logistics, causing confirmed fires and casualties at facilities in Krasnodar, Armavir, and Nevinnomyssk. RF retaliatory aerospace saturation strikes targeted Zaporizhzhia and Kharkiv, inflicting civilian casualties and damaging critical industrial nodes, including the "Olis" food processing enterprise.

Operational Updates

  • Eastern Sector (Donetsk): RF maintained high-tempo attritional assaults. The UAF General Staff reported repelling 19 attacks in the Pokrovsk direction and 17 in the Sloviansk direction. Small-group infantry infiltrations were noted near Sofiivka and Rodinske, heavily interdicted by UAF drone units. No verified territorial changes occurred despite RF claims.
  • Northern Sector (Kharkiv/Sumy): RF MoD claimed the capture of Artelne (Kharkiv Oblast) by the 34th Guards Motor Rifle Brigade and 11th Tank Regiment; this claim remains unverified by independent OSINT. KAB strikes hit residential areas in Kharkiv city (Saltivskyi and Nemyshlianskyi districts), causing fires. UAV threats were tracked towards Sumy and Chernihiv.
  • Southern Sector (Zaporizhzhia/Odesa/Kherson): A strike on the "Olis" food processing enterprise in Zaporizhzhia caused a 1,000 sqm fire, killing 1 and injuring 3. RF MoD claimed strikes on port infrastructure in Odesa and Chornomorsk, targeting vessels and logistics centers. UAF Air Force tracked reactive UAVs approaching Chornomorsk from the Black Sea.
  • Central Rear (Kyiv/Chernihiv): UAV threats were tracked towards Kyiv and Chernihiv oblasts. No significant ground activity reported.

Deep Strikes & Air Defense

  • UAF Deep Strikes:
    • Krasnodar Krai: Confirmed strikes on a Wildberries warehouse and an oil depot in Armavir. Krasnodar authorities reported 2 fatalities and multiple injuries, with debris hitting residential buildings in Krasnodar and Dinskaya.
    • Stavropol Krai: Emergency regime declared in Nevinnomyssk following a strike on a Wildberries warehouse.
    • Maritime: EU Naval Forces (Operation IRINI) intercepted the RF shadow fleet tanker MV South Star in the Mediterranean on July 20.
  • RF Aerospace Campaign:
    • Port Interdiction: RF MoD claimed strikes on Odesa and Chornomorsk port infrastructure, alleging hits on vessels unloading military cargo and three UAV warehouses. Maersk suspended operations in response to security risks.
    • Urban Strikes: KAB and drone strikes on Zaporizhzhia (Olis enterprise) and Kharkiv (residential districts). UAF Air Force reported intercepting 207 of 220 incoming targets overnight, including ballistic missiles and UAVs.

SAR Intelligence (Satellite Data)

  • High Priority:
    • 16th Separate EW Regiment (Belarus): Anomaly score of 5.05 indicates significant activity deviating from historical baselines, warranting monitoring for potential regional spillover or force generation.
    • 96th Operational Purpose Regiment (RF): Score of 7.11 suggests notable movement or logistical activity at this facility.
  • Analysis: The elevated activity at the Belarusian EW regiment contrasts with public statements of stability, suggesting enhanced defensive posturing or electronic warfare support activities. No significant changes were detected at frontline RF logistics hubs, indicating stable baseline activity there despite rear-area disruptions.

Equipment & Losses

  • RF Losses:
    • Infrastructure: Fires at Wildberries warehouses in Krasnodar and Nevinnomyssk; oil depot fire in Armavir.
    • Maritime: MV South Star tanker intercepted by EU forces; GOLDEN LEO bulk carrier struck near Odesa (10 sailors killed).
  • UAF Losses/Damage:
    • Civilian Casualties: 1 dead, 3 injured at Olis enterprise in Zaporizhzhia; casualties reported in Kharkiv KAB strikes.
    • Infrastructure: Damage to residential buildings in Kharkiv and Zaporizhzhia.

Confidence Check

  • Maersk Suspension: HIGH (Confirmed by multiple sources and AIS tracking).
  • UAF Leadership Appointments: HIGH (Confirmed by Presidential Office and official media).
  • RF Claims in Artelne/Blahodatne: LOW (RF claims only; lacks independent geospatial verification).
  • Krasnodar/Armavir Strikes: HIGH (Confirmed by local authorities and visual evidence).
  • Belarus EW Activity: MEDIUM (SAR anomaly detected; requires further SIGINT corroboration).

The Bottom Line

The conflict trajectory is defined by the successful RF escalation of maritime interdiction, forcing major commercial actors like Maersk to withdraw from Ukrainian ports, while UAF deep strikes continue to degrade RF rear-area logistics and energy infrastructure. In the next 24 hours, monitor:

  1. Maritime Logistics Shift: Assessment of the volume redirection to Constanta and Danube ports following Maersk's withdrawal.
  2. RF Penal Unit Deployment: Tracking the operational deployment of newly authorized organized crime convict units on the frontline.
  3. Zaporizhzhia Industrial Impact: Evaluation of the supply chain disruption caused by the strike on the Olis food processing facility.

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 22 Jul 2026, 15:06 UTCLagged by 24.5 h
Map revision comparison

Against the previous report from 21 Jul 2026, 15:06 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 24.5 hours before this report. The daily change covers 20.5 h. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+5.8 km²
20 h ending 21 Jul 2026, 14:35 UTC
Daily net
+5.8 km²
20.5 h comparison
Seven-day net
+25 km²
169.6 h comparison
Largest changes in the latest measured interval
Near Hulyaipole
5.8 km² changed · RF-held gained 5.8 / 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 #748: Pokrovsk area

Geospatial Analysis

11 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 11 places with coordinates
Geocoded places in report 748
PlaceCountryLatitude, longitudeCopy
ChornomorskUA46.2952236, 30.6480855
OdesaUA46.4845702, 30.7326047
PokrovskUA48.282193, 37.1847804
SlovianskUA48.8532, 37.6053
KharkivUA50.00201269999999, 36.3073994
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
KrasnodarRU45.036035, 38.97457060000001
ArmavirRU45.0014406, 41.1326893
NevinnomysskRU44.6393075, 41.9419233
BelarusBY0, 0
ArtelneUA0, 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.