Problems with US-only routing policies

What to do

• Check whether you use Ably in us, us-east-1, us-east-2, us-west-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 2023-07-19 10:35 UTC and 2023-07-19 10:35 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. resolvedJul 19, 2023, 10:35 AM UTC

   Customers using a US-only routing policy (eg environment="us") who would naturally have been routed to us-east-1 may be experiencing issues, we are investigating 19th Jul 11:04 AM This has now been resolved. The cause was incorrect DNS configuration for the US-only routing policy. We had taken the us-east-1 region down for maintenance; the command to do this updates all relevant routing policies, in this case while the global DNS routing policy was updated correctly, the US-only routing policy was not. We apologise for the inconvenience and will be taking steps to make sure this does not happen again. Ably SDKs will automatically retry any failed attempts to a fallback site, and this mechanism was still working as normal. So in most cases, the only customer-visible effect to those affected (those using a US-only routing policy who are nearer us-east-1 than us-east-2 or us-west-1) will have been higher latencies when establishing a connection or making a REST request.

   provider

Corrections

None so far.

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