# 80023: Connection re-established in a different region

Identifier: `connection_re_established_in_a_different_region`



The client reconnected to a different Ably region from the one it was using, so it could not keep its connection ID and was given a new one.

## What you should do

Nothing. The connection is established normally and keeps working. The difference is that it has a new connection ID rather than continuing the previous one.

The only thing to be aware of is presence: a presence member is identified by both its client ID and connection ID, so when the client re-enters presence after reconnecting in a different region it appears as a new member rather than the one it was registered as before.

## Why it happens

When a client briefly drops its connection, it can reconnect and carry on with the same connection ID rather than being assigned a new one.

A connection ID cannot be carried across Ably regions, and the main reason is presence. When a client enters presence, its membership is registered against its connection ID and tracked by the region it is connected to, and Ably checks whether those members are still present only within that region, not across regions — which keeps regions independent of one another. So if the client reconnects to a different region, it is issued a new connection ID instead of keeping the previous one.

## What you'll see

The connection reaches the connected state, so this surfaces as the connection's error reason rather than a failure. It is reported with code 80023 and HTTP status 400, with the message `Unable to resume connection from another site` — "site" here is the internal term for a region.