- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Vectara. 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 0m it lasted.
Anything that failed between 2024-06-25 21:42 UTC and 2024-06-25 07:00 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 1
- resolved
On of the indexing servers OOMed, due to which indexing requests going to that server failed. The OOM resulted in the server to be in a limbo state, which the liveness prober did not detect as FAILURE and hence, did not restart the server in time. This resulted in a long partial outage. Start: June 25 2024: 7:40 am UTC End: June 25 2024: 9:28 am UTC While the issue has been fixed, and a long term solution for improving the liveness prober is in progress.
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-741cf497ce
Is Vectara still down?
No, this incident was resolved 2024-06-25 07:00 UTC. For Vectara's live state, see https://down.guide/vectara.
How long did it last?
0m, from 2024-06-25 21:42 UTC to 2024-06-25 07:00 UTC, by the times Vectara posted.
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.