The failover numbers you currently have to guess at.
Running two WAN connections — a UDM/UCG, pfSense, or a router with a failover script — tells you failover happened. It doesn't tell you how long it took, how often it happens, or whether WAN2 is actually pulling its weight. ClumsyLinkWatch tracks all three on a Windows box on your LAN, no enterprise NMS required.
ClumsyLinkWatch periodically resolves your public IP and records a WAN-state change whenever it shifts. A public IP change with no connectivity gap in the timeline means a clean failover. A change with a gap means the failover took a measurable number of seconds — that number is what most dual-WAN setups currently can't produce without building it themselves in Uptime Kuma plus guesswork.
Reported separately per WAN, not blended into one number that hides which link is actually carrying the reliability.
How often failover triggered over a period, and how long it typically takes — the two numbers people want and currently can't get.
Every WAN-state change sits on the same time-proportional timeline as every other detected event, sleep gaps included and excluded correctly.
Free for individual and personal use, no account required. Windows 10/11 only.