Triple Whale Outage History
10 incidents recorded over the last 365 days, 10 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 Triple Whale Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 2, 2026 | OpenAI Models Unavailable in MobyThis incident has been resolved. | 46 min | Resolved |
| Sep 1, 2026 | OpenAI Models Unavailable in MobyThis incident has been resolved. | 1h 28m | Resolved |
| Sep 1, 2026 | Meta Data DelayThis incident has been resolved. | 4h 46m | Resolved |
| Sep 1, 2026 | Meta Data DelayMeta has confirmed an issue on their side affecting the Insights API, which is causing delays in Meta spend data being returned to Triple Whale. Other Meta data services have remained operational. We are beginning to… | -362 min | Resolved |
| Jun 24, 2026 | Delayed Pixel Event ProcessingThis incident has been resolved. | 39 min | Resolved |
| Jun 24, 2026 | Degraded Pixel Event IngestionStatus: Resolved Date: June 24, 2026 Start Time: ~14:14 UTC End Time: ~14:29 UTC Duration: ~15 minutes Triple Whale experienced a degradation in pixel event ingestion resulting in approximately 50% of pixel events not… | -166 min | Resolved |
| Feb 18, 2026 | Temporary Attribution Page IssueThis incident has been resolved. | 1h 34m | Resolved |
| Feb 5, 2026 | Data loading issues on Summary & Pixel pagesThis incident has been resolved. | 48 min | Resolved |
| Nov 18, 2025 | Cloudfare OutageThis incident has been resolved. | 2h 11m | Resolved |
| Nov 18, 2025 | Triple Whale App OutageOur app experienced a brief outage this morning due to an external Cloudflare service issue. Downtime: 6:57 AM EST – 7:14 AM EST During this window, the app may have been inaccessible or slow to load. Cloudflare has… | -17 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 Triple Whale 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 Triple Whale 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 Triple Whale 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 Triple Whale outage in this window ran 4h 46m, against a mean recovery of 1h 45m. If you depend on Triple Whale 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.