">
sevanalysis

Tavily

AI. Source: Tavily status page.

Incidents, last 90 days
1
Median to mitigation
39m
Median to resolution
39m
p95 to resolution
39m
Naming an upstream provider
0%
With a postmortem on the status page
0%

What failed, last 90 days

The text does not say enough to tell1

Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.

Incidents per month

All recorded incidents

Tavily website degraded performance minor 2026-09-17 08:40 UTC 39m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We’re currently experiencing issues with our web platform at [app.tavily.com](http://app.tavily.com). Our team is actively investigating and working to restore normal service. We’ll share updates as we learn more.

  2. resolved

    We’ve identified the root cause, deployed a fix, and verified that [app.tavily.com](http://app.tavily.com) is back to normal.

Excerpts are shortened. Read the full incident on Tavily's status page.

Status Degraded major 2025-11-25 20:36 UTC 18m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. identified

    Currently investigating downtime

  2. identified

    Experiencing issues with Tavily API Service. We're currently investigating.

  3. monitoring

    Issue has been identified and resolved. Currently monitoring the service

  4. resolved

    Incident has been resolved.

Excerpts are shortened. Read the full incident on Tavily's status page.

Service Degraded minor 2025-10-20 15:27 UTC 4h 39m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    Some features may be slower or partially unavailable. The issue related to an AWS regional outage.

  2. resolved

    The recent AWS outage has been fully resolved. All systems are now stable and operating normally.

Excerpts are shortened. Read the full incident on Tavily's status page.

Service Degraded minor 2025-10-20 07:21 UTC 3h 34m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    Some features may be slower or partially unavailable. Our team is investigating the issue.

  2. identified

    The issue appears to be related to an AWS regional outage.

  3. monitoring

    We are seeing significant signs of recovery. Most requests should now be succeeding.

  4. resolved

    The issue has been resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Tavily's status page.

MCP service disruption minor 2025-10-08 14:15 UTC -70m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. resolved

    MCP service disruption

Excerpts are shortened. Read the full incident on Tavily's status page.

Service Latency Increased minor 2025-09-10 16:59 UTC 36m

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently experiencing increased latency across our API endpoints. Response times may be slower than usual while we investigate and resolve this issue.Our engineering team has been notified and is actively working to identify the root cause and implement a fix. We...

  2. resolved

    Service latency is back to normal.

Excerpts are shortened. Read the full incident on Tavily's status page.

MCP service disruption minor 2025-09-06 12:21 UTC -5781m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. resolved

    MCP service disruption

Excerpts are shortened. Read the full incident on Tavily's status page.

Minor Result Quality Reduction minor 2025-08-14 20:47 UTC 21m

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. identified

    Minor reduction in quality of results when using include_domains parameter

  2. identified

    Minor reduction in quality of results when using include_domains parameter

  3. resolved

    Result quality has returned to normal

Excerpts are shortened. Read the full incident on Tavily's status page.

API service disruption minor 2025-08-05 12:57 UTC 6m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. identified

    API experiencing intermittent failures and timeouts.

  2. identified

    API experiencing intermittent failures and timeouts.

  3. resolved

    Only for Crawl endpoint (Beta)

Excerpts are shortened. Read the full incident on Tavily's status page.