Profound Outage History
6 incidents recorded over the last 365 days, 3 of them resolved, 3 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 Profound Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Perplexity has returned to normal | 12h 59m | Resolved |
| Oct 28, 2026 | AI Overviews are impacted | — | Investigating |
| Oct 7, 2026 | Data Quality and Delays affecting Perplexity data | — | Investigating |
| Sep 24, 2026 | Perplexity and AI Overviews are impacted | 993h 49m | Resolved |
| Sep 18, 2026 | Service availability issues | 1136h 17m | Resolved |
| Sep 2, 2026 | Google AI Mode citations are affected | — | Investigating |
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 Profound 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 Profound 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 Profound 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 Profound outage in this window ran 47d 8h, against a mean recovery of 29d 18h. If you depend on Profound 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.