How open-source intelligence and military tracking systems monitor Houthi missile and drone strikes against commercial shipping in the Red Sea.
Since late 2023, the Houthi movement—a Yemen-based armed group backed by Iran—has launched hundreds of missile and drone attacks against commercial vessels transiting the Red Sea and Gulf of Aden. These strikes have disrupted one of the world's busiest shipping corridors, forcing vessels to reroute around Africa at enormous cost and time penalty. For analysts, journalists, and maritime professionals, understanding how these attacks are detected, tracked, and reported has become essential to making sense of regional escalation.
The challenge for open-source observers is significant. The Red Sea is a crowded maritime environment with hundreds of ships moving daily across an area spanning hundreds of kilometres. Most Houthi attacks involve coordinated waves of drones and missiles launched from territory in Yemen, often at night or during poor visibility. Tracking these incidents requires piecing together information from multiple sources: military statements, shipping industry reports, satellite imagery, radio intercepts, and eyewitness accounts from crews.
The most authoritative real-time source for Red Sea incidents comes from the U.S. military's Central Command (CENTCOM), which maintains a strong presence in the region. CENTCOM releases public statements detailing attacks it has monitored or responded to, typically including the location, number and type of weapons used, targets hit or missed, and whether its forces intercepted incoming munitions. These statements are factual and sourced from radar, satellite, and direct observation, but they represent only incidents that occurred within U.S. detection range or that the military chose to disclose publicly.
Other governments with naval assets in the region—including the United Kingdom, France, Germany, and others—also release statements about attacks they have monitored or their ships have experienced. These accounts sometimes add detail or contradictory information compared to U.S. reports. The International Maritime Organization (IMO) and regional port authorities collect incident reports from shipping companies and publish summaries, providing a merchant-centric view that may capture attacks the military did not report or that occurred in gaps in military surveillance.
Commercial vessels operating in contested areas file incident reports with flag state authorities, insurance brokers, and maritime security firms. When a ship is attacked or witnesses an attack, the crew typically files a detailed account including time, location, weapon type (if identifiable), damage sustained, and crew injuries. These reports flow through marine insurance networks and are aggregated by commercial databases used by shipping companies and brokers. Some reports are made public; many remain private.
Crew radio communications and distress calls (monitored on public maritime radio frequencies) can provide immediate, unfiltered information about incidents as they unfold. Open-source monitors track these frequencies and share significant events through social media and specialist networks. However, radio reports are inherently limited—they reflect only what the crew observed, may contain errors under stress, and are sometimes vague to avoid revealing sensitive information. A crew might report 'missile attack' without specifying the weapon type or providing precise coordinates.
Commercial and government satellite imagery provides visual confirmation of some incidents. When a large vessel is struck and damaged, or when debris or fire is visible, satellite operators can sometimes capture imagery in the days following an attack. This is particularly valuable for confirming hits and assessing damage severity. However, satellite coverage of the Red Sea is not continuous—revisit times vary by satellite constellation and weather conditions often obscure the sea surface. Imagery is most useful for aftermath assessment rather than real-time detection.
Open-source analysts also monitor vessel tracking systems, particularly Automatic Identification System (AIS) data, which shows ship movements and sudden course changes or speed reductions that may indicate an attack or evasive maneuver. However, many vessels deliberately turn off AIS in contested waters to avoid being targeted, creating gaps in the public tracking picture. Comparing AIS tracks before and after an incident can help confirm that an attack caused a vessel to divert or loiter.
One of the hardest aspects of tracking Red Sea attacks is distinguishing between different weapon types and confirming Houthi responsibility. The group uses various drones and missile systems, some produced locally and others supplied from abroad. Identifying which weapon was used relies on eyewitness descriptions (which vary widely), visible wreckage or impact craters (rarely documented in detail), acoustic signatures, and radar characteristics. A crew might report seeing a missile, but confirming its origin or intended target is often impossible without forensic evidence.
Attribution is complicated by the fact that other actors operate in the region, and not every incident in the Red Sea is a Houthi strike. Accidents, collisions, and ordinary fires occur on merchant ships regularly. The Houthis themselves sometimes claim credit for attacks that military sources believe did not occur, or deny responsibility for strikes they likely conducted. Cross-referencing multiple independent sources—military reports, shipping company statements, and crew accounts—is essential to separate confirmed incidents from claims and rumors.
Analysts compile incident reports into databases and map the locations, dates, and targets of attacks to identify patterns. Over time, this reveals information about Houthi targeting preferences, weapon ranges, operational tempo, and success rates. Clusters of attacks in certain zones may indicate concentrations of high-value targets, chokepoints, or gaps in defensive coverage. Tracking the frequency of attacks week to week can suggest whether Houthi capabilities are degraded by international strikes on their launch facilities, or whether they are increasing their operational intensity.
Open-source intelligence communities maintain crowdsourced databases and visualizations that aggregate incident data and allow researchers to query specific time periods, vessel types, or geographic areas. These maps are updated as new reports arrive and are refined when earlier claims are corrected or retracted. The confidence level of each plotted incident varies—some are confirmed by multiple independent sources, others rest on a single statement, and some remain disputed.
When reading reports of Red Sea attacks, it is important to note the source and consider what that source can realistically observe. Military statements are usually reliable on broad facts (attack occurred, general location, type of weapons used) but may understate damage or omit incidents outside their focus. Shipping industry reports reflect commercial impact but may lack technical precision. Crew accounts are eyewitness testimony—valuable but subjective.
Cross-reference reports across multiple independent sources before accepting claims as confirmed. Be alert to the difference between 'attacked' and 'damaged'—an attack can fail to hit its target, and damage can have many causes. Recognize that some incidents take days or weeks to be fully documented. Most importantly, remember that absence of reported attack does not mean no attack occurred; it means no source publicized it. A complete picture of Red Sea incidents will always contain gaps, and new information sometimes revises earlier understanding.