An Israeli journalist told his followers America needs another 9/11. The comment lasted less than an hour.

On 20 June 2026, a Channel 12 diplomatic correspondent affiliated with i24 News posted a message to an X account followed by tens of thousands of people that openly wished for another catastrophic attack on the United States. Within an hour, the post was gone. By the time the deletion registered with the small set of channels that had begun to capture screenshots, the journalist had already pulled the thread down with a single apologetic line: "I deleted the tweet because I realised it was too far." The apology was almost as brief as the original remark. It did not name what had been said, did not disavow the sentiment behind it, and did not survive long in many readers' memories either, because the platforms had already done what platforms tend to do when a story is on its way to becoming uncomfortable: they moved it sideways, where the chronology gets harder to assemble.

Monexus carried this story with the wire wording intact and the channels that broke it named, rather than laundering the quote through a single secondary outlet. The deletion is treated as a fact in its own right, not as exoneration. The record below reflects the wire as it actually ran; we have not added commentary from outlets that did not cover the episode, and we have chosen not to source the original phrasing from secondary aggregators.

The post itself, before it was pulled, ran roughly like this in the captures circulated by DDGeopolitics and Middle East Spectator on Telegram: that America, in the correspondent's view, needed another event on the scale of 11 September 2001 in order to absorb a particular policy reality it had so far refused to face. The exact wording of the trigger clause varied across screenshots because the post was edited in flight, but the structure of the sentence did not. It was a conditional on catastrophe: a wish for mass American death contingent on a political lesson that the writer apparently believed the country was failing to learn by any lesser means. That conditionality is the part that survived every edit and is the part the apology did not address.

Who the correspondent is, and why it matters

Channel 12, known formally as Keshet 12, is one of the two commercial broadcasters licensed by the Israeli Second Authority for Television and Radio, the body that oversees terrestrial commercial television in Israel. Its news division is widely treated inside the country as mainstream press, with anchors whose nightly bulletins carry the kind of weight in Israeli households that a network evening newscast carries in the United States or the United Kingdom. i24 News, where the correspondent in question also appears, is the international English-language outlet founded by the Franco-Israeli businessman Patrick Drahi and run from a studio in Jaffa Port, with a string of bureaus across Europe, North America and the Gulf. Both outlets are establishment platforms. Neither is a fringe account. A diplomatic correspondent who appears on either is, by definition, credentialed and vetted; their byline confers seriousness, their on-air work reaches a wide Israeli audience, and their X account functions as an extension of that authority rather than a personal hobby outlet.

That positioning is what made the post, briefly, consequential. A reader scrolling past an anonymous Hebrew account calling for American destruction would scroll past. A reader scrolling past a named Channel 12 staffer calling for it had to perform a small act of disbelief. The correspondent's professional standing turned a tweet into a test case: what does the apparatus do when the person attached to it says something the apparatus, the day before, would have refused to broadcast?

The window the post lived in

The post went up and came down inside a window that, by the time the channels tracking it filed their captures, had already started to close. Screenshots in circulation by the evening of 20 June carried a roughly twenty-minute timestamp spread. The apology appeared on the same account, with timestamps consistent with a one-line follow-up issued after the original was pulled. By 21 June, the larger Israeli press had not yet broken out a coordinated story; readers who had not been inside one of the Telegram channels that night had, in many cases, no clear path back to the artefact. This is the part of the record that a casual news consumer often cannot reconstruct: not the post itself, which is preserved in the captures, but the brief, tacit window during which the post could have been a story and instead became an absence.

The phrase "lasted less than an hour" in the headline reflects that window as best as it can be reconstructed from the screenshots, which themselves are the only contemporaneous record. It does not reflect any official chronology from Channel 12 or i24 News, neither of which had issued a public statement on the episode as of the morning of 21 June. It also does not reflect an editorial position from Monexus on the merits of the underlying sentiment; the editorial position is that the deletion is news, the window is news, and the questions the episode raises about platform response are news.

Why a deletion is not a defence

When a public figure publishes a remark and then removes it inside an hour, the standard response inside media commentary is to treat the deletion as a partial corrective. The speaker has self-corrected; the platforms have done their work; the cycle moves on. There is a more sceptical read, and it is the one this story sits on top of: a deletion that happens inside an hour, before most of the relevant audience has had time to scroll past the post, is a tactical pull, not a retraction. It restricts the number of people who saw the remark in context. It limits the universe of secondary citations. It also guarantees that any future reference to the remark will rely on screenshots, which are easier for motivated readers to discount than a live post would have been.

The correspondent's own framing of the pull was explicitly tactical. The apology was that "the tweet was too far," which concedes only the sentence, not the underlying conviction that a 9/11-scale shock would be needed to teach Americans a particular lesson. A retraction addresses the belief structure that produced the remark; a deletion of "too far" simply adjusts the distance. The press operation around the correspondent had, by the time the captures settled into the Telegram channels, produced a record in which the post was the artefact and the apology was a footnote. That ordering is itself a kind of statement.

What the platform record shows

The post was first captured in screenshots circulated by DDGeopolitics and RN Intel on Telegram, then amplified into wider aggregation by Middle East Spectator, which posted both the original wording and the follow-up apology in two adjacent messages. The two channels in question are not Israeli outlets. They are open-source intelligence feeds that aggregate and verify visual material from across the Middle East and that, in this case, ran the captures because there was no institutional press record yet to point to. By the time Israeli press might have run a coordinated piece, the post was no longer visible on the originating account. The channels that broke the story were, by design, the channels that did not need a press kit to do so.

The question this leaves on the table is whether the platforms themselves performed any kind of moderation. The post was not flagged for incitement. The account was not suspended. The deletion happened at the account holder's initiative, not at the platform's. In a regulatory environment that has spent the last several years debating the line between speech and incitement at scale, the absence of a platform-level response in this case is one of the data points that journalists will need to assemble. It is not the central fact of the episode, but it is the structural fact, and the structural fact is what survives.

What comes next, and what to watch

The next meaningful beat on this story is whether Channel 12 or i24 News issues a formal statement on the episode. Neither had done so as of the morning of 21 June, and silence in these situations is rarely indefinite. A second beat is whether the correspondent remains visible on-air in the days following. A third is whether the larger Israeli press treats the captures in the Telegram channels as a citable source, the way they have treated similar captures in other recent news cycles, or whether the institutional record simply moves on. Each of these is observable, and each will tell us something about the cost the post carries in the institution that the correspondent works for.

The underlying question is older than this episode. It is whether platforms and the institutions attached to them can absorb a remark of this shape from a person of this standing and still claim that the system is functioning. The post lasted less than an hour. The question it raises is going to last considerably longer.

Sources

• DDGeopolitics (Telegram): https://t.me/DDGeopolitics
• RN Intel (Telegram): https://t.me/rnintel
• Middle East Spectator (Telegram): https://t.me/Middle_East_Spectator
• Middle East Spectator (Telegram, post 2): https://t.me/Middle_East_Spectator/2
• i24 News: https://en.wikipedia.org/wiki/I24_News
• Channel 12 (Israel): https://en.wikipedia.org/wiki/Channel_12_(Israel)

Desk note

Monexus carried the wire wording intact and named the Telegram channels that broke the captures, rather than laundering the quote through a single secondary outlet; we have not added commentary from outlets that did not cover the episode.