Site Launch FAQ
This document provides a list of questions that customers commonly ask when preparing to launch new sites on the Arc XP platform.
What is a site launch?
Arc XP site launches intentional increases in user traffic to your Arc XP-hosted site. Typically, the traffic increase is public traffic directed to the Arc XP content delivery network (CDN), but it can also include an internal beta launch. We typically refer to launches as cutovers.
What are the options for site cutover?
You have four primary options for your cutover plan:
Full DNS cutover - A full DNS cutover means your site domain is associated with Arc XP DNS and the majority of your sections and pages are hosted on Arc XP.
Partial cutover - A partial cutover means a subset of your sections and pages are cutover to Arc XP.
Beta - A beta cutover means a subset of your users are directed to the site or part of the site.
Headless - A headless cutover means production site traffic begins using Arc XP APIs.
When can I launch my site? How do I request a site launch?
A site launch requires coordination among multiple Arc XP teams. We ask for two to four weeks of lead time to schedule a launch, and capacity for launches is limited to the following windows on a weekly basis:
Tuesdays: 9:00 AM to 5:00 PM Eastern Time
Thursdays: 9:00 AM to 5:00 PM Eastern Time
We recommend you request your launch far in advance for planning and scheduling purposes, even exceeding a month in advance.
What is a launch freeze window?
A launch freeze window is a set of days when Arc XP does not permit launches to occur. These freeze windows typically align with major holidays where Arc XP capacity to support launches is very limited. These holidays include the weeks of the Fourth of July, Thanksgiving, Christmas, and New Year's Day.
Why do we need approval and coordination with Arc XP to launch?
Arc XP is a complex platform supported by many teams across the technology stack. On-call or after hours launches impact our ability to coordinate and support you effectively. We require launches to occur during standard launch windows so that we can:
Provide hyper-care as your site goes live, having members of the CE and Delivery teams available to react to and troubleshoot any issues that may arise.
Coordinate with the Arc XP platform and product teams for traffic and utilization monitoring.
Establish a standard post-launch cadence as your site moves into operational mode.
How should I prepare for a launch? Is there a list of steps you can provide?
At a high level, you should focus on the following areas when preparing for a launch:
Content delivery configuration (domains, redirects, static files, alt-origins)
Environment configuration (PageBuilder templates, Site Service)
Content creator readiness and support (training and support for your users)
Code management (launch gate, production deploys)
Logistics (go/no-go call, launch call)
Arc Customer Support (ACS) introduction and access setup
For more detailed steps and suggested timing, see Getting Started with a Launch: Launch Checklist.
How should I update my DNS so my domains serve Arc XP content?
Arc XP uses the following process to validate and update your DNS:
The Arc XP team associates your provided domain names with the Arc XP production CDN address in Akamai.
We provide your team a text challenge file to validate your ownership of the domain. You enter the text challenge information into your DNS provider, and Arc XP validates the domain in Akamai.
After the validation is complete, Arc XP provides a DNS CNAME record that you can use for the site cutover.
Several hours before the planned cutover, reduce your current, legacy CDN’s TTL to five minutes. Otherwise, site cutover time takes much longer than necessary.
On the day of launch, change the CNAMEs of your domains to the Arc XP-provided CNAME record. Assuming TTL is set to five minutes, traffic starts directing to Arc XP in 5 to 15 minutes.
For more detailed information on DNS changes, see Managing DNS changes for Arc XP Delivery.
What does the day of launch look like?
The day of your launch typically follows this process:
Both teams join a launch call 30 minutes before the planned launch time.
During this call, Arc XP checks in with your stakeholders to confirm readiness.
If any last minute issues arise, we troubleshoot those issues on the call.
When all work streams are green, we instruct your DNS coordinator to point the host name to Arc XP’s production CDN.
User traffic accesses the new site within 5 to 45 minutes, based on your legacy TTL settings, geographic location, and your previous CDN provider.
Arc XP provides support as needed, and we provide a 404 report at the end of the day.
What happens after launch?
After your site is live, Arc XP monitors traffic and error logs, regularly providing a 404 report. Your team then uses Arc Customer Support when issues occur in your production environment