- Level
- confirmed
- Worst impact
- Major outage
- Components
- Admin, Console, Index, Query, Chat, Document
- Down Index
- 59of 100
What to do
Check whether you use Vectara Admin, Console, Index, Query and 2 more. 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 54m it lasted.
Anything that failed between 2025-03-28 17:34 UTC and 2025-03-28 18:28 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
- investigating
We are seeing many API requests fail, and are actively seeking a fix.
provider
- monitoring
We have identified the issue; a bad routing configuration got rolled out. The issue should be resolved, and we are monitoring the situation. We will be doing and publishing a post mortem.
provider
- resolved
Services should be back to normal now, we will conduct a postmortem.
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-9d5931eebc
Is Vectara still down?
No, this incident was resolved 2025-03-28 18:28 UTC. For Vectara's live state, see https://down.guide/vectara.
How long did it last?
54m, from 2025-03-28 17:34 UTC to 2025-03-28 18:28 UTC, by the times Vectara posted.
What was affected?
Vectara named Admin, Console, Index, Query and 2 more.
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.