SQL availability group failover latency experienced is 35 seconds, which is 10 seconds higher than older SQL Mirror failover

**Encountered problem:** Our use-case has 3 x Server 2022 in a topology of a domain controller with two node cluster. This is a SQL Always On AG architecture. The cluster hosts the SQL availability group roles. This is a replacement for the MS deprecated SQL Mirroring architecture. While the older Mirror setup had a hard (physical power or network cable out) failover time of 10 seconds or less failing over to the database, the newer Always On (AO-AG) system takes 21 seconds. **solutions tried:** Raw database only failover (with simple, threaded client app) takes 22 seconds with all configurations set to optimal as mentioned briefly below: Same client application when run in the Mirror architecture setup on same hardware and databases show a less than 10 second failover to new principal DB - All cluster Role properties and Role Resource properties are set to minimize latency. (image) - Network is a lab based dedicated setup with no other resources utilizing it. - RegisterAllProvidersIP and HostRecordTTL has been changed respectively from 1 and 1200 to 0 and 10. - SQL listener and IP resource roles in use - which is connected to clients before and after failover. - Manual failover occurs within 5 seconds. - Auto failover (pulling net or power cable) takes around 22 seconds for HA AO-AG setup. SQL Mirror setup for same takes around 10 seconds. - MultiSubnetFailover=True and False also has been tried. Did Microsoft make SQL AO-AG slower than the legacy SQL Mirror? **How do I speed up the failover time?** thanks (https://i.sstatic.net/9YO7D.png) Role Resource properties - these have been changed in many permutations