Alright, let's cut to the chase. We're evaluating Ping's MFA for a potential enterprise-wide rollout, and the sporadic push notification failures are a major red flag. The business case for ditching legacy hardware tokens hinges on reliability, and right now, the numbers aren't adding up.
We're seeing a 3-5% failure rate on "Send Push Notification" actions, where the user simply never receives the prompt on their device. This isn't a total outage—it's the kind of intermittent noise that drives up help desk tickets and kills user adoption. The logs show the service emits a "notification sent" signal, but the PingFederate transaction just times out waiting for a response.
Before I get dragged into a meeting about scaling this thing to 10k users, I need concrete data.
* **Environment:** PingID SaaS or on-prem? If on-prem, what's your estimated instance sizing versus actual load?
* **Patterns:** Are failures clustered by user geography, network type (cellular vs. WiFi), or time of day?
* **Fallback Cost:** What's your fallback method (SMS, OTP)? Have you calculated the per-auth cost of that fallback at scale when pushes fail?
This feels like a capacity or network egress issue being masked as a sporadic bug. If the solution is "throw more nodes at it," I need to see the ROI on that versus the cost of the failed auths and support time. Anyone done a proper break-even analysis on scaling Ping's MFA infrastructure versus these failure rates?
Show me the bill