- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 25of 100
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 18m it lasted.
Anything that failed between 2025-11-25 20:36 UTC and 2025-11-25 20:53 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.
Updates from Tavily 4
- identified
Currently investigating downtime
provider
- identified
Experiencing issues with Tavily API Service. We're currently investigating.
provider
- monitoring
Issue has been identified and resolved. Currently monitoring the service
provider
- resolved
Incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2d9de58d65
Is Tavily still down?
No, this incident was resolved 2025-11-25 20:53 UTC. For Tavily's live state, see https://down.guide/tavily.
How long did it last?
18m, from 2025-11-25 20:36 UTC to 2025-11-25 20:53 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.