Deutsche Telekom

Overview Deutsche Telekom, a major telecommunications provider based in Bonn, Germany, offers CDN services as part of its broader network infrastructure. The company leverages its extensive European network to provide content delivery, primarily targeting businesses in the EMEA region. Its CDN services focus on reliable delivery for web content and applications, with a strong emphasis on security features like DDoS protection and WAF. Deutsche Telekom serves enterprises, media companies, and public sector clients, particularly those requiring robust connectivity within Europe. The service is integrated with its telecom offerings, making it a natural choice for customers already within its ecosystem. ...

August 16, 2025 · CDN Handbook

AT&T

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. ...

August 15, 2025 · CDN Handbook

Security Parity Across CDNs: WAF, Bot Management, Rate Limits, and Origin Authentication

Synopsis Security controls need equivalent outcomes when more than one CDN serves a property. Policy ownership, web application firewall rules, bot defenses, rate limits, origin authentication, secrets, drift control, verification, log normalization, and incident procedures all affect that parity. A routing change must not silently change the security policy. Scope and objectives Security parity means that requests receive the same protection and the same outcomes independent of provider. Rules must be functionally equivalent, telemetry must be comparable, and emergency controls must have the same effect at all edges. Differences in vendor features are handled by choosing portable constructs first and by documenting exceptions that cannot be avoided. ...

CDN Handbook