Ably incident

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

Resolved after 3 hours, on October 20, 2026.

resolved Oct 22, 2026, 04:19 PM UTC

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) 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.

Started
Oct 20, 2026, 02:00 PM UTC
Resolved
Oct 20, 2026, 05:00 PM UTC
Duration
3h
Detected by Pingoru
Oct 20, 2026, 02:00 PM UTC

Update timeline

  1. resolved Oct 22, 2026, 04:19 PM UTC

    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) 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.

Your product runs on more than Ably

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →