> This page is for Home.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.emnify.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.emnify.com/_mcp/server.

# Automatic breakout region update

> emnify is reassigning mobile operators to lower-latency breakout regions, and some configurations need a change before it takes effect

## Background

emnify's continuous expansion of the global connectivity drives reductions in the data path latency.
emnify continuously monitors the data path latency and, whenever necessary, reassigns specific mobile network operators to breakout regions with the goal of minimizing it.
A reassignment only affects devices whose service policy is set to **Automatic Breakout Region**.
For details, see the main article [Set the breakout region](/portal/how-tos/set-breakout-region).

The next change will be applied on **October 26, 2026**.
Active data sessions will continue uninterrupted.
If the mobile network operator used by the device has been reassigned to a different breakout region, the next data session will be created in the new breakout region.

## Who needs to act

The devices will successfully establish data sessions, but they can stop reaching your application if either of the following applies:

* Your application is behind a firewall that allows only some emnify public IP addresses.
  See [If your devices use internet breakout](/portal/how-tos/set-breakout-region#if-your-devices-use-internet-breakout).
* Your devices reach your application through Cloud Connect or OpenVPN.
  See [If your devices use Cloud Connect or OpenVPN](/portal/how-tos/set-breakout-region#if-your-devices-use-cloud-connect-or-openvpn).

If neither applies, no action is needed.

## When

If your configuration is affected, emnify will timely notify you via a Portal banner and by email.
Take action before **October 26, 2026** to avoid losing connectivity to your application.