PartnerStack Outage History
5 incidents recorded over the last 365 days, 5 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 PartnerStack Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 15, 2026 | Scheduled MaintenanceMaintenance has started | 48 min | Resolved |
| Jun 1, 2026 | API and dashboards outageAll services are fully restored and operating normally. | -5529 min | Resolved |
| Feb 18, 2026 | [Resolved] Link-Based Attribution Tracking IssueWe have resolved the incident affecting link-based attribution. The issue was traced back to a misconfiguration in how our static JavaScript tracking snippets were hosted during a recent update. This prevented the… | -102 min | Resolved |
| Feb 4, 2026 | Customer attributions not being processedThere is an issue with our customer attribution processing - errors are causing attribution events to be put back into the queue, and are then being lost (but recoverable) after 24 hours. | -116032 min | Resolved |
| Dec 5, 2025 | Several Failures due to Cloudflare System OutageThe incident has been resolved. And our systems are now fully operational. | 13 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 PartnerStack 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 PartnerStack 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 PartnerStack 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 PartnerStack outage in this window ran 48 min, against a mean recovery of 31 min. If you depend on PartnerStack 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.