PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if SumUp is down?

PulseWatch evaluates user reports and replay-approved automated evidence for SumUp. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported SumUp issues today?

As of Oct 8, 2026 19:26 UTC, 0 users had reported issues with SumUp in the previous 24 hours.

How can I report a SumUp outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Finance

Is SumUp down right now?

NormalOfficial status last polled Oct 8, 2026 19:13 UTCwww.sumup.com Official status page

A major European fintech providing payment processing and business banking solutions for small merchants.

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

Is SumUp down right now?

No. SumUp has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 8, 2026 19:26 UTC

Normal

SumUp is operating normally

As of Oct 8, 2026 19:26 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 16, 2026 12:16 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

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 SumUp.

Incident days

No recorded incident

50 min

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 SumUp. Hover a day for detail.

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

Days with incidents

1 incident

Busiest day

50 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

SumUp outage on September 16 — 50 minutes disruption

Sep 16, 11:25 AM → Sep 16, 12:16 PM · 50 minutes · high

On September 16, SumUp experienced a major-impact incident. This disruption was detected by PulseWatch through the vendor's status page. The incident was resolved at 12:16 PM UTC on September 16, 2026.

Duration

50 minutes

tracked by PulseWatch

Impact

During the 50-minute high-severity incident affecting SumUp, service availability was impacted. This disruption was identified through automated monitoring signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore, specific user-visible impacts such as affected features, regions, or issue types could not be determined from user reports.

Incident timeline

Sep 16, 11:25 AM
PulseWatch detected the incident from automated vendor and probe signals (high severity)
Sep 16, 11:25 AM
Status updated: possible issue
Sep 16, 12:16 PM
Signals cleared — incident resolved

Official updates

Sep 16, 11:25 AM
SumUp status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.88%

90-day uptime

96.5%

Calculated from SumUp's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

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.

Be the first to post a report.

Incident timeline

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

Full history →

ResolvedHigh

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

9/16/2026, 11:25:47 AM · 50 min

11:25 AM12:16 PM

Detection9/16/2026, 11:25:47 AM · 22d ago

Detected — high severity

ResolvedMedium