# Ably: Elevated 502 error rate 15:40 and 17:40 UTC

> Ably status incident “Elevated 502 error rate 15:40 and 17:40 UTC” on 2024-07-09: impact minor (vendor’s label), -685117 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/ably/incidents/0f22c8zsg2by
Last updated: 2024-07-09T10:36:38Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2024-07-09 10:36 UTC · Resolved: 2023-03-21 16:00 UTC · Duration: -685117 min
- Updates: 1
- [Vendor status page: https://stspg.io/fqqlf2bqqnk4](https://stspg.io/fqqlf2bqqnk4)
- [Company: Ably](https://rewindex.com/company/ably.md)

## Timeline of updates

- **resolved** 2023-03-21 16:00 UTC: 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.

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

- Canonical URL: https://rewindex.com/company/ably/incidents/0f22c8zsg2by
- Citation: Ably, “Elevated 502 error rate 15:40 and 17:40 UTC” (2024-07-09 10:36 UTC). Archived by Rewindex: https://rewindex.com/company/ably/incidents/0f22c8zsg2by (CC BY 4.0).
- Markdown link: `[Ably: Elevated 502 error rate 15:40 and 17:40 UTC (2024-07-09)](https://rewindex.com/company/ably/incidents/0f22c8zsg2by)`


---
Canonical: https://rewindex.com/company/ably/incidents/0f22c8zsg2by · Markdown: https://rewindex.com/company/ably/incidents/0f22c8zsg2by.md · JSON: https://rewindex.com/api/v1/companies/ably/incidents/0f22c8zsg2by · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T14:19:02.964Z
