Spiff Outage History
8 incidents recorded over the last 365 days, 7 of them resolved, 1 still open. 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 Spiff Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 14, 2026 | UpdateWe identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information | — | Investigating |
| Sep 14, 2026 | UpdateIncident Resolved | 1h 2m | Resolved |
| Aug 24, 2026 | UpdateIncident Resolved | 21h 47m | Resolved |
| Aug 7, 2026 | UpdateCustomers who experienced a failed sync due to user mappings can start a re-sync. | 18 min | Resolved |
| Jul 10, 2026 | UpdateThe Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical… | 48 min | Resolved |
| Jul 1, 2026 | UpdateThe Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical… | 20 min | Resolved |
| Jun 18, 2026 | Degradation StartedIncident Resolved | 43 min | Resolved |
| Jun 15, 2026 | Degradation StartedIncident Resolved | 50 min | 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 Spiff 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 Spiff 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 Spiff 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 Spiff outage in this window ran 21h 47m, against a mean recovery of 3h 41m. If you depend on Spiff 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.