Ably: Elevated 502 error rate 15:40 and 17:40 UTC
Timeline of updates
- resolved
Between 15:40 and 17:40 UTC, customers using the REST API directly may have observed 502 error responses. Our SDKs automatically retry 5xx responses to fallback endpoints, so customers using SDKs should not have noticed anything except increased latency due to the retries. The proximate cause was a faulty router deploy, we are actively investigating the root cause, and will be improving our alerting system, which should have caught this sooner. We apologise for any disruption.
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
a19227e367cd7390…
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: minor) posted by Ably, started 2024-07-09 10:36 UTC, resolved after -685117 min, 1 update(s).
- Title
- Elevated 502 error rate 15:40 and 17:40 UTC
- Vendor
- Ably
- Date
- URL
- https://rewindex.com/company/ably/incidents/0f22c8zsg2by
Ably profileRecent Ably incidentsAll outages on July 9, 2024Ably in July 2024MarkdownJSON