Skip to content
PulseWatchOUTAGE.INTEL
Spendesk logo

Finance

Is Spendesk down right now?

UnknownOfficial status last polled Sep 28, 2026 10:08 UTCspendesk.comOfficial status page

Are you on the Spendesk team and see something inaccurate? Report it to us. We respond within one business day.

Is Spendesk down right now?

Vendor-reported issue. Spendesk: Amazon Payments – Card Tokenisation Failure Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 28, 2026 10:39 UTC

UnknownVendor-reported issue

Spendesk: vendor reports an issue

As of Sep 28, 2026 10:39 UTC

Amazon Payments – Card Tokenisation Failure Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

Sep 25, 2026 11:32 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Spendesk.

12

Incident days

18

No recorded incident

192h 1m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Spendesk. Hover a day for detail.

Aug 30Sep 4Sep 9Sep 14Sep 19Sep 2401234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

12

Days with incidents

2 incidents

Busiest day

192h 1m

Recorded duration

Report volume

0 reports in last 24H

10:30 AM02:00 PM05:30 PM09:00 PM12:30 AM04:00 AM07:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Spendesk outage on September 24 — 19h 28m disruption

Sep 24, 04:04 PM → Sep 25, 11:32 AM · 19h 28m · high

Spendesk experienced a high-severity service disruption. This incident was detected through automated signals, including the vendor's own status page, starting on September 24, 2026, at 16:04 UTC. The disruption was resolved on September 25, 2026, at 11:32 UTC.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
19h 28m
until recovery

Impact

During the 19-hour and 28-minute high-severity disruption, the Spendesk service experienced an outage. This incident was detected solely through automated monitoring and the vendor's status page. No user-reported data was collected for this incident, meaning there is no information regarding specific user-visible impact on features, regions, or issue types from user reports.

Outage timeline

  1. Sep 24, 04:04 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 24, 04:04 PM

    Status updated: possible issue

  3. Sep 25, 11:32 AM

    Signals cleared — incident resolved

Official updates

  1. Sep 24, 04:04 PM

    Spendesk status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Spendesk is unknown, so there is no incident history to measure and no uptime figure is shown.

Other finance services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Spendesk: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Spendesk or have an alert rule on it can be alerted, labelled vendor-reported.

9/24/2026, 4:04:38 PM · 19h 28m

04:04 PM11:32 AM
Detection9/24/2026, 4:04:38 PM · 3d ago

Detected — high severity

Spendesk: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Spendesk or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Spendesk: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/21/2026, 3:56:04 PM · 3d 0h

03:56 PM03:57 PM
Detection9/21/2026, 3:56:04 PM · 6d ago

Detected — medium severity

Spendesk: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Spendesk: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/19/2026, 11:17:40 AM · 21h 4m

11:17 AM08:22 AM
Detection9/19/2026, 11:17:40 AM · 8d ago

Detected — medium severity

Spendesk: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Spendesk: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Spendesk or have an alert rule on it can be alerted, labelled vendor-reported.

9/16/2026, 10:08:43 AM · 3d 0h

10:08 AM10:57 AM
Detection9/16/2026, 10:08:43 AM · 12d ago

Detected — high severity

Spendesk: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Spendesk or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Spendesk incident correlated across 1 signal group: official/vendor.

9/4/2026, 11:38:28 AM · 2h 58m

11:38 AM02:37 PM
Detection9/4/2026, 11:38:28 AM · 23d ago

Detected — medium severity

Spendesk incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Spendesk enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Unknown
Monitoring
Vendor-reported issue: Amazon Payments – Card Tokenisation Failure. Affected scope is described in the vendor notice; service-wide impact is not established.
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

spendesk.com