Edge Caching
Edge caching saves your Kinsta site/page cache (which is only saved to your site’s data center) to any of Cloudflare’s global network of 260+ data centers. When your visitors load your application in their browser, cached responses will be delivered from the location closest to them, increasing the performance and speed of your application.
Edge caching serves your Kinsta site/page cache but does not serve static assets like images, JavaScript files, and CSS files. Kinsta’s CDN, which is independent of edge caching, can be enabled to serve your static assets. If Kinsta CDN is enabled, your site has an additional caching layer managed separately from edge caching. Clearing the edge cache for applications also clears the CDN cache.
Edge caching is not enabled by default on Application Hosting. The application’s Overview page shows if edge caching is enabled or disabled.
Enable or disable edge caching
To enable edge caching within MyKinsta, click Applications > app name > Networking, and within CDN/Edge caching, click Edit settings.
To enable edge caching, select Edge caching status.
You can also enable or disable edge caching by sending a POST
request with the edge-cache API endpoint. To access and use the API with your account, you need to generate an API Key.
To use the edge caching API endpoint you need you need your application’s unique ID. You can obtain this programmatically by listing all applications associated with your Kinsta company with the applications endpoint, which provides essential details about each application.
Clear edge cache
To clear the edge cache, within MyKinsta, click Applications > app name > Networking, and within CDN/Edge caching, click Purge cache. If both CDN and edge caching are enabled, purging the cache will apply to both.
You can also clear the edge cache by sending a POST
request with the clear-cache API endpoint. If you have enabled the CDN, it also clears the CDN cache.
Clearing edge cache in all of Cloudflare’s data centers may take 2-5 minutes to fully complete.