Hardcoded or Static IP Addresses

We do not support or recommend hardcoding IP addresses directly into a client application. DNS is part of our redundancy and disaster recovery strategy, and we expect customers to always use DNS to resolve their site's identifying hostname or the global application hostname as appropriate. We also use Geo-DNS to route traffic to the fastest and closest available server, and to take troubled servers out of the active pool.

Hard-coding IP addresses is a risky practice with little benefit. Using a hardcoded or stale IP may well direct you to a server that is down, currently undergoing maintenance, etc.

If a connection absolutely must use a hardcoded or static IP address, the best workaround is to provision a Custom Domain for your site. Adding a custom domain automatically assigns 2 dedicated IP addresses to your site. Our goal is to keep your dedicated IPs stable, and we work hard to avoid having IP addresses change out from under you. In practice, dedicated IPs for our customers have remained the same for the past several years.

If we ever have to make changes to dedicated IP addresses associated with a custom domain, we will provide advance notice when possible. For real-time notification of changes, poll the IP Addresses API endpoint to monitor when a change occurs. This endpoint returns a response that includes both our published list of IP addresses and your site's 2 dedicated IP addresses.