Skip to content
PulseWatchOUTAGE.INTEL
Tavily logo

Other

Is Tavily down right now?

NormalOfficial status last polled Oct 12, 2026 19:13 UTCtavily.comOfficial status page

Are you on the Tavily team and see something inaccurate? Report it to us. We respond within one business day.

Is Tavily down right now?

No. Tavily has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 20:30 UTC

Normal

Tavily is operating normally

As of Oct 12, 2026 20:30 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 19, 2026 07:43 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Tavily.

2

Incident days

28

No recorded incident

2h 48m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Tavily. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

2

Days with incidents

1 incident

Busiest day

2h 48m

Recorded duration

Report volume

0 reports in last 24H

08:30 PM12:00 AM03:30 AM07:00 AM10:30 AM02:00 PM05:30 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Tavily outage on September 19 — 47-minute disruption

Sep 19, 06:55 AM → Sep 19, 07:43 AM · 47 minutes · medium

A service disruption affected Tavily, detected by automated monitoring systems. The incident began at 2026-09-19T06:55:49.707Z and was resolved after 47 minutes, at 2026-09-19T07:43:29.279Z.

Duration
47 minutes
tracked by PulseWatch

Impact

This medium-severity incident affected Tavily for a duration of 47 minutes. During this period, automated monitoring systems indicated a disruption in service. No user-reported data was collected for this incident, and therefore no specific user-reported features, regions, or issue types can be identified.

Incident timeline

  1. Sep 19, 06:55 AM

    PulseWatch detected the incident from automated vendor and probe signals (medium severity)

  2. Sep 19, 06:55 AM

    Status updated: possible issue

  3. Sep 19, 07:43 AM

    Signals cleared — incident resolved

Official updates

  1. Sep 19, 06:55 AM

    Tavily status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the sources listed above.

Reliability

Detected by PulseWatch

30-day uptime

99.61%

90-day uptime

99.87%

Calculated from Tavily's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Tavily: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/19/2026, 6:55:49 AM · 47 min

06:55 AM07:43 AM
Detection9/19/2026, 6:55:49 AM · 23d ago

Detected — medium severity

Tavily: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Tavily: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/17/2026, 8:43:43 AM · 1h 59m

08:43 AM10:43 AM
Detection9/17/2026, 8:43:43 AM · 25d ago

Detected — medium severity

Tavily: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Tavily enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

tavily.com