> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Static Sites - Networking

> Configure public networking options for your static site, including cache purging and rate limiting.

On your static site's **Networking** page, you can purge the CDN/Edge cache and configure rate limiting. To view these settings, go to **Static sites** > ***site name*** > **Networking**.

## Public networking

### CDN/Edge cache

Your static site is served from our global CDN at [the Edge](/static-sites/overview#the-edge). If updated assets aren't showing up after a deploy, you can clear the cached assets yourself instead of waiting for the cache to expire.

To clear the cache, click **Purge cache**. This purges the CDN/Edge cache for your site, so the latest version of your assets is served. The purge takes effect right away, and you'll get a confirmation once the cache is cleared.

<Info>
  Anyone with update access to the static site can purge the cache.
</Info>

### Rate limiting

Rate limiting protects your site from abusive traffic. When enabled, Cloudflare limits each visitor to **100 requests per minute** and applies your chosen action when the limit is exceeded. The limit is fixed and cannot be changed.

#### How requests are counted

Requests are counted per **IP address**, per **domain (hostname)**, and per **Cloudflare data center**, and each combination has its own independent counter. The limit caps individual clients; it is not a hard cap on the total traffic your site receives:

* The same IP address can send up to 100 requests per minute to each of your domains. For wildcard domains, the root domain and each subdomain are counted separately.
* Requests are counted at the Cloudflare data center that serves them, so traffic reaching a domain through multiple data centers - a distributed attack, for example - can exceed 100 requests per minute in total before each source is mitigated.

#### Update rate limiting

To change your rate limiting settings, click **Update settings** within the **Rate limiting** section, toggle **Rate limiting** on or off, and choose one of the following actions:

* **Challenge:** Visitors that exceed the limit must pass a Cloudflare managed challenge to continue. Mitigation lasts 5 minutes.
* **Throttle:** Requests over the limit are blocked only while the rate stays above the limit. Traffic resumes as soon as the rate drops.
* **Ban:** Visitors that exceed the limit are blocked for 5 minutes.

To save the changes, click **Update rate limiting**.

<Info>
  Rate limiting requires an enabled primary domain with active or pointing status. If your site does not have one, set it up on the [Domains](/static-sites/domains) page first.
</Info>

Rate limiting applies to your site's domains. Preview deployment URLs are not rate limited.

<Note>
  Changes take effect within about a minute, whether you enable, disable, or switch the action. When you disable rate limiting, visitors that are already mitigated may remain blocked or challenged for up to 5 more minutes.
</Note>