Some SSE connections disconnected and reconnected every 30s

What to do

• Check whether you use Ably in ap-southeast-2, au. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2024-10-01 13:05 UTC and 2024-10-01 13:05 UTC may need a replay.

• Subscribe to Ably's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=ably works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Ably 1

1. resolvedOct 1, 2024, 1:05 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.