Perplexity: Elevated API errors and timeouts
AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents
Perplexity’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +5 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
root --> h1
later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
root --> later
me["Perplexity (this incident)<br/>posted +5 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: WebsiteAppComputer
Timeline of updates
- investigating
Users may experience errors or timeouts when making API requests. We are investigating elevated API errors and timeouts.
- monitoring
The issue causing elevated API errors and timeouts has been mitigated.
- monitoring
Correction to our previous updates: we do not believe the API was affected by this incident and it remains operational.
- resolved
The issue affecting the Website, App, and Computer has been resolved. All services are operational. The API remained operational throughout this incident.
Impact, status and times are the vendor’s own, as last archived. View on status.perplexity.com (opens in new tab).