Tremendous Outage History
5 incidents recorded over the last 365 days, 3 of them resolved, 2 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 Tremendous Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | Fulfillment delays for international prepaid cards | — | Investigating |
| Oct 23, 2026 | Fulfillment delays for US and international gift cards | — | Investigating |
| Oct 19, 2026 | Issues with Virtual Visa transaction notifications | 46h 29m | Resolved |
| Aug 12, 2026 | Fulfillment delays for USA gift cards | 8h 28m | Resolved |
| Jul 24, 2026 | Delays adding some Visa cards to digital wallets | 1642h 24m | 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 Tremendous 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 Tremendous 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 Tremendous 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 Tremendous outage in this window ran 68d 10h, against a mean recovery of 23d 13h. If you depend on Tremendous 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.