> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/how-to/configure-multi-region-deployment-in-waf-saas.md).

# Configure Multi-Region Deployment in WAF SaaS

WAF SaaS supports deployment across multiple regions to improve service resiliency and availability.

### Default Multi-Region Failover Configuration

The default multi-region deployment in WAF SaaS is a failover-based configuration managed by Check Point.

#### How It Works

1. Create two WAF SaaS profiles for the same protected application.
2. Both profiles receive the same DNS hostname.
3. One region serves as the primary region.
4. The second region serves as the standby region.
5. Check Point manages traffic failover between the regions automatically behind the scenes.

#### Failover Conditions

Traffic may be redirected to the secondary region if the primary region:

* Is unreachable
* Does not respond within the expected time
* Returns specific server-side errors

Failover is supported only for the following HTTP methods:

* GET
* HEAD
* OPTIONS

#### Recovery Behavior

When the primary region becomes healthy again:

* Traffic is automatically routed back to the primary region
* The secondary region returns to standby mode

{% hint style="warning" %}

### Important Notes

The failover behavior described above is not supported for special configurations, including:

* Protecting a root (apex) domain which were onboarded prior to May 25th, 2026
* Using custom ports
* Protecting a domain with an existing CDN distribution (for example, CloudFront)

In these cases, each WAF SaaS profile receives a different DNS hostname and traffic is routed directly to the specific profile region.

Customers requiring multi-region traffic handling for these configurations should contact Check Point.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://waf-doc.inext.checkpoint.com/how-to/configure-multi-region-deployment-in-waf-saas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.