- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 30of 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 0m it lasted.
Anything that failed between 2026-08-24 23:39 UTC and 2025-10-20 09:55 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 5
- investigating
We are investigating elevated error rates on the Perplexity website.
provider
- identified
We are experiencing an outage related to an AWS operational issue. [https://health.aws.amazon.com/health/status.](https://health.aws.amazon.com/health/status) We are continuing to work on a fix for this incident.
provider
- identified
We can confirm this is related to an AWS service disruption. We are actively working with AWS on a resolution. We will continue to update this page.
provider
- monitoring
Most services are operational now, we are continuing to monitor
provider
- resolved
This incident has now been resolved.
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-2888d248ab
Is Perplexity still down?
No, this incident was resolved 2025-10-20 09:55 UTC. For Perplexity's live state, see https://down.guide/perplexity.
How long did it last?
0m, from 2026-08-24 23:39 UTC to 2025-10-20 09:55 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.