Privacy Outage History
4 incidents recorded over the last 365 days, 4 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 Privacy Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Apr 22, 2026 | Everywhere Card tokenization issueThis incident has been resolved. | 1h 7m | Resolved |
| Feb 17, 2026 | Unexpected declines on newly created cardsWe detected an issue that caused unexpected declines on cards that were created between 2026-02-17 17:05 UTC (12:05pm ET) and 2026-02-17 17:53 UTC (12:53pm ET). The issue has been resolved, and cards created during that… | 0 min | Resolved |
| Dec 16, 2025 | Transacting processing issues for select cards between 2025-12-16 20:05 and 20:25 UTCCards created between 20:05 and 20:25 UTC (3:05pm to 3:25pm ET) were unable to transact. This issue was resolved at 20:25 UTC (3:25pm ET) and card transactions are working as expect. Previous transaction attempts on… | 0 min | Resolved |
| Nov 11, 2025 | Investigating unexpected declinesNormal transaction processing has resumed. Thank you for your patience. | 5h 47m | 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 Privacy 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 Privacy 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 Privacy 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 Privacy outage in this window ran 5h 47m, against a mean recovery of 1h 44m. If you depend on Privacy 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.