# A vendor-run backbone changes the path between PoPs, not the path from your branch to the first PoP

Guide, 12 Nov 2026, read 12/13 Nov 2026

**The short answer.** Cato, Aryaka, Check Point and Open Systems describe a private backbone between PoPs. Palo Alto Networks, Forcepoint and Barracuda describe public cloud provider networks. Zscaler describes internet peering. Barracuda runs on the Microsoft Global Network through Azure Virtual WAN, and Cato says its PoPs link over multiple tier-1 carriers.

## The part of the path a backbone touches

A SASE path has three legs: your site to the nearest PoP, PoP to PoP, and the last PoP to the application. A private backbone only changes the middle leg. Your branch still reaches the first PoP over whatever ISP circuit you buy, and the exit PoP still reaches the SaaS provider over the internet or a peering link.

That matters most for traffic that crosses regions: a Frankfurt user reaching a private app in Singapore, or two branches on different continents talking to each other. For a branch that talks to a SaaS app in its own city, the backbone is mostly irrelevant.

## What each vendor publishes about the middle leg

The table groups vendors by what their own pages describe. The wording and the counts are the vendors', read on 12 Nov 2026.

| Vendor | Middle leg as published | Footprint figure as published |
| --- | --- | --- |
| Cato Networks | Own backbone (Cato Neural Edge); PoPs interconnected by multiple tier-1 carriers | 100+ PoPs; 91 named locations in its knowledge base PoP guide (researcher's count) |
| Check Point | Global private backbone, tier-1 links at each PoP, reserved bandwidth, peering agreements; the admin guide footnotes that only some data centers are Check Point-managed | 80+ or 85+ data centers, depending on the page; about 90 regions in the admin guide |
| Aryaka | Own private network | 38 named PoPs on the PoP page, no total stated |
| Open Systems | Private backbone; owner of the PoP infrastructure none found on 12 Nov 2026 | 500+ PoPs in 121 cities across 48 countries |
| Versa | Traffic-engineered backbone and full-mesh overlay | 100+ PoPs in more than 100 metros |
| Netskope | NewEdge, described as a private security cloud | 120+ data centers in 80+ regions |
| Palo Alto Networks | AWS, Google Cloud and Oracle Cloud Infrastructure | Over 150 PoPs and compute locations |
| Forcepoint | PoPs built on AWS (February 2022 release) | 300+ PoPs in 2022 and 2023 releases |
| Barracuda | Microsoft Azure and the Microsoft Global Network via Azure Virtual WAN | 17 Azure regions in the vendor list |
| Zscaler | Peering with ISPs at internet exchanges; vendor-run backbone none found on 12 Nov 2026 | 160+ or 200+ data centers, depending on the page |

## Private does not mean owned

Cato states that its PoPs are interconnected by multiple tier-1 carriers. So even a vendor-run backbone rides on carrier capacity somebody else owns. What you are buying is the routing, the capacity reservation and the monitoring that the vendor adds on top. Check Point likewise lists reserved bandwidth and peering agreements, which are commercial arrangements, not fiber the vendor owns.

Barracuda is explicit the other way. Microsoft documents that Azure Virtual WAN hubs connect over the Microsoft backbone, so the inter-site backbone for SecureEdge is run by Microsoft. That can be a fine design. It also means a Barracuda SLA cannot promise what Microsoft does not. Barracuda's own availability commitment excludes platform or hosting provider failure.

## The numbers do not agree with each other

Footprint figures need a date and a page. Cato says 100+ PoPs while Network World reported more than 85 in March 2026, Wikipedia lists more than 73 in over 150 countries, an older and undated figure, and Cato's knowledge base lists 91 named locations. Zscaler gives 160+ data centers on one page and 200+ in an October 2026 release. Fortinet gives 200+ PoPs on its product page and over 190 in its annual report. Netskope gives 11,000+ peering adjacencies on one page and over 12,000 on another.

Check Point says 80+ data centers on two pages and 85+ on another. None of this is dishonest, and none of it is a basis for a comparison. Ask for the PoP list that applies to your contract, and count only the ones in your regions.

## What to measure instead

Ask for the measured result on your actual site pairs. Fortinet publishes tunnel guidance in its administration guide: jitter under 30 ms and packet loss of 0%, plus a speed test at speed.fortisase.com. That is the kind of figure you can check from a branch. Cloudflare states that 95% of the world's internet-connected population is within 50 milliseconds of one of its data centers, and that it interconnects with over 13,000 networks. Those are vendor figures about proximity, not about your path.

Cisco shows what a mixed footprint looks like. Its region table, updated 8 Nov 2026, has 96 region rows in 31 countries by my count: 47 Cisco Edge, 15 Cisco Edge v2 in private preview and 34 public cloud rows using AWS. Cisco does not describe a private backbone between regions on those pages.

Run your own test. Send a fixed-size transfer between two sites in different regions, through each candidate, at the same hour on five days, and record the median and the worst case. That takes an afternoon of scripting and it is the only number that is yours.

Ask each vendor whether PoP-to-PoP traffic ever leaves its stated backbone for the public internet, for example when a link is saturated. A written answer to that one question tells you more than a PoP count.

## Where the middle leg decides the outcome

Two cases. First, inter-region private app access, where latency compounds with every hop. Second, China, where the path crosses a regulated border. Zscaler states that China Premium Access runs on its Chinese technology partners' backbone, so it is a partner network. Cato states it operates licensed PoPs in Beijing, Shanghai and Shenzhen. Fortinet's administration guide warns that mainland users connecting to a PoP outside China may see slower or less direct routing.

If neither case applies to you, a public cloud footprint with PoPs in your cities is likely enough. If both do, ask each vendor to put PoP-to-PoP latency and loss in the contract as a measured term, and read the SLA guide on this site first.

## Sources

- Cato Networks, platform architecture: https://www.catonetworks.com/platform/architecture/ (read 12 Nov 2026)
- Cato Networks, global private backbone: https://www.catonetworks.com/platform/global-private-backbone/ (read 12 Nov 2026)
- Check Point, Private Access: https://www.checkpoint.com/harmony/sase/private-access/ (read 12 Nov 2026)
- Aryaka, global PoP locations: https://www.aryaka.com/about-us/global-pop-locations/ (read 12 Nov 2026)
- Open Systems, SD-WAN backbone: https://www.open-systems.com/sase/sd-wan-backbone/ (read 12 Nov 2026)
- Versa, SASE Fabric: https://versa-networks.com/products/versa-sase-fabric/ (read 12 Nov 2026)
- Netskope, NewEdge: https://www.netskope.com/newedge (read 12 Nov 2026)
- Barracuda, SecureEdge secure SD-WAN: https://www.barracuda.com/products/network-protection/secureedge/secure-sd-wan (read 12 Nov 2026)
- Microsoft, Azure Virtual WAN overview: https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about (read 12 Nov 2026)
- Cisco, Secure Access regions: https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/regions-intro/secure-access-regions.html (read 12 Nov 2026)
- Cloudflare, network: https://www.cloudflare.com/network/ (read 12 Nov 2026)
- Zscaler, China FAQ: https://www.zscaler.com/privacy-compliance/china-faq (read 12 Nov 2026)

Last reviewed 12 Nov 2026. Canonical: https://bestsasesolutions.com/guides/what-a-private-backbone-changes/
