Public IP Migration FAQs

Updated by Brandy Smith on Nov 23, 2020
Article Code: kb/1307

Important Update
Lumen Public Cloud (formerly Lumen Public Cloud – CLC) has made the decision to not move forward with the IP Migration initiative outlined below.
Instead, Lumen is pivoting to an internal platform change that will allow for better governance and security over our networks and the platform while not impacting our customers.
A formal communication will be sent via email to all Lumen Public Cloud customers with more information.
At this time there is no action required by customers.


This communication is an important announcement regarding the migration from Lumen Public Cloud public IPs. This document is to provide Lumen Public Cloud customers with information how to identify if a public IP is impacted and how to migrate.

What IPs Require Migration?

Any Lumen Public Cloud public IP that is not within the following range is an impacted IP and will require migration: ( -

Why Is Migration Happening?

  • Better governance over our networks.
  • Increased security by adding DDoS mitigation in the new IP range. This is not possible with some of the existing ranges.

Frequently Asked Questions

Q: What products will be impacted?

  • Servers using public IP addresses
  • Existing IPSec (Site-to-Site) VPN tunnels

Q: How do I migrate a public IP assigned to a server?

Simply remove and assign a new public IP via the Control Portal and a new IP within the range will be assigned. Our Public IP Article provides detailed instructions.

One migration method is to assign a second internal IP to your server, then add a corresponding new public IP. Next update DNS records to point to the new public IP. Once satisfied with the migration, release the original public IP via the Control Portal. Note, release of the initial internal IP in the Control Portal will require a support request to

Q: How do I migrate an existing IPSec VPN

Our March 31 Release Notes recently announced that any changes to an existing self-service IPSec VPN will automatically update the CLC peer IP with the new IP range.

Custom IPSec VPNs that are not displayed in the Control Portal will require manual configuration changes to complete migration. Please contact our Customer Care Team via for assistance.

Q: When is migration required?

A final migration date is not yet available, more information will be provided regarding final deadlines. Our intent is to provide as much advanced notice as possible. Migration is encouraged at the earliest possible customer convenience.

Q: My Public IP is in the range -, is there anything I need to do?

Nothing is required, your Public IP is already in the correct range.

Q: How Can I Migrate Existing Public IP Configuration To a New IP?

Use our API to effeciently gather existing public IP configuration and assign a new public IP with the same configuration:

  1. Authenticate to the API
  2. Get current public IP configuration
  3. Delete the current IP
  4. Assign a new IP using the configuration parameters gathered in step 2.
    NOTE, include the current internal IP in the API call to ensure the new public IP is configured with the existing internal IP rather than a new internal IP being assigned with the request. Here is a PUT call Body example:
	"internalIPAddress": "",
	"ports": [
            "protocol": "ICMP",
            "port": 0
            "protocol": "TCP",
            "port": 802,
            "portTo": 810
            "protocol": "TCP",
            "port": 9841
    "sourceRestrictions": [
            "cidr": ""

If you wish to add an additional internal IP in the migration process, review our "How to Associate Additional Private IPs" article. A blueprint can be deployed in the Control Portal or following this APIv1 documentation.