We have identified few connectors that are impacting users.
Timeline · 1 update
- resolved Sep 05, 2026, 07:09 AM UTC
Status: Resolved This incident has been resolved.
Perplexity Outage History
Perplexity is up right nowPerplexity had 15 outages in the last 2 years totaling 4h 10m of downtime — averaging 0.6 incidents per month.
There were 15 Perplexity outages since October 20, 2025 totaling 4h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
Issue with usage based billing
Timeline · 1 update
- resolved Sep 03, 2026, 09:10 PM UTC
Status: Resolved This incident has been resolved.
Computer Tasks Degraded
Timeline · 1 update
- resolved Sep 01, 2026, 12:06 AM UTC
Status: Resolved This incident has been resolved. Affected components Computer (Operational)
Computer Sandbox Errors
Timeline · 1 update
- resolved Aug 14, 2026, 11:43 AM UTC
Status: Resolved This incident has been resolved.
Investigating API issue
Timeline · 1 update
- resolved Aug 13, 2026, 01:49 AM UTC
Status: Resolved This incident has been resolved.
test incident
Timeline · 1 update
- resolved Aug 11, 2026, 10:40 PM UTC
Status: Resolved all our tests are back to normal
Computer Sandbox Issue
Timeline · 1 update
- resolved Aug 06, 2026, 06:03 PM UTC
Status: Resolved This incident has been resolved.
Computer sandbox issues
Timeline · 1 update
- resolved Jul 23, 2026, 06:14 PM UTC
Status: Resolved This incident has been resolved.
Computer outage
Affected: WebsiteComputer
Timeline · 1 update
- investigating Jun 30, 2026, 10:49 PM UTC
We’re experiencing an internal infrastructure outage that’s degrading the Computer experience. Our team is actively investigating and working on a resolution.
Connector connectivity issues
Timeline · 1 update
- resolved Jun 04, 2026, 09:10 PM UTC
Type: Incident Duration: 4 hours and 31 minutes Affected Components: Website Jun 5, 01:00:00 GMT+0 - Monitoring - Connectors are recovering and getting back to normal for all users. Jun 4, 21:10:00 GMT+0 - Investigating - We have identified connector issues that are currently impacting users. Jun 5, 01:40:38 GMT+0 - Resolved - This incident has been resolved.
Perplexity Website and API incident
Affected: WebsiteAPI
Timeline · 5 updates
- investigating May 08, 2026, 12:20 AM UTC
A small percentage of our users may experience instability while using Perplexity Website and products. We're investigating the incident.
- identified May 08, 2026, 12:30 AM UTC
We’ve identified the root cause in the underlying AWS infrastructure. We’re actively working with the AWS team to mitigate the issue and fully restore the service.
- resolved May 08, 2026, 01:59 AM UTC
This incident has been resolved.
- identified May 08, 2026, 02:10 AM UTC
We are continuing to work on a fix for this incident.
- resolved May 08, 2026, 04:19 AM UTC
This incident has been resolved.
Sonar API incident
Timeline · 1 update
- resolved Feb 16, 2026, 09:35 PM UTC
Type: Incident Duration: 52 minutes Affected Components: API Feb 16, 21:35:20 GMT+0 - Investigating - We are currently investigating this incident affecting Sonar API. Feb 16, 21:48:00 GMT+0 - Identified - We have identified the root cause and working on the mitigation. Feb 16, 22:14:44 GMT+0 - Monitoring - Sonar API is recovering. We'll continue monitoring the service and its health. Feb 16, 22:27:00 GMT+0 - Resolved - This incident has been resolved.
An issue affecting the stability of the website has been detected
Timeline · 1 update
- resolved Feb 05, 2026, 10:18 PM UTC
Type: Incident Duration: 18 minutes Affected Components: Website Feb 5, 22:18:11 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. Feb 5, 22:36:11 GMT+0 - Resolved - This incident has been resolved.
Service outage
Timeline · 1 update
- resolved Dec 05, 2025, 09:06 AM UTC
Type: Incident Duration: 34 minutes Affected Components: Website, API Dec 5, 09:06:41 GMT+0 - Investigating - We are currently investigating this incident. Dec 5, 09:23:16 GMT+0 - Monitoring - The service is recovering and we are monitoring; the outage was caused by an underlying service provider issue. Dec 5, 09:41:11 GMT+0 - Resolved - This incident has been resolved.
Investigating connectivity issues
Timeline · 1 update
- resolved Nov 18, 2025, 01:00 PM UTC
Type: Incident Duration: 2 hours Affected Components: Website, API Nov 18, 13:00:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 13:46:17 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 14:59:39 GMT+0 - Resolved - This incident has been resolved.