Asynchronous transactions with degraded performance

June 24, 2026 — Asynchronous Transaction Processing Disruption

High Level Summary

On June 17, 2026 from approximately 10:02 AM to 10:41 AM UTC, Spreedly experienced a disruption affecting asynchronous gateway transactions and 3DS authentication flows. During the 39-minute window, approximately 1,634 transactions were left in a pending state without a confirmed outcome, representing less than 1% of total transaction volume during that period.

What Happened

A code deployment introduced a compatibility issue between newly deployed and previously running application instances. During a rollback process, some requests were routed across mixed code versions, causing failures when processing asynchronous transaction status updates. Affected transaction types include asynchronous gateway transactions (gateway specific 3DS, and other asyncronous verifications, authorizations, and purchases) and 3DS Global authentication. Transactions that entered the affected flow during this window may reflect an indeterminate outcome, the transaction state at your gateway may differ from what Spreedly reports.

Next Steps

We recommend reviewing transactions from the 10:02–10:41 AM UTC window on June 17 that remain in a pending state:

Verifications may be safely retried.

Authorizations should be voided at the gateway before retrying.

Purchases carry a risk of duplication, we recommend refunding before retrying.

Please reach out to Spreedly support if you need assistance identifying affected transactions or determining the appropriate remediation path. We are actively working to prevent this class of issue through improved deployment safeguards and automated rollback detection.

-The Spreedly Team