Tavily website degraded performance
We’ve identified the root cause, deployed a fix, and verified that [app.tavily.com](http://app.tavily.com) is back to normal.
The latest update from Tavily.
State
Resolved
Started
Lasted
39 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
39 min 100%
Updates
Times in UTCAs posted by Tavily
We’ve identified the root cause, deployed a fix, and verified that [app.tavily.com](http://app.tavily.com) is back to normal.
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.
Tavily in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
39 min
This incident
About the median
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.
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.
https://outages.live/feed.xml?providers=tavily/feed subscribe https://outages.live/feed.xml?providers=tavilyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane