Vectara Inc Outage History
9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Vectara Inc Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Degraded Reranking on Queries due to Capacity issuesThis incident has been resolved. | 2h 18m | Resolved |
| Sep 2, 2026 | API experiencing higher error rates.This incident has been resolved. | 34 min | Resolved |
| Jul 15, 2026 | DNS for console.vectara.com misconfiguredThis incident has been resolved. | 2 min | Resolved |
| Jul 2, 2026 | Degraded document indexingThis incident has been resolved. | 1h 22m | Resolved |
| Jun 30, 2026 | Increased Error Rates for GET Agent EventsThis incident has been resolved. | 5h 3m | Resolved |
| May 2, 2026 | Failures on Indexing DocumentsThis incident has been resolved. | 2h 15m | Resolved |
| Feb 26, 2026 | Degraded performance on queriesThis incident has been resolved. | 3h 9m | Resolved |
| Dec 1, 2025 | Queries on Newly Indexed Data are not Returning ResultsThis incident has been resolved. | 1h 9m | Resolved |
| Nov 18, 2025 | Some users are unable to loginThis incident has been resolved. | 1h 0m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Vectara Inc incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Vectara Inc Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Vectara Inc acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Vectara Inc outage in this window ran 5h 3m, against a mean recovery of 1h 52m. If you depend on Vectara Inc in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.