Open Conflict / Military → Drone incidents. The layer screens public reporting for drone-related attacks, interceptions, airport disruptions, crashes, sightings, recovery/investigation and denial/correction wording. This is a source-bounded reporting layer, not a complete incident census, a verified order of battle or live drone flight tracking.
Counts are canonical reports/source records, not unique attacks or drones. Different publishers can describe the same event. Neither repeated coverage nor a map pin establishes independent confirmation.
| Source family | Coverage and limits |
|---|---|
| Reviewed publisher / official feeds | The current catalogue has 556 configured publisher feeds. All usable retained public feed buckets are scanned and exact canonical URL/language copies are deduplicated. This is bounded existing feed coverage, not every article published by every outlet. |
| Reviewed public social/account feeds | 479 configured feeds at the 17 October 2026 review; two directory-only entries are excluded. Collected public posts and publisher-linked references are unverified reporting, not complete platform timelines. Private channels, accounts and owned-key output are excluded. |
| UCDP Candidate GED | The latest available monthly provisional release is screened for explicit drone language in source headlines. At qualification it was the August 2026 release. Source event-date ranges, geographic precision and original citations are retained. Missing drone wording can cause omissions. Some records involve multiple weapons or multiple source headlines. |
Configured feed totals describe the source registry, not the number of responding feeds or independent confirmations. Live source-health counts and captured dates are provided in the panel. Repeated articles can concern the same event.
Incident types are multilingual keyword classifications of headline action plus explicit drone wording in the title or supplied summary. Opinion, procurement, training and future-plan cues are screened out where recognized. Language, phrasing and truncated summaries can still produce misses or classification errors. A drone may be the reported weapon, an affected object/facility or part of a combined-weapon report; the original source governs that meaning.
Reported means a publisher/account made the claim. Official claim attributes an institutional source; it is not independent verification. Unconfirmed claim and dispute/denial reflect explicit source wording. Provisional identifies UCDP candidate records. Multiple copies or publisher counts are not automatically labelled corroborated or verified. Reports do not receive a new conflict-risk score.
City-name disambiguation: an explicit adjacent country/region is preferred. Near-coincident references to the same city can share an anchor. Without adjacent country context, a city with at least 500,000 people and at least 50 times the population of the next candidate may provide the inferred reference; a blocked list of common ambiguous names is exempt. This heuristic can be wrong. Unresolved alternatives stay unmapped; no city anchor is independently verified incident geography.
News windows use the supplied publication or explicitly labelled update/reference timestamp. Event occurrence time is not inferred from publication time. UCDP uses the beginning of its source event-date range for the window and retains both range endpoints and source date precision. Window boundaries are anchored to the retained collector snapshot so paginated reads remain consistent.
The projection runs approximately every five minutes. It reuses the existing public feed cache rather than refetching all publishers. Feed buckets older than six hours are withheld from new ingestion; retained/failed source reads keep their original clocks. The UCDP publication index and file are checked on a daily cadence. Source denials persist a pause; rate failures retain backoff. The store retains at most 20,000 canonical reports/source records within 365 days. A new collection time does not turn an old observation into a current event.
Records absent from a later feed window can remain in history; absence from a feed is not a retraction. This layer does not infer that an incident is still active or resolved. UCDP fatality estimates belong to the entire source-coded event, including any combined weapons; they are not assigned specifically to drones or summed into a new casualty total.
The read-only endpoint is /agent/api/drone-incidents. Views: overview, records, map, detail, sources. Filters include days, kind, source, location, country and literal q. Native record pages are limited to 200; map pages to 5,000 reports and an output byte bound. Follow native nextOffset and reuse the returned native snapshot; a changed snapshot returns409. The browser limits a map response to 15,000 location markers and labels a bounded display.
MCP discovery provides the reviewed route and filter hints. Native source paging and MCP snapshot-bound JSON Pointer/scalar paging are separate. The default overview includes a bounded recent-record selection; it is not an export of the full retained history. Private account, GIS, portfolio, provider-credential and individual asset-telemetry data are not inputs to this dataset.
UCDP Candidate Events: Hegre, Håvard, Mihai Croicu, Kristine Eck and Stina Högbladh (2020), “Introducing the UCDP Candidate Events Dataset.” UCDP data and GeoNames references are credited under CC BY4.0; Natural Earth reference material is public domain. Publisher/platform rights remain with the original sources. Bounded excerpts, source links, provenance and corrections should travel with any reused reporting.