Relevance AI 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 Relevance AI Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 9, 2026 | Customers are unable to save triggers when creating workforces | 1350h 32m | Resolved |
| Aug 4, 2026 | Degraded Claude Sonnet 5 service | 2129h 20m | Resolved |
| Jul 22, 2026 | Users aren't receiving email verification and password reset emails | 1701h 30m | Resolved |
| Jul 20, 2026 | Existing agents do not show tools and prompts in some projects | 1747h 17m | Resolved |
| Jul 13, 2026 | We are currently experiencing issues with cross project agent cloning | 1896h 30m | Resolved |
| Jun 19, 2026 | Trigger Visibility Issue in Platform UI | 1773h 59m | 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 Relevance AI 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 Relevance AI 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 Relevance AI 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 Relevance AI outage in this window ran 88d 17h, against a mean recovery of 73d 14h. If you depend on Relevance AI 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.