Evidence · DiggingBeagle record
Perplexity Decisions API returned near-uniform decisions, first-hand support thread
Time-stamped first-hand report and provider response indicating semantically near-uniform option scores despite HTTP 200 and schema-valid response; broad outage scope unknown.
- Published
- Oct 13, 2026
- Source role
- primary disclosure
Evidence record
Time-stamped first-hand report and provider response indicating semantically near-uniform option scores despite HTTP 200 and schema-valid response; broad outage scope unknown.
Claim-level citations (3)
- supportsSchema-valid Decisions API calls returned near-uniform, unusable choice confidences: The reporter recorded semantically near-uniform choices on straightforward queries despite successful HTTP status and expected response schema.
First user report, exact product review choice scores and HTTP traces
- supportsSchema-valid Decisions API calls returned near-uniform, unusable choice confidences: Provider engineers responded on October 13 and the original reporter later described recovery; precise root cause and global blast radius were not established.
Provider response and final reporter recovery comment
- supportsSchema-valid Decisions API calls returned near-uniform, unusable choice confidences: Repeated well-formed API responses support the reporter's account of low-confidence decisions, but the public thread does not determine the number of affected customer requests or establish downstream losses.
Perplexity community bug thread #6348, reporter direct HTTP examples and engineering replies