Pledge It Outage History
3 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 Pledge It Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 2, 2026 | Site slow-down and increased errorsThis incident has been resolved. | 13 min | Resolved |
| Sep 10, 2026 | Users seeing 500 errors across all sitesThis incident has been resolved. | 29 min | Resolved |
| Aug 18, 2026 | Increased error rates on Pledge It siteThis incident has been resolved. | 1h 39m | 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 Pledge It 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 Pledge It 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 Pledge It 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 Pledge It outage in this window ran 1h 39m, against a mean recovery of 47 min. If you depend on Pledge It 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.