Turbopuffer
Service Reliability
Operational
As of September 24, 2026, Turbopuffer's reliability: A public status page exists and shows operational at time of observation; no public uptime history or SLA percentage is visible, so buyers cannot independently verify historical availability before committing.
Backed by 2 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
Current statusoperational
Reliability Change Historydated events · values unlock with a key
Reliability changed: Status Page Url
Reliability changed: Uptime 90d · high significance
Reliability changed: Uptime 90d
Reliability changed: Uptime 90d
Every reliability fact on this pagekey · value · provenance · dated · sourced
| Fact | Value | Provenance | As of | Source |
|---|---|---|---|---|
| reliability.status | operational | company stated | 2026-09-24 | status.turbopuffer.com |
| reliability.status_page_url | https://status.turbopuffer.com/ | company stated | 2026-09-24 | status.turbopuffer.com |
Reliability across Vector DatabasesTurbopuffer ranked in place · tap through for each read
| Company | Reliability read | Facts |
|---|---|---|
| Chroma | Dependable | 3 |
| Pinecone | Operational | 3 |
| Vectara | Operational | 3 |
| TopK | Operational | 2 |
| Turbopuffer this record | 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.
IdentityBixel ID · free forever
Operated by
No registered company joined yet. Would resolve with: a registry identifier for the entity; a legal page on the site naming the registered company.
Registry identifiers
None on record.
Published identifiers
None read from the company's own pages yet.
Get reliability for turbopuffer.com via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/turbopuffer.com/facts?dimension=reliability
{
"data": {
"facts": [
{
"key": "reliability.status",
"value": "operational",
"provenance": "company_stated",
"as_of": "2026-09-24",
"source_url": "status.turbopuffer.com"
},
{
"key": "reliability.status_page_url",
"value": "https://status.turbopuffer.com/",
"provenance": "company_stated",
"as_of": "2026-09-24",
"source_url": "status.turbopuffer.com"
},
"…"
]
}
}MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "turbopuffer.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.