Scalapay Outage History

6 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Scalapay Incident

Scalapay incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 26, 2026Scheduled maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.1h 0mScheduled
Oct 13, 2026Elevated ErrorsThis incident has been resolved.37 minResolved
Aug 24, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 16, 2026Elevated ErrorsThis incident has been resolved.1h 31mResolved
Apr 21, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jan 19, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Scalapay incident opens instead, at the point where knowing still changes what you do.

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

How to Read This Scalapay Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Scalapay acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Scalapay outage in this window ran 1h 31m, against a mean recovery of 1h 1m. If you depend on Scalapay in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.