Scratchpay Outage History
8 incidents recorded over the last 365 days, 3 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 Scratchpay Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 1, 2026 | scratchpay.com is downWe have resolved the issue and traced the root-cause to an issue from our cloud provider - https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev. | 56 min | Resolved |
| Apr 24, 2026 | Scratch Maintenance - LoansMaintenance completed. | 1h 0m | Scheduled |
| Apr 14, 2026 | Scratch Maintenance - LoansScratch internal team has confirmed all services are fully functional. | 3h 0m | Scheduled |
| Mar 31, 2026 | Scratch Maintenance - LoansThe internal team has confirmed all services are functioning as expected. The maintenance is completed. | 1h 0m | Scheduled |
| Mar 24, 2026 | Scratch Maintenance - LoansThe internal team has confirmed all systems are functioning as expected. | 3h 0m | Scheduled |
| Mar 3, 2026 | Scratch MaintenanceScratch maintenance has been successfully completed and the internal teams confirmed all services are functioning effectively. | 1h 0m | Scheduled |
| Feb 16, 2026 | scratchpay.com is currently experiencing an outageOur internal team has confirmed the scratchpay.com service is fully restored. | 55 min | Resolved |
| Nov 18, 2025 | Severely restricted availability of all servicesThis incident has been resolved. | 4h 3m | Resolved |
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 Scratchpay 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 Scratchpay 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 Scratchpay 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 Scratchpay outage in this window ran 4h 3m, against a mean recovery of 1h 52m. If you depend on Scratchpay 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.