brief partial network partition between us-east-1 and eu-central-1

What to do

• Check whether you use Ably Europe (Frankfurt), US East (Northern Virginia) in eu, eu-central-1, us, us-east-1. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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-08-22 22:57 UTC and 2024-08-22 22:57 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. resolvedAug 22, 2024, 10:57 PM UTC

   Between 22:43 and 22:50 UTC, us-east-1 and eu-central-1 datacenters experienced network issues communicating between each other. Seemingly no other pairs of regions were affected, only those two. Messages published in one of those two regions during that time may have experienced increased latency before being received by the other. (You can find out your local ably datacenter by querying rest.ably.io/metadata)

   provider

Corrections

None so far.

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