Historical provider.
The listed service has been retired. The brand has changed name.

Website

Overview

This entry covers NTT’s former CDN Platform Powered by Edgecast. Its service notice gives January 15, 2025 as the retirement date.

NTT Communications was established in 1999 with headquarters in Tokyo. It changed its name to NTT DOCOMO BUSINESS on July 1, 2025 and continues to offer a separately documented Akamai-powered CDN.

Use the current Akamai-based service’s documentation and quote for a new project or replacement.

Network

The former Edgecast delivery footprint is historical and is not plotted as an available current network. NTT’s telecom offices, backbone routes and data centers are also not interchangeable with CDN caches.

For a current deployment, use the selected NTT/Akamai service’s coverage and contractual details. Test the audience locations that matter to your application.

Past features

Current feature support is unconfirmed for the retired Edgecast-powered platform. Delivery, security, automation and reporting requirements must be checked against the chosen replacement and its plan.

Service status

For a former NTT Edgecast deployment:

  1. Confirm the account’s service, migration outcome and contract through NTT support.
  2. Recover hostnames, origins, certificates, cache rules, access controls and delivery records.
  3. Configure and test the selected replacement, including domain ownership and origin restrictions.
  4. Change DNS only after verifying behavior; remove obsolete routing records when safe.

NTT’s separate Akamai -powered service has current support and tutorials. Ask NTT for the migration arrangement for your account. Use the current calculator with confirmed replacement rates rather than old Edgecast pricing.

Media Services Live 4 retirement

If the replacement uses NTT’s Akamai-powered Media Services Live 4 (MSL4), migrate that media workflow to Media Services Live 5, powered by Harmonic, before December 31, 2026. NTT warns that existing MSL4 streams will be disabled from that date. Review Akamai’s MSL5 migration guide and confirm the arrangement with NTT. This deadline concerns MSL4; it does not retire NTT’s entire Akamai-powered CDN.

History timeline

  • 1999-07-01 — NTT Communications established — Company history, separate from CDN service launch.
  • 2025-01-15 — Edgecast-powered CDN service retired — Date retained from the prior official service notice.
  • 2025-07-01 — Company renamed NTT DOCOMO BUSINESS — The company continues, with a separate Akamai-powered service.

Budgeting for a replacement

No current tariff applies to the retired Edgecast-powered service. NTT’s current Akamai offering is a separate commercial product; confirm the contract, delivery/request meters, minimum commitments and optional-service costs.

Use the calculator for current providers or enter a confirmed replacement quote. Historical zero-valued tariff placeholders are not free delivery.

Historical integrations

Former Edgecast API and portal details should be recovered from the actual account records where available. Confirm current support and compatibility before reusing those references.

NTT’s current Akamai service publishes tutorials for reports, cache deletion, domain ownership, EdgeDNS and SiteShield. Evaluate those separately when choosing the replacement.

What to know

For a former NTT Edgecast account, recover the delivery configuration and confirm the migration destination. Evaluate NTT’s current Akamai-powered service using its own terms and documentation.

Planning a replacement

The Edgecast-powered service has retired. For a new deployment or replacement, use the current NTT/Akamai service’s own documentation, coverage and quote.

History

Company and service are separate

  • 1999: NTT Communications was established.
  • January 15, 2025: its notice records the end of the Edgecast-powered CDN service.
  • July 1, 2025: the continuing company became NTT DOCOMO BUSINESS.

The current Akamai-based service has its own contract, configuration and product scope. For an old account, check the migration destination and supported settings with NTT.

Sources