Resolved incident
Elevated 502 error rate 15:40 and 17:40 UTC
Ably · Minor · Started
- Duration
- < 1m
- Severity
- Minor
- Status
- Resolved
Summary
Minor · 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.
Event timeline
How this incident unfolded, from the official status page.
Resolved
Ably
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.