Tavily outage history
We hold 10 Tavily incidents from Tavily's status page, the newest from Sep 19, 2026. 9 of the 10 listed carry Tavily's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.
Uptime & history
Tracking since Jun 22, 2026% of our checks that found Tavily fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.
- salesforce->dwh transfer stuckSep 19, 2026 · ongoing · resolved
- Tavily website degraded performanceSep 17, 2026 → Sep 17, 2026 · resolved
- Status DegradedNov 25, 2025 → Nov 25, 2025 · resolved
- Service DegradedOct 20, 2025 → Oct 20, 2025 · resolved
- Service DegradedOct 20, 2025 → Oct 20, 2025 · resolved
- MCP service disruptionOct 8, 2025 → Oct 8, 2025 · resolved
- Service Latency IncreasedSep 10, 2025 → Sep 10, 2025 · resolved
- MCP service disruptionSep 6, 2025 → Sep 2, 2025 · resolved
- Minor Result Quality ReductionAug 14, 2025 → Aug 14, 2025 · resolved
- API service disruptionAug 5, 2025 → Aug 5, 2025 · resolved
How Tavily fails
Since Sep 17, 2026, Tavily's status page has marked 2 Tavily components as impaired, across 10 of our five-minute readings. Tavily Website accounts for the most: 8 readings (40 minutes) on 1 day, most recently on Sep 17, 2026. Next is Tavily API Service, with 2 readings on 1 day. We hold 10 Tavily incidents from Tavily's status page, the earliest from Aug 5, 2025. Of the 7 that Tavily closed with an end time, the median lasted 36 minutes.
| Component | Outage | Degraded | Maint. | Days | Last |
|---|---|---|---|---|---|
| Tavily Website | — | 8 | — | 1 | Sep 17, 2026 |
| Tavily API Service | — | 2 | — | 1 | Sep 19, 2026 |
Incidents by month: Aug 2025: 2 · Sep 2025: 2 · Oct 2025: 3 · Nov 2025: 1 · Sep 2026: 2
Counts are five-minute readings of Tavily's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.
Every recorded incident
September 2026 · 2
- Sep 19, 2026salesforce->dwh transfer stuckminorend not published
- Sep 17, 2026Tavily website degraded performance minor39 min2 updates
November 2025 · 1
- Nov 25, 2025Status Degradedmajor18 min4 updates
October 2025 · 3
- Oct 20, 2025Service Degradedminor4 h 39 min2 updates
- Oct 20, 2025Service Degradedminor3 h 34 min4 updates
- Oct 8, 2025MCP service disruptionminor—1 update
September 2025 · 2
- Sep 10, 2025Service Latency Increasedminor36 min2 updates
- Sep 6, 2025MCP service disruptionminor—1 update
August 2025 · 2
- Aug 14, 2025Minor Result Quality Reductionminor21 min3 updates
- Aug 5, 2025API service disruptionminor6 min3 updates
Incidents and their updates are Tavily's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Tavily.