Routing
Sub-10s SASE Failover
An in-process health daemon switches hub peers before end-user calls can drop.
Test< 10 s
HOW IT WORKS
Walk through a single flow
- 1Probes run on a sub-second cadence with a composite score across ICMP, HTTP, and DNS.
- 2A consecutive-failure threshold triggers the decision to switch.
- 3Peer reassignment and routing changes execute atomically, without cleartext leak or peer overlap.
- 4Hysteresis protects against borderline endpoints causing flap.
UNDER THE HOOD
Technical notes
Why in-process?
Externally scheduled failover takes tens of seconds at best. The in-process daemon reacts to probe results immediately, so switchover completes inside a single user session.
RELATED