Elevated 5xx error rate for connection creation in us-east-1

What to do

• Check whether you use Ably in us, us-east-1. 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-06-18 13:24 UTC and 2024-06-18 13:24 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. resolvedJun 18, 2024, 1:24 PM UTC

   There was an elevated 5xx error rate for connection creation from the us-east-1 datacenter from 13:24-14:20 UTC, due to a broken router process, which was then removed from service. The error rate in that region peaked at 4%. No other regions were affected. Any customers using an Ably SDK will not have noticed anything other than potentially increased latencies, since Ably SDKs automatically retry to a fallback region on 5xx. However, customers in east coast or central US who are using SSE, or other protocols using our protocol translation functionality (such as mqtt, pusher, or pubnub), may have noticed some connection attempts fail with 5xx.

   provider

Corrections

None so far.

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