Discontinuation notice: Old domain brokers
Background
While the CDN service and Custom domain service have not allowed the creation of new domain services for over four years, there are still domain services on these old brokers which were never migrated to the External domain service.
We have decided to fully retire the older services on February 1, 2026. We're here to support you in the transition, and aim to do so with minimal disruption to your operations.
Timeline
| Dates | Important information |
|---|---|
| Now - February 1, 2026 | Customers migrate their services to the external domain broker |
| February 1, 2026 | The Cloud.gov team removes the infrastructure for the old CDN service and Custom domain service brokers |
| After February 1, 2026 | Certificate renewals for domains handled by the CDN service and Custom domain service brokers will fail, leading to a possible outage for your site if you do not upgrade your domain service before this date. |
How to know if you are affected
If you are using service(s) on one of the old domain brokers, you will be contacted either by the Cloud.gov or the Cloud.gov Pages support teams. The email will specify which services are affected and include instructions on how to migrate your service(s).
All affected customers should receive a notification by Friday, October 10, 2025.
If you want to check for yourself whether you are using one of deprecated services,
you can use this shell script (replacing your-org with your actual organization name):
MY_ORG="your-org"
ORG_GUID=$(cf org --guid "$MY_ORG")
PLAN_GUIDS=$(cf curl "/v3/service_plans?names=custom-domain,cdn-route" | jq -r '[.resources[].guid] | join(",")')
cf curl "/v3/service_instances?organization_guids=$ORG_GUID&service_plan_guids=$PLAN_GUIDS" | jq '.resources[] |.name'
The script will return the names of any service instances on the deprecated brokers, if there are any.
How to migrate your service(s)
The notification email from Cloud.gov will include specific instructions for how to migrate your service(s), but in general, there are two migration paths:
- Automated migration
- Manual migration
Whether you can use automated migration or manual migration is based upon whether the domain(s) for your service(s) are apex domains.
Automated migration for non-apex domains
Follow the steps on documentation for migrating domain service(s) to create or update your DNS records to the values expected by the external domain broker. Once you complete these steps, your domains will automatically be migrated to external domain services with no downtime.
Manual migration for apex domains
Migrating service(s) for apex domains requires coordination between DNS updates and the provisioning of new CDN services, so performing these migrations is best done on a scheduled call with the Cloud.gov support team or Cloud.gov Pages support team.
You can schedule a call to perform your migration by contacting Cloud.gov support at support@cloud.gov or Cloud.gov Pages support at pages-support@cloud.gov.
Questions
If you have any questions, please contact support@cloud.gov.