Is Spendesk Down?

SaaSLive status, outages, and incident history

Degraded. Spendesk is up but having problems.

Spendesk is reporting degraded performance as of September 25, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · 60s while moving1 active incident

Don't find out like this next time

You searched to find out Spendesk was down. Next time we tell you, usually before your customers do, and always before you think to check.

Free, no password, no card. Unsubscribe in one click.

Official Spendesk status page

How we know: the official Spendesk status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Spendesk Component Status

3 of 23 Spendesk components are impaired. Worst problems listed first.

3degraded20operational

Cards » Physical Cards

Degraded

Cards » Subscription Cards

Degraded

Cards » Virtual Cards

Degraded

20 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Bookkeeping » Bookkeep > Export, Bookkeeping » Bookkeep > Prepare, Expense claims » Expense claims, General » All Payables module, General » All Payments module, General » Budgets, General » Email notifications, General » Login, Invoices » Invoices, Receipts » Invoice forward by email, Receipts » Receipt forward by email, Receipts » Upload receipts on payments, and 8 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Spendesk Outages & Incidents

Incident history from the official Spendesk status page, including resolution updates.

Invoices : New French E-Invoices Not ReceivedResolved Sep 22, 2026 · 19h 49mResolved

The issue affecting the delivery of new e-invoices for some customers in France was resolved at 02:56 CEST, following an approximately 18-minute interruption. The issue was caused by an update to our e-invoicing provider’s platform; all invoices have since been received, and no data loss was identified. We apologize for the disruption and thank you for your patience. --- [2026-09-22T16:46:10.993+02:00] (monitoring) We have identified the cause of the issue affecting new e-invoices for some customers in France: an update to our e-invoicing provider’s platform interrupted invoice delivery. New invoices are now being received, and we are working with the provider to confirm whether any invoices were missed and ensure they are recovered where necessary. We apologize for the inconvenience and will keep you updated on our progress. --- [2026-09-22T16:44:13.170+02:00] (monitoring) We are currently investigating an issue affecting the delivery of new e-invoices for some customers in France. Our technical team is actively investigating the situation. We sincerely apologize for any disruption this may cause and will provide updates as soon as more information is available.

The issue affecting email-link sign-in for some iOS users has been resolved. A corrected version of the mobile app is now available in the App Store; please update your app to access the fix. We apologize for the disruption and thank you for your patience. --- [2026-09-22T09:00:46.815+02:00] (identified) We have identified that the issue affecting email-link sign-in for some iOS users is related to the latest app release. We have stopped the rollout of the affected version, and a hotfix has been submitted to Apple for review. We apologize for the inconvenience and will keep you updated on our progress. --- [2026-09-21T17:14:28.346+02:00] (investigating) We are currently investigating an issue affecting some iOS users who use email and password to sign in, where login links received by email may not complete the authentication process. Our technical team is actively investigating the issue. We sincerely apologize for any disruption and will provide an update as soon as more information is available.

Amazon Payments – Card Tokenisation FailureStarted Sep 16, 2026Investigating

We are continuing to investigate an issue affecting some online card payments across multiple merchants. Transactions may be declined when the merchant does not request Strong Customer Authentication; where possible, please ask the merchant to retry using 3D Secure or use an alternative payment method. We are working with our partners to resolve the issue, apologise for the disruption, and will provide an update as soon as more information is available. --- [2026-09-21T11:56:09.409+02:00] (investigating) We are continuing to investigate an issue affecting some EEA card payments and card storage attempts at certain online merchants. Customers may experience declined transactions where additional authentication is not requested by the merchant. We are working with our banking partners to resolve the issue, apologise for the disruption, and will share a further update as soon as more information is available. --- [2026-09-17T10:09:51.454+02:00] (investigating) Our banking team is currently in contact with our banking partner Visa to investigate the root cause of this incident. We apologise for the ongoing disruption and will provide further updates as soon as more information is available. --- [2026-09-16T16:52:57.340+02:00] (investigating) We are currently investigating an issue affecting merchant card tokenisation when customers try to add Spendesk cards on Amazon. Our technical team is actively working to understand the scope and identify the cause. We sincerely apologise for any disruption this may cause and will provide an update as soon as more information is available.

Spendesk Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Spendesk incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed

Aug 8100.00% average · 12 days with incidentsSep 25

Live Spendesk Outage Reports

Problems reported by engineers using Spendesk. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Spendesk problems reported yet.

Are you seeing Spendesk problems too?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Spendesk

Spendesk publishes a public status page at status.spendesk.com covering 32 components, including Bookkeep > Prepare, Bookkeeping and Virtual Cards. PulsAPI tracks Spendesk outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Spendesk uptime at 99.83%. Response times, incident history, and SLA tracking for Spendesk are available on the PulsAPI dashboard.

Spendesk Status FAQ

Is Spendesk down right now?

The verdict at the top of this page comes from the latest poll of the official Spendesk status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Spendesk is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Spendesk recovers.

How do I check Spendesk uptime history?

PulsAPI tracks Spendesk uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.83%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Spendesk changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Spendesk outages?

PulsAPI reads the official Spendesk status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Spendesk components?

Yes. PulsAPI monitors 23 individual Spendesk components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Spendesk goes down?

Yes. Create a free account and subscribe to Spendesk: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Spendesk to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Spendesk problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Spendesk?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Spendesk plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Spendesk with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services