> ## Documentation Index
> Fetch the complete documentation index at: https://ngrok.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# IP Addresses

> Learn about ngrok's dynamic IP addresses, dedicated IPs, IPv6 support, and global load balancing for endpoints and agent connections.

ngrok's cloud service uses a dynamic, rotating set of multitenant IPs to serve
your public Endpoints. Endpoint IPs may change frequently ***and without
notice***. If you hardcode any of ngrok's IPs or rely on DNS answers past their
TTL, your applications ***will break***.

The information on this page about IPs also applies not only to Endpoint IPs but also to the IPs used for [Agent Connections](/agent/connect-url/), the Dashboard, and the [API](/api/).
They each support Dedicated IPs, IPv6, and Global Load Balancing.

## Dedicated IPs

For scenarios requiring static IP addresses, ngrok offers dedicated IPs that are exclusively assigned to your account.
These can be configured for [Domains](/gateway/dedicated-ips/) and [Agent Connect URLs](/agent/connect-url/#dedicated-ips).

<Info title="Coming Soon">
  Dedicated, static IPs for public endpoints are in Early Access.
  [Request access to the developer preview](https://dashboard.ngrok.com/developer-preview).
</Info>

## IPv6

ngrok's cloud service universally supports IPv6. DNS queries for the hostnames
of its public endpoints return `AAAA` DNS records.

Don't forget that ngrok supports IPv6 when using the [`restrict-ips` Traffic
Policy action](/traffic-policy/actions/restrict-ips/). If you forget to allow IPv6
traffic, you may unintentionally cause connectivity failures if connections to
your Endpoints use IPv6.

## Global Load Balancer

When you resolve Endpoint IPs via DNS, you will receive a partial list of IPs
because ngrok's [global load
balancer](/gateway/global-load-balancer/) will return a different set
of IPs depending on where you are located in the world.

## API

There is no supported API to query ngrok's IPs at this time.
