DroneLedger

Editorial pack · DroneLedger

Drone report in Rostov region, Russia

Dossier auto-ru-2026-11-11-77b0a3d5eb · revision 2 · exported · fixed version of this revision · JSON

Current state

According to Kommersant, drones were reported in Rostov region, Russia on 11 November 2026.

Evidence states

Drone presencereported · sources [1]
Impactreported · sources [1]
Attributionnone · sources none

According to an official source of an involved party, via Kommersant, as of 11 Nov 2026 05:27 UTC+00:00: flight disruption.

Single-source report, automatically published: one source reports drone presence at this place and date. It has not been corroborated by a second independent source and may be incomplete or wrong. It is shown so that early and local reports are visible; treat it as unverified. Claims are shown as made by the named source; claims by a party to a conflict remain claims. For conflict incidents only the city or region named in the reports is shown, never a precise location, and no operational details; the cited articles may contain more precise details than this dossier. This is not a warning service: for incoming threats, follow official alerts. DroneLedger has not independently verified the claims and an editor has not yet reviewed this dossier.

Not established

Not yet assessed by an editor: impact, exact location, operator and intent.

Not assessed in this automatic report; see the cited sources for any claims of responsibility.

Chronology

Sources

  1. Kommersant () (, source family: kommersant)
    https://www.kommersant.ru/doc/9094202

How to cite

DroneLedger. “Drone report in Rostov region, Russia.” Dossier auto-ru-2026-11-11-77b0a3d5eb, revision 2, updated 11 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-11-77b0a3d5eb/v2/

Editorial changes

Evidence states: confirmed = established by the cited evidence; reported = stated by a source, not independently established; inconclusive; debunked; unknown. A claim by a party to a conflict remains a claim. Methodology: https://droneincidents.com/methodology/