Spendesk Status
System status
Incident overview
Total incidents
13
Active now
0
Resolved
13
Avg. resolution
82h 18m
Recent incidents
View all →Strong Customer Authentication – Customers Unable to Complete Security Checks
Subscription Cards – Card Details Unavailable
Invoices – E-Invoices Not Received
3DS Authentication – Notifications Not Received on iOS
Login – Users Unable to Sign In
Invoices : New French E-Invoices Not Received
Login : iOS Email Links Not Completing Sign-In
Amazon Payments – Card Tokenisation Failure
International Transfers feature is unavailable for affected EEA customers
Third-Party Service Disruption : Email Notifications – Microsoft Service Disruption
Frequently asked questions
Is Spendesk down right now?
Spendesk is currently operational. DevHelm monitors Spendesk's official status page continuously and updates this page every 5 minutes.
What is Spendesk's current uptime?
Spendesk has a measured 30-day uptime of 99.97%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 99.88%. These figures are computed from Spendesk's official status page data.
How many incidents has Spendesk had recently?
Spendesk has experienced 13 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 82h 18m. All incidents are currently resolved.
What components does Spendesk monitor?
DevHelm tracks 23 individual components for Spendesk, including Invoices, Bookkeep > Prepare, Requests, Virtual Cards, Settings, and 18 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Spendesk outages?
You can subscribe to Spendesk's incident feed via Atom/RSS at devhelm.io/status/spendesk/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Spendesk as a dependency in your DevHelm workspace.
About Spendesk status monitoring
This page provides real-time operational status for Spendesk, powered by DevHelm's continuous monitoring infrastructure. We track Spendesk's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Spendesk status data is refreshed every 5 minutes. We currently track 23 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Spendesk in your stack
Get alerted when Spendesk has issues — before your users notice. Set up in 30 seconds.