We're investigating issues in the us-east-2 (Ohio) region.
All other regions are operating normally, so service should be unaffected, other than slightly higher than normal latency if you would normally be routed to the Ohio region.
We have disabled the region at the dns level in all cluster in which it operates, so traffic that would have been going to Ohio will now be going to the next closest region (such as us-east-1 East Virginia).
The service should still be operating normally; please contact Ably support in the usual way if you do experience any problems.
28th Jul 05:56 PM We are continuing to monitor AWS reports on the incident and will re-enable us-east-2 when we are confident that that region is stable. Until then, the Ably service will continue to operate as normal with traffic routed through the five other regions in which our production cluster operates.
29th Jul 09:34 AM The us-east-2 region has now been re-enabled in all clusters which used in that region.