Ably: Some SSE connections disconnected and reconnected every 30s
Timeline of updates
- resolved
For most of the production cluster, between 13:05 and 14:02 UTC on 2024-10-01, a small proportion of SSE connections were disconnected 30 seconds after establishing a connection. For the duration of that 30s they still worked fine, and connection resumption was working correctly, so this should not have caused any missed messages. The net effect would have been a small increase in subscribe latency about once every 30s.
Only the SSE endpoint was affected; websocket traffic (including anyone using an Ably SDK) was not.
For customers connected to ap-southeast-2 (Sydney), the duration of the effect was much longer, between 10:06 on 2024-09-30 to 14:02 on 2024-10-01.
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.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a03d456a3935bb6c…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Ably, started 2024-10-01 13:05 UTC, resolved after 0 min, 1 update(s).
- Title
- Some SSE connections disconnected and reconnected every 30s
- Vendor
- Ably
- Date
- URL
- https://rewindex.com/company/ably/incidents/t84szl0vhz3r
Ably profileRecent Ably incidentsAll outages on October 1, 2024Ably in October 2024MarkdownJSON