Signifyd Outage History
6 incidents recorded over the last 365 days, 6 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 Signifyd Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 10, 2026 | API Server ErrorsWe experienced intermittent "API Server Errors" when orders were being sent to Signifyd from 12:20 to 12:25 UTC. This issue has now been resolved. Should you have any other questions, please contact us via the support… | 0 min | Resolved |
| Aug 13, 2026 | Webhook Processing DelaysAll webhooks are being processed. You will notice a delay in responses while we process the order backlog. Should you have any questions, please contact us via the support portal: signifyd.com/support Operational: -… | 46 min | Resolved |
| Aug 3, 2026 | API Server ErrorsThe "API Server Errors" issue has been resolved. All orders impacted by this incident should now have processed to Signifyd. Should you have any other questions, please contact us via the support portal… | 2h 56m | Resolved |
| Jul 15, 2026 | API Server ErrorsSignifyd experienced an intermittent "API Server Errors" when orders/login requests were being sent to Signifyd. Our engineering team is investigating the root cause and putting safeguards in place to prevent a… | -201 min | Resolved |
| Jun 18, 2026 | API Server ErrorsWe are experiencing intermittent "API Server Errors" when orders are being sent to Signifyd. We are investigating the issue and will update the status page once additional information is available. Should you… | -198 min | Resolved |
| Apr 14, 2026 | Order Review Processing Delay All ClearAll submitted orders are now being processed successfully and queued for a decision, but you may notice a delay in responses while we are processing the orders backlog. Should you have any questions, please contact us… | -58 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 Signifyd 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 Signifyd 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 Signifyd 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 Signifyd outage in this window ran 2h 56m, against a mean recovery of 1h 14m. If you depend on Signifyd 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.