Live  /  Perplexity  /  Incident

Perplexity: Elevated API errors and timeouts

Perplexity · perplexity.aiMinor incidentResolved2026-10-09 23:15 UTC
Public — what happened

Summary

Perplexity reported a minor incident on October 9, 2026, starting at 22:38 UTC, saying people using its API might run into failed requests or requests that took too long to respond. By 23:01 UTC the company said the problem had been mitigated and it was watching the situation. At 23:10 UTC Perplexity issued a correction, stating it did not believe the API had actually been affected and that it stayed operational. The incident was marked resolved at 23:15, and the company did not name a cause.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Perplexity against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Perplexity: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Perplexity report →

More from Perplexity

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Perplexity status & history page.

Related: Perplexity status & history. SquidGrid is not affiliated with Perplexity.