Live / Spendesk / Incident
Spendesk: Strong Customer Authentication – Customers Unable to Complete Security Checks
Spendesk · spendesk.comMajor incidentResolved2026-11-03 17:24 UTC
Public — what happened
Summary
Spendesk said some customers could not complete extra security checks, which affected approving online card payments, logging in, and sensitive actions in the app. The company reported that SMS codes were not reaching some customers for roughly 45 minutes, so some actions failed or stayed pending. The issue was first posted at 12:25 UTC on 2026-11-03, and by 12:55 UTC Spendesk said the service was recovering and it was monitoring to confirm stability. It said the cause was still under investigation and advised customers to retry anything that did not complete.
Affected
Virtual Cards, Login, Physical Cards, All Payments module, Subscription Cards
Timeline
- Started — 2026-11-03 12:25 UTC
- Investigating — 2026-11-03 12:25 UTC (2 updates)
- Monitoring — 2026-11-03 12:55 UTC
- Identified — 2026-11-03 13:38 UTC
- Monitoring — 2026-11-03 16:19 UTC
- Resolved — 2026-11-03 17:24 UTC · 4h 58m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Spendesk against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Spendesk: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Spendesk report →
More from Spendesk
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.