rewindex

CompaniesAblyIncidents

Ably: issue with rewind=1 and persist-last in some situations

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.ably.com (opens in new tab)

Timeline of updates

  1. resolved

    Between about 14:00 UTC on the 20th and 17:00 on the 21st, on channels with the persist last message (https://ably.com/docs/channels#rules (opens in new tab)) channel rule enabled, attachments with rewind=1 in situations where the most recent message was published over two minutes ago but still somewhat recently (and where the channel has been continuously active in a given region since the message was published) may not have had that rewound message correctly delivered to the attaching client. We apologise to anyone whose application was affected by this.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.ably.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Ably, started 2026-10-20 13:00 UTC, resolved after 0 min, 1 update(s).

Title
issue with rewind=1 and persist-last in some situations
Vendor
Ably
Date
URL
https://rewindex.com/company/ably/incidents/mwsm9xbk9xt1

Ably profileRecent Ably incidentsAll outages on October 20, 2026Ably in October 2026MarkdownJSON