Skip to main content

​
Introduction

A dedicated edge network gives your Private Cloud its own isolated edge zone with full control over caching, custom rules, and traffic visibility. This feature appears as the “Private network” card on your environment’s canvas. A dedicated edge network includes everything in the shared Cloud Edge Network, plus:
  • Rule builder: Create cache rules and custom rules with execution ordering inside each rule type.
  • Custom rules: Match requests on conditions like path, IP, country, or headers, and apply a challenge, block, or IP access action.
  • Cache rules: Override default caching with per-path control over cache eligibility, edge TTL, browser TTL, stale-while-revalidate, and ETag handling.
  • Traffic visibility: Review the top IP addresses and paths hitting your edge over the last 24 hours, 7 days, or 30 days.
  • Rule event counts: See how many requests matched each custom rule and rate limit rule in the last 24 hours.
Dedicated edge networks are available to Private Cloud customers. Contact Sales to request one.

​
Custom rules

Custom rules let you define request-matching conditions and apply an action to anything that matches. They are useful for blocking known-bad traffic, allowing specific clients, presenting challenges to suspicious requests, or restricting access by IP. Each custom rule has:
  • Conditions: Request properties to match against, including path, hostname, IP, country, user agent, headers, and query parameters.
  • Action: What happens to a matching request. Available actions are challenge, block, and IP access (allow or block specific addresses or ranges).
  • Name: A human-readable label for the rule.
Rules execute in order within the custom rules section, and the first matching rule wins. You can reorder rules by dragging them. To create a custom rule, click on the “Private network” card from your environment’s canvas, then add a new rule under “Custom rules”.

​
Cache rules

Cache rules give you per-path control over how content is cached at the edge and override the default extension-based caching behavior described in the Cloud Edge Network documentation. Each cache rule applies to requests matching its conditions and lets you configure:
  • Cache eligibility: Whether matching responses are eligible for caching at all.
  • Edge TTL: How long the response stays in the edge cache.
  • Browser TTL: The cache lifetime served to the client browser.
  • Serve stale while revalidating: Serve a stale response while a fresh copy is fetched in the background.
  • Respect strong ETags: Honor strong ETag validators on origin responses.
Cache rules execute in order within the cache rules section, independent of custom rules, and can be reordered by dragging.
Cache rules do not display per-rule hit counts. Use the traffic cards on the network overview to understand cache performance instead.

​
Traffic visibility

The network overview displays cards showing the top IP addresses and top paths hitting your dedicated edge network. Use the time filter to switch between the last 24 hours (the default), 7 days, or 30 days. Clicking a row in the traffic cards opens a new custom rule pre-filled with that IP or path as a condition, allowing you to act on anomalous traffic immediately.

​
Rule event counts

Custom rules and rate limit rules display an inline event count for the last 24 hours next to each rule, showing how many requests matched. Cache rules do not display this count.