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

What to do

• Check whether your product depends on Ably. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-20 13:00 UTC and 2026-10-20 13:00 UTC may need a replay.

• Subscribe to Ably's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=ably works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Ably 1

1. resolvedOct 20, 2026, 1:00 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.