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

- Provider: [Ably](https://down.guide/providers/ably)
- Confidence: Confirmed
- Impact: Operational
- lasted 0m
- started 2026-10-20 13:00 UTC
- id: DWN-b33c9884af
- Official page: https://stspg.io/k4tn4vcsklwt

## Updates from Ably
### 2026-10-20 13:00 UTC: 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) 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.

From the builder: does your app depend on Ably? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=ably) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Ably.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-b33c9884af), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.