Tavily: MCP service disruption

What to do

Check whether your product depends on Tavily. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-10-08 14:15 UTC and 2025-10-08 13:05 UTC may need a replay.
Subscribe to Tavily's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=tavily works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Tavily still down?

No, this incident was resolved 2025-10-08 13:05 UTC. For Tavily's live state, see https://down.guide/tavily.

How long did it last?

0m, from 2025-10-08 14:15 UTC to 2025-10-08 13:05 UTC, by the times Tavily posted.

What caused it?

Tavily hasn't published a root cause. If it does, it shows here.

Where does this come from?

Tavily's official status page, https://status.tavily.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.