# 62052: Interconnect: Account is not a subaccount of the Connection owner

Log Level: ERROR

## Description

This error occurs when the account making the request does not belong to the same account hierarchy as the Interconnect Connection identified by the `Connection SID`. To access the connection, authenticate with the parent account that owns the connection or with one of that parent account's subaccounts.

### Possible causes

* The request was authenticated with credentials from a different parent account than the one that owns the Interconnect Connection.
* The request used a subaccount that is not under the connection owner's parent account. A subaccount can access only its own resources, while the parent account can access its subaccounts' resources.
* The request included the wrong `Connection SID`, so Twilio looked up a connection owned by another account hierarchy. Twilio uses `CN`-prefixed SIDs to identify Connection resources.

### Possible solutions

* Verify the `Connection SID` in your request and confirm that it matches the Interconnect Connection you intend to manage. A valid Connection SID starts with `CN`.
* Check the authenticated account's `OwnerAccountSid` and confirm that it matches the parent account that owns the connection. If it does not, retry the request with the correct parent account credentials or with a subaccount that belongs to that parent account.
* If you work across multiple Twilio accounts or projects, switch to the correct account context in Console or update your API credentials before retrying the request. Parent account credentials can access subaccount resources, but subaccount credentials cannot access sibling or parent account resources.

#### Additional resources

* [Interconnect overview](/docs/interconnect)
* [Subaccounts API](/docs/iam/api/subaccounts)
* [Accounts API](/docs/iam/api/account)
