Relevance AI Uptime History
Measured by PulsAPI's own checks, not reported by Relevance AI. Every figure below is computed over the 90 days in the last 365 that PulsAPI actually observed, from 2026-08-08 to 2026-11-05. Days nobody watched are left out rather than counted as perfect.
Relevance AI Uptime at a Glance
- Measured uptime
- 66.20%
- Days with an issue
- 58
- Longest outage
- 88d 17h
- Mean recovery
- 73d 14h
across 90 observed days
days were not fully operational
single longest resolved incident
average time to resolve
Monthly Relevance AI Uptime
Each month is the mean of its observed days. The strongest month was November 2026 at 91.24%, the weakest October 2026 at 57.50%. Months with few observed days are marked, because a short month is not evidence of a good one.
| Month | Uptime | Uptime bar | Days observed |
|---|---|---|---|
| November 2026 | 91.24% | 5partial | |
| October 2026 | 57.50% | 31 | |
| September 2026 | 63.18% | 30 | |
| August 2026 | 76.02% | 24 |
Get an email when Relevance AI moves
Every figure on this page came from a check we ran. Those same checks can reach your inbox the moment Relevance AI stops being operational, so the next dip arrives as a notification rather than a row you find later.
Free, no password, no card. Unsubscribe in one click.
How This Relevance AI Uptime Figure Is Measured
PulsAPI checks Relevance AI continuously (every 60 seconds) and records the result. A day's uptime is the share of that day's checks that came back fully operational, so a 20-minute outage shows up as a dip rather than being rounded away. The window figure is the mean of those daily values.
Two things this deliberately is not. It is not Relevance AI's own published uptime, because vendors generally measure against their own SLA definitions, which usually exclude scheduled maintenance and often exclude partial degradation. And it is not a promise about the future: 90 days of history describes what happened, and the useful way to read it is alongside the incidents behind the dips.
Uptime measured this way is a mean of component uptimes where a vendor publishes components, so coverage matters as much as the percentage. That is why the observed-day count sits beside every figure on this page rather than in a footnote.
These measurements are published under CC BY 4.0. Quote or republish them freely, with attribution to PulsAPI.