The length of time website data is cached at a CDN (Content Delivery Network) node depends on the caching rules you specify for your website. The cache time is not a universal setting, but depends on parameters like TTL ( Time To Live ) and HTTP cache headers.
A CDN is a network of servers around the world that stores copies of your website content (images, CSS, javascript and sometimes even pages). When a user visits your website, the CDN delivers content from the nearest node instead of your origin server, resulting in a faster, more efficient experience.
CDN cache lifespan will be based on configuration:
Static files (images, css, js): usually cached for hours, days or even weeks
HTML pages: Typically cached for short periods, from minutes to hours
Dynamic content: can’t be cached or cached for a very short time
The actual length is determined by:
Cache-Control headers
Cache-Control:max-age=31536000,public
CDN Dashboard Configuration
Server-side configuration
TTL is the amount of time content is kept in the cache at a CDN node before it is refreshed from the origin server.
When you’re at home, you’re at home.
TTL = 3600 seconds → 1 hour cache
TTL = 86400 seconds Cache for 24 hours
When the TTL expires, the CDN fetches a new copy from the origin server.
Yes, you can refresh CDN content before the TTL expires with:
Purge / clear cache option
File versioning (renaming a file)
Manual Purge Tools for CDN Dashboard
CDN caching does help:
Speed Optimization of Website
Reduce server load
Improve worldwide performance
Good at managing high traffic.
The CDN node caches website data according to the TTL and cache rules that are configured on your server or CDN. Depending on the type of content and caching policy, the TTL can vary from a few minutes to a few days. Good cache management = fast performance and up-to-date content.