The IDF spokesperson said sirens that sounded in Eilat shortly before 03:36 warning of a hostile aircraft intrusion were determined to be a false identification. The alert has been declared over.
The IDF confirmed at 03:36 Jerusalem time that the sirens that sounded in Eilat since 03:18 were a false identification. The military stated no hostile aircraft was detected and the alert has been declared over. The development closes a sequence of alerts that began at 03:18, when sirens first sounded across Eilat, Eilot, and the Shahoret industrial zone, with initial reports describing a suspected drone infiltration from Yemen. A second siren wave followed at 03:19, and by 03:20 the IDF said details were under review. The Home Front Command declared the incident over at 03:29, and the IDF's confirmation of a false identification came seven minutes later.
Over the preceding hour, The Zioneer reported seven consecutive updates on the evolving situation. At 03:18 the first alert was activated citywide. By 03:19 initial reports identified the suspected source as Yemen. A second siren sounded at the same minute, and by 03:20 the IDF confirmed it was investigating two drone alerts. At 03:29 the Home Front Command lifted the red alert state. Source quality progressed from unverified Cumta Alerts reports through multiple newsroom confirmations to a formal IDF spokesperson statement classifying the event as a false identification.
As The Zioneer has reported this month, false-identification sirens have become a recurring pattern across multiple fronts — including Metula, Misgav Am, the Western Galilee, and Gaza — often linked to Israeli forces' activity in the area or tracking errors. A suspected hostile aircraft alert over Eilat was also reported on June 13, though that incident remained unclassified overnight.
No interception or impact was reported at any stage of this alert sequence. The IDF has not specified what triggered the false identification, and it remains unclear whether the earlier suspected Yemen-origin drone report reflected a genuine tracking error or a separate unresolved incident.
7 developments
Source and signal
- Internal intake