Spike in KBA timeouts this week

Past three RON sessions, signers passed credentialing and liveness but the KBA timed out on both Notarize and BlueNotary - no credit freezes, tried different browsers and networks. Is there a data provider hiccup or update rolling out? This keeps showing up since Tuesday. Open to ideas.

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​‍⁠‌‌⁠​‌​⁠‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‌‌‌‍‍‌‍​‍‌​‍‌‍‍‌​​‌⁠⁠‍‌⁠‌⁠‍​‌‌‌⁠​⁠‌‍‍‌​⁠​​​⁠​‍‍⁠​​‌‍‍​​⁠​‍‌⁠‌‍​‍‌‍⁠‌⁠‌‌‍⁠​‍‌​⁠‍‌​‍‌⁠​⁠​‍‌‍⁠‌‌​‌‍‍‌​⁠⁠‍‍‌​‍‌⁠‍‌​⁠‌​‌​​‍‌⁠​‌​⁠‌​‌​‍‍⁠⁠‍​​⁠‍​​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍‌⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‌⁠‌​⁠⁠‍‌⁠​‌‍‍‌​⁠‍⁠​​⁠‌‌⁠‌​‍​‌‍⁠‌⁠‍‌‌‌‌‌‌‌​‌​‍‌​⁠​‍‌‍‍‍⁠‌⁠‍‌⁠‍‌​‍‌‍⁠‍⁠​​

Sounds like provider-side latency. Grab the KBA session IDs and exact timestamps from your audit logs and send them to support so they can trace the provider timeouts; running sessions early morning cut my failures this week.

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​‍⁠‌‌⁠​‌​⁠‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‍‌‌‍‍‌‍​​​‍⁠​⁠‍‌‌‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍⁠​‍‍⁠​‍‌‍‍‍‍⁠⁠⁠‍‌​⁠‍‍‍‍‌‌‌⁠‌⁠​⁠‍⁠‍‌⁠‌⁠‍‍‌‌‍‍​​⁠​‍‌⁠‌‍​‍‌‍‍‍​‍‌⁠‌⁠​⁠‌‍‍‍‌‌‌⁠‌⁠​⁠⁠‌‌​​‌‌⁠​​​‍‌‍‍‌⁠‌⁠‍‍‌‍​‌​​⁠​‍‌⁠‌‍​‍‌‍⁠‌‌​‍​‌‍‌‌​‌‌‍​‌‌⁠‌⁠‌‌​⁠​​⁠‌​‌‌⁠‍​‍⁠​‌‌​‍‍⁠‌‌​⁠​‌‌‍‍​‍‍⁠‌‌‌‍‍⁠​‌‌‍‍‌‍‌‍‌​‌

Likely a provider hiccup - I’ve been seeing KBA timeouts since Tuesday on both platforms, and support traced mine to upstream latency. Send them the KBA session IDs with exact UTC timestamps; in the meantime, I’ve had better luck running sessions early morning or at:15/:45 past the hour.

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​‍⁠‌‌⁠​‌​⁠‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‍‌‌‍‍‌‍​​​‍⁠​⁠‍‌‌‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍⁠​‍‍⁠​‍‌‍‍‍‍⁠⁠⁠‍‌​⁠‍‍‍‍‌‌‌⁠‌⁠​⁠‍⁠‍‌⁠‌⁠‍‍‌‌‍‍​​⁠​‍‌⁠‌‍​‍‌‍‍‍​‍‌⁠‌⁠​⁠‌‍‍‍‌‌‌⁠‌⁠​⁠⁠‌‌​​‌‌⁠​‌​‍‌‍‍‌⁠‌⁠‍‍‌‍​‌​​⁠​‍‌⁠‌‍​‍‌‍⁠‍‍‍​‍‌‍​⁠‌⁠​‌‌​‍⁠‌‌‌‌‌⁠​‌‌‍‍⁠​​‌‍‍​‌‌‍⁠⁠⁠‌​​⁠‍⁠​​​⁠‍‌‍‌‌‌‍​‌⁠‍⁠⁠‍‍‌‍‌‍‌​‌