Vectara
Service Reliability
Dependable
As of September 3, 2026, Vectara's reliability: The public status page shows 99.99% uptime over 90 days with one incident, and current status is operational. That observed track record is short but clean, and the public page means a buyer can monitor it independently rather than taking the vendor's word.
Backed by 4 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Every value derives from a dated, sourced capture — open any fact for its source.
Details
Uptime (90d)99.99%
Incidents (90d)1
Current statusoperational
Reliability Change Historydated events · values unlock with a key
Reliability changed: Status Page Url
Reliability changed: Uptime 90d
Reliability changed: Incidents 90d
Reliability changed: Uptime 90d
Reliability changed: Incidents 90d
Reliability changed: Uptime 90d
Reliability changed: Incidents 90d
Reliability changed: Status · high significance
Every reliability fact on this pagekey · value · provenance · dated · sourced
| Fact | Value | Provenance | As of | Source |
|---|---|---|---|---|
| reliability.incidents_90d | 1 | company stated | 2026-09-03 | status.vectara.com |
| reliability.status | operational | company stated | 2026-09-03 | status.vectara.com |
| reliability.status_page_url | https://status.vectara.com/ | company stated | 2026-09-03 | status.vectara.com |
| reliability.uptime_90d | 99.99 pct | company stated | 2026-09-03 | status.vectara.com |
Reliability across Vector DatabasesVectara ranked in place · tap through for each read
| Company | Reliability read | Facts |
|---|---|---|
| Pinecone | Dependable | 4 |
| Vectara this record | Dependable | 4 |
| Chroma | Dependable | 3 |
| TopK | Operational | 2 |
| Turbopuffer | Operational | 2 |
| Epsilla | Dependable | 1 |
| Weaviate | Dependable | 1 |
| Zilliz | Dependable | 1 |
No observed reliability facts yet for Activeloop, KDB.AI, LanceDB, Marqo, Milvus, MyScale, Qdrant and Vespa.
Get reliability for vectara.com via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/vectara.com/facts?dimension=reliability
{
"data": {
"facts": [
{
"key": "reliability.incidents_90d",
"value": 1,
"provenance": "company_stated",
"as_of": "2026-09-03",
"source_url": "status.vectara.com"
},
{
"key": "reliability.status",
"value": "operational",
"provenance": "company_stated",
"as_of": "2026-09-03",
"source_url": "status.vectara.com"
},
{
"key": "reliability.status_page_url",
"value": "https://status.vectara.com/",
"provenance": "company_stated",
"as_of": "2026-09-03",
"source_url": "status.vectara.com"
},
{
"key": "reliability.uptime_90d",
"value": 99.99,
"provenance": "company_stated",
"as_of": "2026-09-03",
"source_url": "status.vectara.com"
},
"…"
]
}
}MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "vectara.com", dimension: "reliability" })
# returns the reliability record above,
# each value with its source_url + as_of,
# ready to reason overBuild on the company record. One key, REST + MCP, every signal dated and sourced back to the page it came from.
Public record, read from companies' own pages and boards. Every fact dated and sourced; provenance (observed vs company stated) shown inline.