What's New?

We are constantly improving your CDN experience by:

Adding new services.
Adding new features.
Revising existing features to provide a more intuitive and flexible CDN configuration.

Key recent changes to our CDN service are listed below.

02/09/2022	We have reserved the 700 - 999 status code range for communication between our servers. Your servers should not return a status code within this range. Learn more.
07/20/2021	Rules Engine now has: Improved internationalization support for the following match conditions: URL Path Literal \| URL Path Regex \| URL Path Wildcard \| URL Query Literal \| URL Query Regex \| URL Query Wildcard More flexible customer origin matching for the following features: Cache-Key Rewrite \| URL Redirect \| URL Rewrite
06/25/2021	RTLD CDN now supports the following log fields: client_tls_version \| origin_name \| platform \| prewrite_time \| total_time Learn more.
06/01/2021	We have released Edge Image Optimizer. Use this feature to dynamically optimize your images at the edge of our network.
05/28/2021	RTLD now supports the following log delivery destinations: Google Cloud Storage. New Relic (RTLD CDN only).
05/24/2021	We have introduced the Identity dashboard. Leverage this dashboard to manage your multi-factor authentication configuration and OAuth 2.0 API clients. You may no longer manage two-factor authentication from within the TCC. Additionally, existing two-factor configurations have been reset.
03/12/2021	RTLD WAF now supports the ability to filter log data by Security Application Manager, Access Rule, Custom Rule, or Managed Rule configuration.
2/24/2021	Custom rules now also allows you to identify traffic by country, IP address, and the request URL path including query string. Learn more.
02/08/2021	Web Application Firewall now supports custom rules. Custom rules allow you to define a profile or pattern through which WAF will identify threats. For example, you can create a custom rule that identifies requests by user agent. Learn more.
12/15/2020	We have released a new version of WAF. It expands upon all of the capabilities offered by WAF (legacy) and Rate Limiting (legacy) with a simplified and centralized setup that allows you to: Define the type of requests that will be secured. Reuse configurations when securing different applications. Learn more.
12/11/2020	Real-Time Log Delivery (RTLD) now consists of two modules: RTLD CDN encompasses the original behavior of RTLD. Use this module to deliver log data that describes requests submitted to our CDN service. RTLD WAF provides new functionality. Use this module to deliver log data that describes requests identified by WAF.
09/29/2020	Real-Time Log Delivery now supports the ability to filter log data by user agent.
09/08/2020	Edge Performance Analytics now supports the ability to generate reports for 400 Bad Request, 401 Unauthorized, and 429 Too Many Requests status codes.
09/02/2020	Real-Time Log Delivery now supports the ability to log custom request headers, response headers, and cookies. Learn more.
08/31/2020	Real-Time Log Delivery now supports the following log fields: Background Fill Wait Time Client City Client Region Learn more.
08/25/2020	Real-Time Alerts now supports the ability to selectively apply alerts to specific edge CNAME configurations. Learn more.
08/14/2020	We have released the following features for Rules Engine - Advanced: Revalidate While Stale Revalidate While Stale Timer These specialty features, which should not be confused with the Stale While Revalidate feature, determine how often our service will attempt to revalidate with your web servers when communication has been temporarily disabled due to repeated origin server availability issues.
08/06/2020	We have released the Mask Client Subnet feature for Rules Engine - Basic. This feature masks a client's IP address for logging and reporting purposes.
06/18/2020	We now support the following HTTP variables: Path %{path} The Request URI variable (i.e., %{uri}) was deprecated in favor of the Path variable. Please update your configurations to use %{path} instead. Normalized Path %{normalized_path} Normalized Query String %{normalized_query} Normalized URI %{normalized_uri} QUIC Versions %{quic_altsvc_versions}
05/05/2020	Our implementation of QUIC now supports Google's latest format for specifying QUIC versions. If you have implemented QUIC via our QUIC feature, then no additional action is required on your part to leverage the latest QUIC versions. Manually enabling QUIC via HTTP variables is not recommended. The recommended method for enabling QUIC is via the QUIC feature.
05/05/2020	We now support the WebSocket protocol. This protocol is useful for applications that require low latency or full-duplex communication. Learn more.
04/17/2020	Log data may now be delivered to your web server(s), AWS S3, Azure Block Blob, Splunk Enterprise, Sumo Logic, and Datadog in near real-time by leveraging Real-Time Log Delivery. Learn more.
03/03/2020	Due to the security risks inherent to FTP (e.g., authentication via cleartext passwords), access to CDN storage over FTP is undergoing end-of-life and will only be available until May 26, 2020. If you are currently using FTP to view/manage CDN storage, please update your workflow to use SFTP or rsync. Learn more.
02/14/2020	Rules Engine now supports the ability to identify traffic through the following Device match conditions: Is App? Is Full Desktop? Is Robot? Is Touchscreen? Is Windows Phone?
02/14/2020	Rules Engine now supports HTTP variables that provide the client's request protocol (i.e., %{virt_http_version}) and SSL/TLS connection information (i.e., %{virt_ssl_cipher} and %{virt_ssl_protocol}).
02/14/2020	Stale responses now include a Warning response header.
08/06/2019	Rules Engine now supports HTTP variables (i.e., %{http_x_ec_uuid} and %{http_x_ec_session_id}) that track requests and sessions.
07/10/2019	Rules Engine now supports the ability to identify traffic through the following Location match conditions: City Name Literal City Name Regex Continent DMA Code Latitude Longitude Metro Code Postal Code Region Code
06/11/2019	A new POP location (i.e., CHZ) in Chicago, Illinois, USA is now live.
05/02/2019	A new POP location (i.e., NYZ) in New York, New York, USA is now live.
04/24/2019	A new POP location (i.e., DAZ) in Dallas, Texas, USA is now live.
04/17/2019	A new POP location (i.e., DCY) in Ashburn, Virginia, USA is now live.
04/12/2019	A new POP location (i.e., MAY) in Madrid, Spain is now live.
02/28/2019	The maximum file size for edge server compression has been increased to 3 MB.
01/09/2019	A new Rules Engine feature (i.e., QUIC) and an HTTP variable (i.e., %{quic_versions}) have been introduced to make it easier to set up QUIC support. Learn more about QUIC.
10/18/2018	A new POP location (i.e., SGZ) in Singapore is now live.
10/18/2018	A new POP location (i.e., SKZ) in Stockholm, Sweden is now live.
09/13/2018	A new POP location (i.e., VIY) in Vienna, Austria is now live.
08/14/2018	A new Edge Performance Analytics report for the 503 Service Unavailable response code is now available. Learn more.
08/02/2018	A new POP location (i.e., LAZ) in Los Angeles, California, USA is now live.
06/26/2018	A new POP location (i.e., PAZ) in Paris, France is now live.
06/26/2018	A new POP location (i.e., SEY) in Seattle, Washington, USA is now live.
06/19/2018	Due to the security risks inherent to FTP (e.g., authentication via cleartext passwords), log delivery to your web server over FTP is undergoing end-of-life and will only be available until September 1, 2018. If you are currently using FTP for log delivery, please update your log delivery configuration to use SFTP immediately. Learn more.
06/05/2018	A new POP location (i.e., MIY) in Miami, Florida, USA is now live.
05/31/2018	A new POP location (i.e., SYY) in Sydney, Australia is now live.
05/15/2018	Our service no longer supports TLS 1.0 and older protocols. Please implement TLS 1.2 encryption. Learn more.
04/20/2018	Rules Engine now supports the capability to define the variables that are passed to bespoke traffic processing logic. Learn more.
04/18/2018	A new POP location (i.e., SJY) in San Jose, California, USA is now live.
03/17/2018	CDN traffic may now be tracked on a per edge CNAME basis via Custom Reports. Learn how to activate the custom reports capability.
3/16/2018	Edge Optimizer Edge Optimizer has been deprecated and should not be applied to your traffic. This feature is scheduled to undergo end-of-life in the near future.
02/13/2018	A new POP location (i.e., LHY) in London, United Kingdom is now live.
01/18/2018	Platform-specific real-time statistics may now be filtered by edge CNAME, POP, or country. Learn more.
12/19/2017	A new POP location (i.e., JNZ) in Johannesburg, South Africa is now live.
7/10/2017	The main landing page is now known as the dashboard. As a result of this change, the Home menu item has been renamed to "Dashboard."
4/27/2017	User administration has been redesigned. As a result, the following changes were made: User configuration is now split into two tabs. There is a tab for user settings (i.e., User Info) and another one for defining API access and privileges (i.e., Permissions). The capability to delete a user and various user settings have been moved to a More Details section within the User Info tab. Delete the current user or view/configure those settings by expanding that section. The Grant API Access Token option has been removed. A user's API permissions now determine whether that user will be granted a Web Services REST API token. A user must be granted access to at least one HTTP method (e.g., GET or POST) in order to receive a token. The PUT/POST API permission has been split into two separate permissions (i.e., PUT and POST). By default, the GET method is marked when creating a new user. An account-wide two-factor authentication may no longer be defined. Two-factor authentication may now only be configured on a per user basis. By default, the Two-Factor Authentication option is turned on for new users. If two-factor authentication was previously disabled across the entire customer account, then it currently cannot be enabled on a per user basis. Existing customer accounts will be migrated soon to take advantage of this capability. An administrator may no longer reset a user's password when clearing a 2FA configuration. The Password Expiration label has been renamed to Password Reset Duration. Additionally, it may now only be set to never expire or a preset time interval (i.e., 30, 90, or 120 days).
2/1/2017	Customer origin server compression now supports Brotli. Learn more.
11/17/2016	A new version of the Network Status page and additional notification methods for maintenance windows and network status have been introduced. Learn more.
11/07/2016	The following navigation changes have been introduced: The navigation tabs and the sub navigation bar have been replaced with a menu. The main menu is restricted to a maximum of 4 menus. If more than 3 menus should be displayed, then an additional menu called "More" will be displayed. This menu contains a comprehensive listing of all top-level menus. The top-level navigation links have been moved into a drop-down menu called "User Settings." This menu may be accessed by clicking on the customer account label from the upper-right hand corner of the TCC. Learn more.
04/12/2016	The Customer Origin page now supports the filtering of customer origin configurations by name.
03/31/2016	The Edge CNAMEs page now supports the filtering of edge CNAMEs by hostname.
03/30/2016	The Edge CNAMEs page now supports the sorting of edge CNAMEs by hostname, origin directory, or by origin type.
05/27/2015	Token-Based Authentication An update to Token-Based Authentication was introduced. This version contains the following changes: This update addresses a security vulnerabilityTo protect the integrity of customer data, details on the exact security vulnerability cannot be shared at this time. Although we highly value transparency, this policy provides customers additional time to prepare and implement the transition to version 3. with a previous version of Token-Based Authentication. Token-Based Authentication 3.0 leverages a state-of-the-art cryptographic algorithm and other security enhancements for the sole purpose of hardening token encryption/decryption. The above changes were also applied to the following items: Encrypt/Decrypt Tool (Token Auth page) Update Primary Key (REST API) Encrypt Token Data method (REST API) Token Generator (Windows executable, Linux binaries, and source code) View FAQs. You should upgrade to Token-Based Authentication 3.0. Learn how to upgrade. Developers Only: By default, code that leverages the Encrypt Token Data method (Web Services REST API) will generate tokens using version 2.0. Please update your CDN configuration and script/application to use version 3.0. For more information, please refer to the Encrypt Token Data article in the REST API Help Center.