Perplexity
AI. Source: Perplexity status page.
History starts 2026-08-24 23:39 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 18+
- Median to mitigation
- -136669m
- Median to resolution
- -136669m
- p95 to resolution
- 37m
- Naming an upstream provider
- 5%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 10 |
| A code release introduced the failure | 3 |
| A provider or third-party service this vendor depends on failed | 2 |
| A configuration change caused the failure | 1 |
| Network, DNS, routing or connectivity failure | 1 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Elevated API errors and timeouts
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
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.
Excerpts are shortened. Read the full incident on Perplexity's status page.
We have identified few connectors that are impacting users.
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are continuing to work on a fix for this incident.
-
monitoring
We have mitigated the issue and are monitoring impacted connectors for recovery.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Issue with usage based billing
Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Computer is degraded. It is reporting insufficient credits wrongfully
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Computer Tasks Degraded
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We have identified some degradation in Computer tasks and investigating the root cause.
-
identified
We have identified the root cause and rolled back.
-
monitoring
Rollback completed and we are monitoring the health of Computer tasks.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Computer Sandbox Errors
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Investigating API issue
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
monitoring
We identified the problematic deploy and rolled back the service.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Computer Sandbox Issue
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
identified
We are continuing to work on a fix for this incident.
-
monitoring
We have mitigated the issue and are repairing impacted instances.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Computer sandbox issues
Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
monitoring
We have identified the problem and have rolled back the impacted services.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Computer Sandbox Issue
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Computer Sandbox Issue
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
The team has implemented a fix and are continuing to monitor recovery.
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Connector connectivity issues
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We have identified connector issues that are currently impacting users.
-
monitoring
Connectors are recovering and getting back to normal for all users.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Perplexity Website and API incident
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
A small percentage of our users may experience instability while using Perplexity Website and products. We're investigating the incident.
-
identified
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
This incident has been resolved.
-
identified
We are continuing to work on a fix for this incident.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Sonar API incident
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident affecting Sonar API.
-
identified
We have identified the root cause and working on the mitigation.
-
monitoring
Sonar API is recovering. We'll continue monitoring the service and its health.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
An issue affecting the stability of the website has been detected
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating elevated error rates on the Perplexity website.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Service outage
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
monitoring
The service is recovering and we are monitoring; the outage was caused by an underlying service provider issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Investigating connectivity issues
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
investigating
We are currently investigating this incident.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
An issue affecting the stability of the website has been detected
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We are investigating elevated error rates on the Perplexity website.
-
investigating
We are still investigating this incident
-
identified
This has been determined to be related to the earlier AWS service degradation. We are continuing to work on a fix for this incident.
-
monitoring
Error rates have returned to normal. We will continue to monitor
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
An issue affecting the stability of the website has been detected
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We are investigating elevated error rates on the Perplexity website.
-
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.
-
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.
-
monitoring
Most services are operational now, we are continuing to monitor
-
resolved
This incident has now been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
API outage
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
resolved
We experienced an outage for the API that lasted roughly 20 minutes. This incident has been resolved.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
We are investigating slowness and elevated error rates on the Perplexity website
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating slowness and elevated error rates on the Perplexity website.
-
identified
We are continuing to work on a fix for this incident.
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
An issue affecting the stability of the website has been detected
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating elevated error rates on the Perplexity website.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
An issue affecting the stability of the website has been detected
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating elevated error rates on the Perplexity website.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
Investigating increased API latency
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
P99 First Token Latency of Sonar Pro is elevated
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.
An issue affecting the stability of the website has been detected
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating elevated error rates on the Perplexity website.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Perplexity's status page.