IRGC Retaliatory Waves
The IRGC retaliatory waves thread is the kinetic backbone of this conflict's information architecture — and the single narrative thread that most clearly reveals how different media ecosystems process the same military reality through incompatible frames. From the first Khatam Al-Anbiyaa headquarters statement at ~10:54 UTC on February 28, the IRGC's numbered wave system created a metronomic rhythm that structured coverage across every ecosystem we monitor. Russian milblogs and OSINT channels dominated early amplification, treating each wave announcement as battlefield reporting. Iranian state channels — initially sparse on Telegram — steadily increased output until they became the single largest ecosystem contributor by day three, turning Khatam Al-Anbiyaa communiqués into the primary pulse of the conflict.
The information dynamics evolved through distinct phases. The first 48 hours were dominated by OSINT accounts and Russian milblogs racing to verify strike claims, with Iranian state media playing catch-up. By the end of the first week, the thread had settled into a cadence: IRGC statements issued via Khatam Al-Anbiyaa, instantly amplified by Al Mayadeen and Al Jazeera Arabic, then picked up by Russian state and milblog channels, with Western outlets arriving last — often via ecosystem reflection rather than direct reporting. The wave numbering system itself became an information weapon: by Wave 37 (March 11), the IRGC was synchronizing strike announcements with Shia religious calendar events, embedding military operations within sacred narrative frameworks.
What makes this thread analytically distinctive is the escalation ladder visible in the communiqués themselves. Early waves targeted US military bases across the Gulf. By mid-March, Khatam Al-Anbiyaa explicitly threatened energy infrastructure retaliation, then executed it. By late March, the headquarters was announcing new rules for Hormuz transit, claiming the right to rewrite maritime law through force. The information environment processed each escalation step with diminishing surprise — a normalization effect that itself became the story. Trump's repeated claims of '100% destruction' of Iranian military capacity ran in parallel with IRGC wave numbers climbing past 80, creating a credibility gap that adversary ecosystems weaponized relentlessly.
As of Wave 84 (March 27-28), the thread has produced over 11,000 items across 57 chapters. Iranian state media now accounts for roughly 40% of volume — a remarkable shift from near-silence in the first hours. The IRGC's information operation has achieved what military communiqués rarely do: it has become the primary timeline around which all other coverage organizes itself.
First Signal
Saturday morning, February 28 (10:00–12:00 UTC) — roughly four hours after the first strikes at ~06:10 UTC. The IRGC retaliation thread enters our corpus as Russian milblogs and OSINT channels race to process Iran's response. Rybar's MENA channel (@rybar_mena) is among the first at 10:04 UTC, framing Iran's retaliatory strikes as an opportunity for the Houthis to remind everyone about Bab el-Mandeb shipping — immediately connecting the IRGC response to the broader regional architecture.
At 10:54 UTC, @middle_east_spectator carries the first Khatam Al-Anbiyaa Central Command Headquarters statement — the institutional voice that will dominate this thread for a month. PressTV follows at 11:08 with imagery from Abu Dhabi after reported strikes on US bases. The ecosystem breakdown is telling: OSINT (31 items) and Russian channels (24) outpace Iranian state media (11) by nearly 5:1, revealing that Iran's own information apparatus was slower to mobilize than the networks that would amplify it.
Coverage Widens
Saturday February 28 (12:00–22:00 UTC) — the first full day of conflict. Volume triples to 300 items as the amplification surge begins. OSINT accounts dominate with 156 items, functioning as the connective tissue between ecosystems. At 12:34 UTC, @middle_east_spectator posts footage of an Iranian missile booster falling in Doha after interception — the first viral visual of Gulf states becoming the battlefield. By 12:45, Soloviev's channel is framing the destruction of a US FP-132 radar in Qatar, positioning American defensive infrastructure as vulnerable.
The critical ecosystem dynamic: BBC Persian emerges as a dual-function outlet, carrying both Iranian diaspora celebrations in European cities (17:47 UTC) and fact-checking coverage of the Minab school strike claim (19:51 UTC). This split — between the Iranian street's response and the verification of strike damage — will define BBC Persian's unique position throughout the thread. Iranian state channels (49 items) are now producing at scale, but remain outnumbered by the OSINT-Russian amplification machine.
Coverage Widens
Saturday night through Sunday midday (Feb 28 22:00–Mar 1 12:00 UTC) — the thread's first overnight cycle. Coverage widens dramatically as Arab-language outlets (63 items) surge to second position behind OSINT, and Chinese sources (16 items) enter the corpus for the first time. The geographic scope of strikes expands: at 22:01 UTC, @readovkanews reports a drone striking the sail-shaped tower in Dubai; at 23:20, Sheikh Zayed Airport in Abu Dhabi is hit; by 00:25 March 1, Bahrain International Airport is struck.
At 01:05 UTC, a critical ecosystem crossing occurs: @middle_east_spectator carries Chinese satellite imagery showing at least four impacts at Ali Al-Salem Airbase in Kuwait. Chinese commercial satellite data entering the conflict via OSINT channels represents a new information pathway — Beijing providing visual verification without making political statements. By morning, PressTV carries the General Staff and Khatam Al-Anbiyaa's joint statement that aggressors 'will regret' the war, while BBC Persian reports the British Defense Minister's warning that Iranian attacks endanger British forces and civilians.
Peak Activity
Sunday March 1 (12:00–18:00 UTC) — roughly 30 hours into the conflict. This amplification surge is defined by three simultaneous information events. At 12:03, @dva_majors carries Bloomberg's report that US, Israeli, and Gulf interceptor missile stocks may soon be depleted — a Western media admission that becomes the dominant frame across Russian and Iranian ecosystems. At 12:17, Saudi Arabia announces it will retaliate militarily against Iran if US bases continue to be attacked (via CNN), marking the first Gulf state escalation signal.
At 12:23, Khatam Al-Anbiyaa issues the defiant declaration: 'Iran will never kneel to the United States.' This statement propagates through Al Jazeera Arabic, TASS, and back through OSINT accounts within minutes. BBC Persian at 14:25 carries the IRGC's claim of attacking the USS Abraham Lincoln with four anti-ship missiles — a claim that will be contested but amplified across every ecosystem. The TASS dispatch from Tel Aviv at 12:42 is quietly devastating: life continues normally in Tel Aviv amid the strikes, a frame that undercuts both Iranian maximalist claims and Israeli alarm narratives simultaneously.
Coverage Widens
Sunday evening through Monday morning (Mar 1 18:00–Mar 2 10:00 UTC) — the thread reaches peak activity with 348 items. Israeli OSINT channels enter significantly: @abualiexpress at 19:24 posts Palestinian footage of Iranian missiles over Nablus (71,700 views — the highest-engagement single item in this chapter), then at 20:57 reports seven casualties including one critical from a missile strike in Jerusalem. This is the first chapter where Israeli-sourced damage reporting competes with Iranian strike claims in real time.
The geographic escalation is visible in the data: strikes now span from Erbil (Iraq) to Haifa to Tel Aviv. At 18:51, @boris_rozhin reports an Iranian missile evading air defense and hitting a target in Haifa — a detail that becomes significant for the interceptor effectiveness debate. @readovkanews reports Israeli strikes on Iran's intelligence ministry, state TV headquarters, and a hospital simultaneously at 18:40, framing the exchange as mutual escalation rather than one-sided retaliation. The peak is not just volume — it is the moment when every ecosystem is simultaneously processing kinetic events, with lag times between strike and reporting collapsing to minutes.
Amplification Surge
Monday March 2 (10:00–22:00 UTC) — day three. The amplification surge is driven by a major geopolitical development: @readovkanews at 10:33 reports that France, Germany, and Britain are preparing military operations against Iran. This E3 military entry fundamentally reshapes the thread's ecosystem dynamics — European involvement transforms the framing from 'US-Israel vs. Iran' to something approaching a coalition war.
Iranian state channels respond with two parallel messaging tracks. At 15:15, IRGC Intelligence warns the Iranian public that 'the ruthless enemy's next steps will undoubtedly include...' — a domestic mobilization frame. Meanwhile, Khatam Al-Anbiyaa at 16:53 explicitly states through @middle_east_spectator that Iran 'does not harbor enmity toward neighboring countries' and is 'committed to preserving the security and interests of Muslims' — a diplomatic damage-control message aimed at Gulf states. Tasnim at 20:08 publishes footage of an Israeli Hermes 450 drone being destroyed, while at 21:47 they show massive crowds in Qom — military capability and domestic resilience messaging running in parallel.