Skip to main content
Vectara

Degraded Reranking on Queries due to Capacity issues

Partial outage Lasted 2h 18m · started · Vectara's page

Level
confirmed
Worst impact
Partial outage
Components
Query
Down Index
32of 100

What to do

  • Check whether you use Vectara Query. 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 2h 18m it lasted.

    Anything that failed between 2026-11-03 21:50 UTC and 2026-11-04 00:09 UTC may need a replay.
  • Subscribe to Vectara's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=vectara works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vectara 3

  1. identified

    Queries with default Multilingual Rerankers have increased error rates on some. Cloud provider GPU availability is causing scheduling issues, we are working on resolving capacity.

    provider

  2. monitoring

    We are monitoring the fix, error rates are back to normal.

    provider

  3. resolved

    This 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-a93e9f2a8d

Is Vectara still down?

No, this incident was resolved 2026-11-04 00:09 UTC. For Vectara's live state, see https://down.guide/vectara.

How long did it last?

2h 18m, from 2026-11-03 21:50 UTC to 2026-11-04 00:09 UTC, by the times Vectara posted.

What was affected?

Vectara named Query.

What caused it?

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

Where does this come from?

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