If your cutover causes errors, degraded performance, or origin overload, back out by changing DNS first, then deactivating on Akamai.

How to

1. In your DNS management system, replace the CNAME record with the A and AAAA records that pointed to your origin before the cutover, or with your previous CDN's target. Set the TTL on the restored records to 300 seconds so you keep a short window if you need to change them again.

   ❗️

   Don't delete the record. A hostname with no record at all fails to resolve, which takes your site down entirely.

2. Wait for cached CNAME answers to expire. Wait the TTL your CNAME record was serving while it pointed at Akamai. Some resolvers and clients may hold cached answers longer than the TTL.
3. Confirm your hostnames resolve away from Akamai and that your origin is serving correctly. Query your hostname against a public resolver, then check that your origin is handling full traffic volume without errors.
4. Deactivate the configuration on Akamai. Deactivating while DNS still points at your edge hostname causes errors for users.

Next steps

1. Diagnose the cause before retrying, then test your configuration again.
2. Follow Point traffic to Akamai again. If you had raised your TTL back to standard levels, lower it and wait out the full period again before your next attempt.