Incident · Other
FBI seizes 500+ drones during FIFA World Cup 2026
FBI seized 500+ drones during World Cup. 1,000+ detected near stadiums. Counter-drone technology at all 78 matches.
Occurred 2026-07-02 · Skydio
Machine-readable surfaces
- Markdown mirror: /incidents/other-2026-07-02-skydio.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/37ada585-1aa1-4b20-b06d-d0e17613b49a
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Status history
- Active · 2026-07-03 · agent:depth
Common questions
- What happened in FBI seizes 500+ drones during FIFA World Cup 2026?
- FBI seized 500+ drones during World Cup. 1,000+ detected near stadiums. Counter-drone technology at all 78 matches.
- When did this incident occur?
- The incident is recorded as occurring on July 2, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
- Who was involved in FBI seizes 500+ drones during FIFA World Cup 2026?
- The incident is recorded as involving Skydio on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
- Has anyone responded to FBI seizes 500+ drones during FIFA World Cup 2026?
- No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
- What is the current status of FBI seizes 500+ drones during FIFA World Cup 2026?
- This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (no primary) · last reviewed 2026-07-03
Verification posture
Unreviewed
Low confidence
Review state
Stable
Last reviewed 2026-07-03
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for FBI seizes 500+ drones during FIFA World Cup 2026.Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID 37ada585-1aa1-4b20-b06d-d0e17613b49a