We started checking Spendesk on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Spendesk reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Spendesk's own status page declared. Below it, any public chatter we saw about Spendesk and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Spendesk's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Spendesk in the last 24 hours, which is not evidence that nothing is wrong.
Spendesk's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Spendesk's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Spendesk next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
158
US-West
100.00%
125
Europe
100.00%
113
Asia-Pacific
100.00%
71
Their declared record
Spendesk's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Nov 3, 2026, 12:25 PM UTC to Nov 3, 2026, 5:24 PM UTC (4h 58m)resolved
their latest update (Nov 3, 2026, 5:24 PM UTC): The issue affecting SMS verification codes, login attempts, payment approvals, and other sensitive actions has been fully resolved as of 18:17 CET. We apologize for the disruption and thank you for your patience while we monitored the service.
Oct 26, 2026, 10:44 AM UTC to Oct 29, 2026, 11:38 AM UTC (3d 0h)resolved
their latest update (Oct 29, 2026, 11:38 AM UTC): This incident has been resolved.
Invoices – E-Invoices Not ReceivedMinor incident
Oct 15, 2026, 6:20 AM UTC to Oct 15, 2026, 6:47 AM UTC (27 min)resolved
their latest update (Oct 15, 2026, 6:47 AM UTC): The issue preventing e-invoices from being received has been fully resolved as of 18:18 yesterday, after approximately 1 hour and 37 minutes of impact. We apologize for the disruption and thank you for your patience.
3DS Authentication – Notifications Not Received on iOSMinor incident
Oct 7, 2026, 9:13 AM UTC to Oct 23, 2026, 12:36 PM UTC (16d 3h)resolved
their latest update (Oct 23, 2026, 12:36 PM UTC): This incident has been resolved.
Login – Users Unable to Sign InMajor outage
Sep 29, 2026, 3:57 PM UTC to Sep 30, 2026, 7:17 AM UTC (15h 20m)resolved
their latest update (Sep 30, 2026, 7:17 AM UTC): The issue preventing users from signing in to the Spendesk application was fully resolved at 6:49 PM CEST on 29 September, after approximately 59 minutes. We apologize for the disruption and thank you for your patience.
Invoices : New French E-Invoices Not ReceivedMinor incident
Sep 22, 2026, 2:44 PM UTC to Sep 23, 2026, 10:34 AM UTC (19h 50m)resolved
their latest update (Sep 23, 2026, 10:34 AM UTC): 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 d…
Login : iOS Email Links Not Completing Sign-InMinor incident
Sep 21, 2026, 3:14 PM UTC to Sep 23, 2026, 7:20 AM UTC (1d 16h)resolved
their latest update (Sep 23, 2026, 7:20 AM UTC): 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.
Sep 16, 2026, 2:52 PM UTC to Oct 7, 2026, 9:09 AM UTC (20d 18h)resolved
their latest update (Oct 7, 2026, 9:09 AM UTC): This incident has been resolved.
International Transfers feature is unavailable for affected EEA customersMajor outage
Sep 16, 2026, 10:05 AM UTC to Sep 17, 2026, 8:06 AM UTC (22h)resolved
their latest update (Sep 17, 2026, 8:06 AM UTC): The issue affecting EEA International Transfers and other Wise operations is now fully resolved. We apologize for the disruption and thank you for your patience.
Third-Party Service Disruption : Email Notifications – Microsoft Service DisruptionPartial outage
Sep 4, 2026, 11:10 AM UTC to Sep 4, 2026, 2:03 PM UTC (2h 53m)resolved
their latest update (Sep 4, 2026, 2:03 PM UTC): The issue affecting email delivery to Microsoft-hosted mailboxes was fully resolved as of [time]. During the incident, some emails and Spendesk features relying on Microsoft’s services may have been affected. We apologize for the inconvenience and thank you for your patience.
Showing the 10 most recent of 51 incidents Spendesk has declared in the history we hold.
These entries are Spendesk's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Spendesk's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.