# 40330: Account not permitted in this cluster or region

Identifier: `account_not_permitted_in_cluster_or_region`



The request reached a cluster or region the account is not permitted to use; the accompanying error message gives the specific reason.

## What you should do

Configure every connecting client with the custom `endpoint` Ably issued for the account, following [platform customization](https://ably.com/docs/platform-customization.md), so requests reach the cluster or region the account is permitted to use. The accompanying message states which specific constraint the request violated.

## Why it happens

The account has a placement constraint limiting the cluster or region it may be activated in, and the request reached one that isn't permitted. This usually means a client connected to a default global endpoint instead of the custom endpoint for the account's dedicated deployment, typically because the `endpoint` client option was omitted.

## What you'll see

The error is reported with code 40330 and HTTP status 403. The default message is `Unable to activate account due to placement constraint`; an account may instead carry a more specific custom message.