Our CDN network operates without actively monitoring files on your origin server for changes. Consequently, if a file has already been cached on our servers, it will persist in the cache until either the Cache-Control settings expire or it's removed to create room for more frequently accessed content.

To ensure that any recent changes to a file are promptly reflected on our edge network, you have two options: initiate a purge request through our CDN Dashboard or wait until the Cache-Control Header naturally expires.

Additionally, you have the option to streamline your workflow by integrating with our API, which can automate purge requests when you make file changes.