- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 36m it lasted.
Anything that failed between 2025-09-10 16:59 UTC and 2025-09-10 17:36 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 2
- investigating
We are currently experiencing increased latency across our API endpoints. Response times may be slower than usual while we investigate and resolve this issue.Our engineering team has been notified and is actively working to identify the root cause and implement a fix. We apologize for any inconvenience this may cause.We will continue to monitor the situation closely and provide updates on this status page as more information becomes available. Thank you for your patience.
provider
- resolved
Service latency is back to normal.
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-b2a5d1ac7e
Is Tavily still down?
No, this incident was resolved 2025-09-10 17:36 UTC. For Tavily's live state, see https://down.guide/tavily.
How long did it last?
36m, from 2025-09-10 16:59 UTC to 2025-09-10 17:36 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.