Fastly provides several levels of cache purging. You can use the "Purge All" command to purge all content under a service.
Exercise caution when purging all content from cache, especially if you're seeing an increase in 503 errors. Purging all content overrides other caching-related settings that allow you to serve stale content and forces Fastly to retrieve that content again from your origin servers before it can be re-cached in Fastly POPs. This means that purging all content will temporarily cause your cache hit ratio to drop dramatically and cause an associated spike of traffic to your origin servers. Be certain your origins can handle that temporary spike in traffic until the cache repopulates.
Before you begin
If you're new to the concept of purging, we recommend familiarizing yourself with our purging basics guide.
Purging all content
To instantly purge all content under your service, follow the steps below:
- Log in to the Fastly web interface.
- From the Home page, select the appropriate service. You can use the search box to search by ID, name, or domain.
From the Purge menu, select Purge all. The Purge all window appears and displays the service name you'll be purging.
- In the field of the Purge all window, confirm you want to purge all cached content on a service by entering the exact name of the service that appears (e.g.,
An Example Service).
- Click the Purge all button.
Explore the other purging methods available with Fastly such as [purging with surrogate keys](/en/guides/purging-with-surrogate-keys) and purging a URL.