The connection never blinks.
Lattice scores every path and moves your traffic before you'd notice the one that failed. This page is for the engineers who want to know how.
Five moves, sub-second.
No controller round-trip. Decisions live at the edge so failover happens before a session would time out.
- 01
Score every path
Each candidate path across Strand, Halo, and Arc is scored continuously on latency, jitter, loss, and congestion. Scores update on the order of milliseconds.
- 02
Pin the primary
Traffic rides the highest-scoring path. For metro fiber that's Strand — lowest latency, highest capacity — with alternates kept warm.
- 03
Detect the failure
Loss of signal, a latency spike, or a congestion cliff trips the threshold. Detection is local to the edge, not a round-trip to a controller.
- 04
Hand off in flight
Lattice shifts the flow to the next-best path — Strand to Halo, Halo to Arc — sub-second, mid-session, without renegotiating your connection.
- 05
Heal and rebalance
When the primary recovers, traffic eases back. Congestion-aware routing spreads load so no single path becomes the next bottleneck.
A worked snapshot.
Illustrative target values. Lattice keeps lower-scoring paths warm so a handoff costs no setup time.
| Path | Latency | Loss | Score | State |
|---|---|---|---|---|
| Strand · metro fiber | 2.9 ms | 0.000% | 0.98 | primary |
| Halo · aerial relay | 16 ms | 0.002% | 0.71 | warm |
| Arc · LEO mesh | 41 ms | 0.010% | 0.52 | standby |
Halo and Arc rows reflect target performance — Halo is in development, Arc is in research. Neither carries production customer traffic today. We tag what is real.