Tavily reported "Website maintenance" on its status page at 2025-10-22 11:22 UTC.

Tavily did not name the affected components. The updates on this page have the details.

When did the maintenance start and end?

It started at 2025-10-22 11:22 UTC. This page shows the end time when Tavily marks it resolved.

How do I get alerts for Tavily?

Subscribe to the Tavily live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Tavily. outages.live reads it every few minutes and keeps every update.

TavilyMaintenance ·

Website maintenance

MaintenanceOfficial update

This maintenance activity does not affect site availability or performance.

The latest update from Tavily.

State

Scheduled

Started

Ongoing for

377 days

Worst impact

Maintenance

Timeline

1 update

Oct 22Jan 24Apr 29Aug 1Nov 3

MaintenanceUpdate postedDates in UTC

Scheduled

377 days 100%

Updates

Times in UTC

As posted by Tavily

Scheduled

This maintenance activity does not affect site availability or performance.

Tavily in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

39 min

This incident

Not comparable

Other Tavily incidents

All incidents

Tavily·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.

Resolved

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.cc/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.cc/feed.xml?providers=tavily

Slack

/feed subscribe https://outages.cc/feed.xml?providers=tavily

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane