Overview
Edgio was the name adopted by Limelight in June 2022 after acquiring Edgecast. The combined business covered content delivery, application security and streaming.
Azure CDN from Edgio has retired. Existing customers should check the migration destination for their specific product.
Network
Past features
Historical product families covered delivery, application security and media workflows. Capabilities differed between products and contracts.
Use the old configuration and traffic records to identify replacement requirements for cache rules, protection, media formats, logs and automation. Current Parler/Triton Edgecast documentation does not automatically describe former Edgio contracts.
Migration guidance
For a retired Azure CDN from Edgio workload, verify the destination service, DNS, certificates, origin access and cache behavior. Check Azure delivery options or another current provider against the actual application requirements.
Akamai ’s selected customer-contract purchase is not a promise that every former Edgio account or configuration migrated automatically. Confirm account-specific arrangements.
Build a replacement budget from delivery, request, origin, security and media charges. Use old invoices to recover traffic volumes, then price the replacement with current rates.
Sunset timeline
- 2022-06-15 — Limelight adopted the Edgio name after the Edgecast acquisition. — Historical corporate and product combination.
- 2024-09-09 — Edgio filed for Chapter 11. — The filing initiated a sale process; it did not itself prove universal service termination.
- 2024-12-13 — Akamai completed a selected-asset purchase. — Certain contracts and patent licenses; network assets excluded.
- 2025-01-15 — Azure CDN from Edgio retired. — Microsoft identifies this date for its Azure service.
Budgeting for a replacement
Budget replacement delivery using the destination provider’s current rates. Use historical invoices to recover traffic and usage, then request current rates for the replacement.
Build the replacement budget from the destination provider’s written rates:
- Regional delivery and request charges.
- Origin transfer, storage and operations.
- Security, media processing and support.
- Commitments, fixed fees and transition costs.
Use a current-provider calculator or enter an effective quote in the standalone calculator. Confirm account-specific migration terms.
Historical integrations
Preserve the former property configuration, certificates, origin settings, API clients and log pipelines when assessing a replacement. Product-specific tooling needs to be mapped to the selected destination.
For Azure Developer CLI installations, Microsoft documents changed download endpoints and updated installation scripts. That guidance covers the CLI workflow rather than every CDN integration.
What to know
Planning a replacement
History
Limelight operated from the Phoenix area from 2001 and was incorporated in 2003. It adopted the Edgio name on June 15, 2022.
Edgio filed for Chapter 11 on September 9, 2024. Akamai completed a purchase of selected customer contracts and non-exclusive patent licenses on December 13, 2024. The deal excluded Edgio personnel, technology and network assets.
Microsoft identifies January 15, 2025 as the Azure CDN from Edgio retirement date. For another Edgio product, check its own service notice and migration destination.
Sources
- learn.microsoft.com/en-us/azure/cdn/migrate-edgio-to-front-door
- learn.microsoft.com/en-us/azure/developer/azure-developer-cli/content-delivery-network-changes
- www.sec.gov/Archives/edgar/data/1391127/000139112723000016/llnw-20221231.htm
- www.sec.gov/Archives/edgar/data/1391127/000119312524215572/d795614dex991.htm
- www.ir.akamai.com/news-releases/news-release-details/akamai-completes-acquisition-select-assets-edgio
