# 50306: Region temporarily disabled

Identifier: `region_temporarily_disabled`



The request reached a region that has been temporarily taken out of service, so it was rejected. Requests only reach a disabled region while traffic is still being routed there, and stop once the routing change takes effect.

## What you should do

Usually nothing: Ably SDKs retry this automatically, and the region is taken out of DNS routing, so retries reach a region that is working normally. Leave the endpoint your clients use as it is: an account configured for [regional routing](https://ably.com/docs/platform/account/enterprise-customization.md#regional-routing-and-storage) or with a placement constraint is permitted in a limited set of regions, and switching endpoints can send requests outside that set, where they are refused. If requests keep failing for more than a few minutes, [contact Ably support](https://ably.com/support) with the request ID from the message.

## Why it happens

Ably takes a region out of service temporarily when services there are not functioning correctly, often for reasons outside Ably's control, so that traffic is not disrupted by it. A disabled region rejects the requests that reach it rather than redirecting them, and requests keep arriving until the routing change has propagated. Accounts using regional routing are still served throughout, because the geographic area they are routed within spans more than one region.

## What you'll see

The error is reported with code 50306 and HTTP status 503. The message begins `This site has been temporarily disabled` and ends with the request ID (`reqID`). It also suggests moving to the main global endpoint, which is not necessary and is not appropriate for an account restricted to particular regions.