Resolved
Resolved
After 5 hours and 44 minutes

We confirm that our 3D Secure success rates continue to be stable. Our teams will continue to monitor the transactions closely and with this update, we confirm that this incident stands resolved.

If you have any questions regarding this Service Advisory, please contact Broadcom Support by clicking here.

Monitoring
After 5 hours and 6 minutes

We observe that transaction processing has recovered and success rates have been stable for some time. We continue to monitor and watch the series closely and we shall get back to you with the next update by 19:30 GMT.

Investigating
After 4 hours and 31 minutes

Our internal teams continue to focus on service recovery and configuration changes are being made for our internal components to ensure that our transaction processing server is able to process transactions without a high failure rate.

We shall get back to you with the next update by 18:30 GMT.

Investigating
After 3 hours and 24 minutes

Our teams continue to work on a service restoration plan on priority and as a part of this plan, there are changes being made to the configurations of our internal components. We shall get back to you with the next status update by 17:30 GMT.

Investigating
After 2 hours and 29 minutes

Our internal team continues to work on high priority to change certain configurations of our internal components responsible for connections between our transaction processing server and our database. The impact of the present incident continues to be that a high number of 3-DSecure transactions failing with status Unavailable. This incident continues to impact both 1.x and EMV3DS transactions.

We shall get back to you with the next status update by 16:30 GMT.

Investigating
After 1 hour and 20 minutes

Further investigation has revealed that the problem has been identified with the connections between our transaction processing servers and our database. Our internal team is working on a plan to restore these connections and we shall get back to you with the next update by 15:30 GMT.

Investigating
After 28 minutes

At the present time, we confirm that a certain percentage of transactions are getting failed with status Unavailable. We are continuing to investigate the present issue with high priority and our internal teams are working to restore the service. We shall get back to you with the next update by 14:30 GMT.

Investigating

We are observing and increase in failures due to transaction status Unavailable (U). Incident call has been initiated and teams are working on service recovery.

We will keep you posted on the recovery progress. Next update due at: 13:40 GMT, 20 October

Began at:

Affected components
  • Arcot
    • Arcot for Issuers (AfI)
      • Secure2
      • SecureF
      • Secure4
      • Secure7
      • Secure5
      • SecureT