outages.live
Live

Tavily

Tavily is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Tavily status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Tavily since . The days before that show only what Tavily published.

Incidents in 90 days

1

Days with an incident

1

Median duration

39 min

Longest incident

39 min

Components

3
Tavily API Service Operational
90 days agoNo incidentsToday
Tavily MCP Operational
90 days agoNo incidentsToday
Tavily Website Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 17, 2026

Duration39 min to Tavily website degraded performanceDegraded

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

Maintenance

Website maintenance

This maintenance activity does not affect site availability or performance.

Maintenance

Follow Tavily

Your coding agent knows when Tavily is down, and tells you when a failure is theirs, not yours. You can also get Tavily incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "tavily" and tell me if Tavily has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=tavily
Slack
/feed subscribe https://outages.live/feed.xml?providers=tavily

Go from tracking outages to fixing production issues with Polylane.

Try Polylane