Ably: Problems with US-only routing policies
Timeline of updates
- resolved
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
559404ba4fafbe8c…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Ably, started 2023-07-19 10:35 UTC, resolved after 0 min, 1 update(s).
- Title
- Problems with US-only routing policies
- Vendor
- Ably
- Date
- URL
- https://rewindex.com/company/ably/incidents/76fwsyp274fn
Ably profileRecent Ably incidentsAll outages on July 19, 2023Ably in July 2023MarkdownJSON