Spike in Unavailable transactions for 3D Secure 1.0.2 on Secure4

Resolved
Resolved

Between 1815 GMT and 1915 GMT on 03 September, Transaction Manager service experienced a problem due to which 3D Secure version 1.0.2 transactions requiring cardholders to authenticate themselves via a challenge step were failing with 3D Secure status Unavailable. The problem was found to be caused due to Transaction Manager ACS not being able to connect with callouts that make API calls to Issuer backends in order to perform certain operations for cardholder authentication flow.

Began at: