// AI Platform Drift
Cloudflare One Appliance HA sites can now configure separate WAN gateways per appliance
Cloudflare developer changelog · published 2026-11-17 20:59 UTC
WHAT CHANGEDCloudflare One Appliance high availability sites can now assign each appliance its own default gateway on a static WAN. The API accepts a new optional field static_addressing.secondary_gateway_address in PATCH requests to /accounts/{account_id}/magic/sites/{site_id}/wans/{wan_id}. The dashboard adds a Secondary gateway address field next to Primary gateway address when configuring static WANs on HA sites. If omitted or set to null, the secondary appliance uses the primary gateway address, matching previous behavior.
WHY IT MATTERSHA pairs can now connect each appliance to a separate ISP circuit with its own static IP and gateway, enabling true dual-circuit redundancy instead of sharing a single WAN gateway. Existing HA configurations continue working unchanged because the field defaults to the primary gateway when not specified.
WHAT TO DOIf you operate Cloudflare One Appliance HA sites and want each appliance on a separate ISP circuit, add static_addressing.secondary_gateway_address to your WAN configuration API calls or populate the Secondary gateway address field in the dashboard. No action required if your HA pairs share a single WAN gateway.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Cloudflare One Appliance, Cloudflare One, Cloudflare WAN - Configure a separate WAN gateway for each appliance in a high availability site +https://developers.cloudflare.com/changelog/post/2026-11-17-appliance-ha-secondary-gateway/ +Tue, 17 Nov 2026 00:00:00 GMT + +You can now give each Cloudflare One Appliance in a high availability (HA) site its own default gateway on a static WAN. Before this change, both appliances in an HA pair shared the same WAN gateway. Now each appliance can connect to its own Internet circuit, such as a different ISP for each appliance, with its own static IP and gateway. + +In the dashboard, when you configure a static WAN on an HA site, enter the secondary appliance's gateway in the new Secondary gateway address field, next to Primary gateway address. +In the API, set static_addressing.secondary_gateway_address when you create or update a WAN. To remove the value with a PATCH request, set it to null. + +The field is optional. If you leave it blank, the secondary appliance uses the primary gateway address, which matches how HA sites worked before. You can only use this field on sites in HA mode. +curl --request PATCH \ +https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/wans/{wan_id} \ +--header "Authorization: Bearer <API_TOKEN>" \ +--header "Content-Type: application/json" \ +--data '{ +"static_addressing": { +"address": "203.0.113.2/30", +"gateway_address": "203.0.113.1", +"secondary_address": "198.51.100.2/30", +"secondary_gateway_address": "198.51.100.1" +} +}' +For details, refer to About high availability configurations.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | New API field and HA configuration capability changes how teams deploy dual-appliance sites. |
| signals | new API field introduced: static_addressing.secondary_gateway_address · breaking change to HA site behavior: secondary appliance gateway now configurable · API schema expansion: PATCH request now accepts secondary_gateway_address parameter · deployment model change: each appliance can now use separate ISP circuits · backward compatibility preserved: field optional, defaults to primary gateway if omitted |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |