- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 100
What to do
Check whether your product depends on Perplexity. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 37m it lasted.
Anything that failed between 2026-10-09 22:38 UTC and 2026-10-09 23:15 UTC may need a replay.Subscribe to Perplexity's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=perplexity works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Perplexity 4
- investigating
Users may experience errors or timeouts when making API requests. We are investigating elevated API errors and timeouts.
provider
- monitoring
The issue causing elevated API errors and timeouts has been mitigated.
provider
- monitoring
Correction to our previous updates: we do not believe the API was affected by this incident and it remains operational.
provider
- resolved
The issue affecting the Website, App, and Computer has been resolved. All services are operational. The API remained operational throughout this incident.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-4b77187947
Is Perplexity still down?
No, this incident was resolved 2026-10-09 23:15 UTC. For Perplexity's live state, see https://down.guide/perplexity.
How long did it last?
37m, from 2026-10-09 22:38 UTC to 2026-10-09 23:15 UTC, by the times Perplexity posted.
What caused it?
Perplexity hasn't published a root cause. If it does, it shows here.
Where does this come from?
Perplexity's official status page, https://status.perplexity.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.