Company snapshot

CategoryAT&TOnApp CDN
Statusactiveactive
Founded
Headquarters
Website
Docs

Overview

AT&T operates a content delivery network (CDN) as part of its telecommunications portfolio, leveraging its global network infrastructure to deliver content for enterprise and media customers. The CDN focuses on video streaming, live events, and secure content delivery, utilizing AT&T’s extensive fiber and 5G networks. It serves large organizations, including broadcasters and businesses requiring high-bandwidth applications. The service integrates with AT&T’s broader connectivity offerings, such as private networking and cloud solutions. As of 2025, AT&T continues to expand its fiber footprint, aiming to reach over 50 million locations by 2029.
OnApp CDN is a federated content delivery network designed for hosting providers, utilizing spare capacity in OnApp Clouds to deliver content globally. It supports HTTP push, pull, and streaming/live streaming, catering to hosting providers and enterprises managing web content delivery. The platform integrates with OnApp Cloud, enabling users to leverage a network of edge servers for improved performance. It is primarily used by service providers and enterprises needing scalable CDN solutions. The service is operational as of August 16, 2025, with recent updates enhancing its reporting capabilities.

Network & Architecture

AT&T’s CDN operates across 38 data centers globally, with points of presence (POPs) in North America, EMEA, APAC, and LATAM. It leverages the company’s telecom backbone, including its fiber-optic and 5G networks, for low-latency content delivery. The network is optimized for video streaming and live events, with strong peering agreements with major ISPs. Its North American presence is particularly robust, though its coverage in emerging markets like Africa and parts of Asia is less extensive compared to competitors like Cloudflare or Akamai. The architecture emphasizes integration with AT&T’s private network services for enterprise clients.
OnApp CDN operates a global network of Points of Presence (PoPs) by leveraging spare capacity from OnApp Clouds, though specific PoP counts are not publicly detailed. It uses a federated model, combining edge servers from multiple cloud hosts to ensure broad geographic coverage. The platform supports content delivery across regions including North America, EMEA, APAC, and others, with synchronization between CDN and OnApp Cloud occurring every 20 minutes by default. Regional strengths include flexibility for hosting providers, but limitations may arise from reliance on third-party cloud capacity, potentially affecting consistency in less dense regions.

Feature comparison

FeatureAT&TOnApp CDN
waf
bot_mitigation
ddos
rate_limit
http3_quic
tls13
tiered_cache
origin_shield
instant_purge
stale_while_revalidate
stale_if_error
image_optimization
video_vod
video_live
drm
hls_dash_packaging
websockets
signed_urls
edge_compute
functions
kv_storage
api_first
realtime_logs
log_push
terraform

Legend: ✓ = Supported, ✗ = Not supported, — = Not listed

Pricing

AT&T’s CDN pricing is enterprise-only, with custom contracts based on bandwidth, storage, and service level agreements. No public per-GB pricing is available, and there is no free tier or pay-as-you-go option. Pricing details require direct contact with AT&T’s sales team, as no dedicated pricing page is publicly accessible.
OnApp CDN primarily targets enterprise clients, with pricing typically based on committed contracts tailored to hosting providers. No public per-GB pricing is disclosed, and there is no free tier or pay-as-you-go (PAYG) option widely advertised. Pricing details are available through direct inquiry with OnApp sales teams. For more information, visit https://www.virtuozzo.com/onapp-cdn/.[](https://www.virtuozzo.com/onapp-cloud-docs/7.0/release-notes-onapp-6-4/OnApp%2520CDN.pdf)

Integrations & DevEx

AT&T’s CDN offers an API-first interface for configuration and monitoring, with real-time log access for analytics. Documentation is available but lacks support for Terraform or other infrastructure-as-code tools. SDKs are limited, and there’s no mention of CI/CD integrations or migration tools. The focus is on enterprise workflows, with less emphasis on developer-centric features compared to providers like Fastly or Cloudflare.
OnApp CDN offers API-first integration for managing CDN resources, with documentation available at https://docs.onapp.com/cdn/. Real-time logs support monitoring, but there is no public evidence of Terraform support, SDKs, or specific CI/CD integrations. The platform includes tools for managing CDN resources within the OnApp Control Panel, with recent UI updates enhancing usability. Migration tools or import capabilities are not explicitly documented.

When it fits

  • Enterprises needing a telecom-backed CDN integrated with private networking or 5G for secure, high-bandwidth content delivery.
  • Media companies requiring robust video-on-demand and live streaming with global reach and DDoS protection.
  • Organizations already using AT&T’s connectivity services, seeking seamless CDN integration.
  • Hosting providers needing a federated CDN integrated with OnApp Cloud for scalable content delivery.
  • Enterprises requiring video VOD and live streaming with global reach through a network of edge servers.
  • Users prioritizing API-driven management and real-time logging for CDN operations.

When it doesn’t

  • Small businesses or developers looking for pay-as-you-go pricing or a free tier, as AT&T targets enterprise clients.
  • Users needing advanced edge compute, image optimization, or developer-centric tools like Terraform support.
  • Customers prioritizing extensive POP coverage in Africa or smaller APAC markets, where AT&T’s presence is limited.
  • Small businesses or startups seeking pay-as-you-go pricing or free tiers, which OnApp CDN does not offer.
  • Organizations needing advanced security features like WAF, DDoS protection, or bot mitigation, which are not documented.
  • Users requiring edge compute, image optimization, or specific protocol support like HTTP/3, which are unsupported.

History & Notes