Ably: Network issues for reactor queues in us-east-1
AWS outage, Sep 28, 2023 · 23 vendors, 24 incidents
Ably’s incident names AWS (location or integration). (hop 1, posted +0 min vs the first vendor naming AWS)
“…Network issues for reactor queues in us-east-1 We're currently experiencing network timeouts for hosted reactor queues in the us-east-1 region, we are investigating. 28th Sep 09:01 PM Our team are con…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Ably, Temporal Cloud, Keeper"]:::blames
root --> h1
h4["1 to 4 hours later<br/>4 vendors, 3 blamed AWS<br/>Dremio, Firebolt, CockroachDB, Elastic Cloud"]:::blames
root --> h4
later["Later<br/>3 vendors, 1 blamed AWS<br/>Aptible, Temporal Cloud, Confluent"]:::blames
root --> later
me["Ably (this incident)<br/>posted +0 min"]:::me
h1 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
We're currently experiencing network timeouts for hosted reactor queues in the us-east-1 region, we are investigating. 28th Sep 09:01 PM Our team are continuing to investigate network timeouts for hosted reactor queues in the us-east-1 region. 28th Sep 10:03 PM We have deployed a change to work around ongoing networking issues affecting the queues service in us-east-1. As far as we can tell, this has been successful and service performance has returned to normal. We will continue to monitor the situation. 28th Sep 10:10 PM The service is performing normally.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).