CENTCOM logs 13th consecutive night of strikes on Iran; Tehran reportedly rejects US ceasefire proposal

US Central Command completed its 13th consecutive night of strikes against Iran in the early hours of 24 July 2026, according to war-monitoring channels logging the announcement in real time. @intelslava carried CENTCOM's statement that the latest wave had been wrapped at 01:28 UTC on 24 July, roughly an hour after @bricsnews posted that "major explosions" were being reported inside Iran from US strikes at 00:36 UTC. The night began earlier, on 23 July, with separate relays placing the opening of the new round between 23:16 and 23:33 UTC.

What the cited record shows is a tempo. The chronological sequence runs: a strike notice from @bricsnews at 23:16 UTC, a CENTCOM statement relayed by @farsna at 23:22 UTC, an independent corroboration from @wfwitness at 23:33 UTC, a single-channel report of a rejected ceasefire at 23:50 UTC, fresh explosions inside Iran at 00:36 UTC on 24 July, and the completion announcement via @intelslava at 01:23-01:28 UTC. The dates carry the story; the substance of the strikes themselves does not appear in the cited items.

A diplomatic door, then the bombs

The proximate sequence reported by the channels is a rejected ceasefire followed by continued strikes. @bricsnews, posting at 23:50 UTC on 23 July, reported that Iran had rejected a US ceasefire proposal. The cited item does not name the Iranian official who communicated the refusal, does not specify the venue in which the proposal was tabled, and does not quote the text of either the proposal or the rejection. This publication treats the rejection as a single-source report, attributed to @bricsnews, pending first-party confirmation from Iranian or US channels not present in the cited record.

Within roughly an hour, the same channel was logging fresh strikes, and within two hours, CENTCOM (via @intelslava) was announcing completion of the new wave. The cadence, as documented, leaves no operational pause between the rejection and the next round. That sequencing is the news. Whether it reflects a deliberate US choice to continue striking in the face of an Iranian refusal, or simply the inertia of an air campaign already in motion, is not established by the cited items. The most natural reading, as analysis rather than evidence: a public proposal and a public refusal function in this environment less as negotiation than as positioning for the post-conflict record. Each side gets a clean line for its respective audience. The cited sources support the existence of the two announcements; they do not support a verdict on intent.

What the relays say, and what they do not

The cited items are unusually consistent on chronology and unusually thin on substance. Seven posts from six distinct channels agree that strikes have occurred on 13 consecutive nights, that the most recent wave opened late on 23 July UTC and was declared completed in the early hours of 24 July, and that a ceasefire proposal was rejected shortly before the latest round began. They do not specify the targets struck, the weapon systems used, the casualty figures on either side, the specific Iranian territory affected, or the Iranian ministry or spokesperson who communicated the rejection. The phrase "major explosions in Iran from US strikes" appears in @bricsnews at 00:36 UTC; the geographic specificity ends there.

This is the normal texture of an active strike campaign as seen through monitoring channels. The cadence is public; the payload is not. CENTCOM's own statements, as relayed by the channels, are short and declarative, designed for transcription. @farsna, a Telegram channel whose account name appears in the cited items without further institutional description in the source post itself, carried the CENTCOM quote "We started a new round of attacks against Iran" at 23:22 UTC. @bricsnews, @wfwitness, @intelslava and @disclosetv logged the 13th-night framing and the completion announcement in their own words. Western wire reporting on the strike list, target packages, or Iranian counter-strikes is not present in the cited items, and this publication has not independently established those details from the available record. The honest characterisation of the sourcing is that it confirms a tempo, not a target set.

One further caveat: the cited posts establish that this is the 13th consecutive night of strikes. They do not establish that the prior 12 nights were publicly framed in the same way, that the cadence was uninterrupted from a documented starting date, or that any earlier nights involved comparable target packages. The pattern is consistent across the cited posts; the history of the pattern is not in evidence.

The structural read

Monexus assessment: what is unusual here is not the existence of strikes but their regularity. Thirteen consecutive nights is the kind of cadence that bureaucratises escalation. It moves the campaign out of crisis mode and into operational routine, which has two effects. First, it lowers the political cost of each individual wave: a thirteenth strike is a smaller escalation than a first or a third, even if the kinetic content is comparable. Second, it tightens the coupling between diplomacy and force: a rejected ceasefire in this environment does not, on the documented sequence, produce a pause. It produces the next package.

The structural pattern, expressed in plain terms, is the slow fusion of coercive air power with coercive negotiation. The United States names the offer and the target in the same news cycle; Iran names the rejection and, when it has one, the casualty count in the same news cycle. Each side treats the other as the obstacle, and both can point to a documentary trail that supports the claim. The monitored audience, whether Western, Iranian, or third-party, is asked to read the contest as a sequence of choices rather than a single decision, and that framing favours the side with the deeper bench of nightly announcements. On present form, that side is CENTCOM, which is producing the consistent English-language nightly updates that the cited channels are relaying.

The counter-read deserves equal airtime: a competing interpretation is that the cited record, drawn entirely from Telegram and X monitoring channels rather than from on-the-ground reporting or first-party government statements, reflects the information contest more than the kinetic contest. The same six channels that logged the 13th night also carried the rejection and the explosion reports; they are not independent corroborators of each other in any strict sense. A reader who weights only the cadence and not the source concentration will overstate the certainty with which either the rejection or the explosions can be attributed.

Stakes and the days ahead

The immediate stakes are kinetic. Iranian civilians inside the affected areas, the exact locations of which the cited items do not specify, face a campaign that is no longer being described, in the cited record, as a one-off, and that no announced diplomatic track appears likely to interrupt. The cited record does not establish whether the Iranian government has publicly responded to the latest wave, whether any Iranian counter-strike has been reported, or whether the US has characterised the rejected proposal in any first-party statement.

The forward calendar is short and consequential. If a 14th night begins on 24 July UTC, the ceasefire proposal reported by @bricsnews will be functionally dead in the cited record, and the burden of escalation will sit with Tehran: accept, retaliate, or absorb. If it does not, the diplomatic track, however thin the sourcing on it, regains a sliver of life. The cited record does not yet resolve that question. What it does resolve is that, as of 01:28 UTC on 24 July 2026, CENTCOM is announcing completed strikes via @intelslava and Iran is being reported, via @bricsnews, as having rejected a US ceasefire, with neither side showing signs, in the cited channels, of stepping back from the cadence that produced them.

Desk note: Monexus framed this around the documented cadence (13 consecutive nights) and the sequencing of the ceasefire rejection and the latest wave, rather than around any single target or casualty claim, because the cited sources support the tempo and not the payload. Channel attributions in the cited record are treated at face value as Telegram and X monitoring channels; the institutional affiliations implied by handle names (e.g. "Fars," "BRICS News") are not independently established by the cited items. Where target geography, weapon systems, casualty figures, Iranian counter-strikes, or first-party Iranian or US government statements are concerned, the available record does not specify, and this article has not independently established those details.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/intelslava/91317
• https://x.com/disclosetv/status/2080463742354006524
• https://t.me/bricsnews/17208
• https://t.me/bricsnews/17207
• https://t.me/wfwitness/104691
• https://t.me/farsna/452192
• https://t.me/bricsnews/17206