[JIRA CDNC-12500] Cadence alert fired during peak failover drill Feb 21, 2025

[vishwa-uber]

Context: During Friday UFA Peak Traffic Drill, the following alerts went off for your service cadence:

1. Feb 21, 2025 : [CRITICAL] [Service: cadence][prod-phx2]: SyncMatchLatency Max P99 Latency below SLO threshold -https://umonitor.uberinternal.com/alerts/e7a4d7e6-ce9a-420d-a77d-07b1c6f93d9e
2. Feb 21, 2025 : [CRITICAL] [cadence] gateways ""exeggutor"" latency SLA Breach-https://umonitor.uberinternal.com/alerts/50681dd8-f91e-4505-b4bf-141a5a98c998
3. Feb 21, 2025 : [CRITICAL] [Service: cadence-production06][prod06-dca]: SyncMatchLatency Max P99 Latency below SLO threshold -https://umonitor.uberinternal.com/alerts/bc63742d-b4cd-4f60-aba4-8a6619d7402f
4. Feb 21, 2025 : [CRITICAL] Flipr error during cadencefx start up-https://umonitor.uberinternal.com/alerts/f1903565-18d9-4208-8038-65afa107194b

Details Required:

Business Impact: What was the impact captured by these alerts and in what ways did it affect the business? How many customers/users were impacted?
Mitigation Actions: What steps were taken to resolve or reduce the impact?
Preventive Measures: What actions are being implemented to prevent this in future failovers (outage or drill)?

Please just answer the details above as a comment in the jira ticket below to complete.