sevanalysis

Perplexity

AI. Source: Perplexity status page.

Incidents, last 90 days
7
Median to mitigation
57m
Median to resolution
57m
p95 to resolution
3h 33m
Naming an upstream provider
0%
With a postmortem on the status page
0%

What failed, last 90 days

The text does not say enough to tell5
A code release introduced the failure2

Tagged by deepseek/deepseek-v4.1-flash from each incident's updates. See the methodology.

Incidents per month

All recorded incidents

Elevated API errors and timeouts minor 2026-10-09 22:38 UTC 37m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    Users may experience errors or timeouts when making API requests. We are investigating elevated API errors and timeouts.

  2. monitoring

    The issue causing elevated API errors and timeouts has been mitigated.

  3. monitoring

    Correction to our previous updates: we do not believe the API was affected by this incident and it remains operational.

  4. 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. major 2026-09-05 04:50 UTC 2h 19m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. identified

    We are continuing to work on a fix for this incident.

  2. monitoring

    We have mitigated the issue and are monitoring impacted connectors for recovery.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Issue with usage based billing critical 2026-09-03 20:30 UTC 40m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    Computer is degraded. It is reporting insufficient credits wrongfully

  2. monitoring

    We implemented a fix and are currently monitoring the result.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Computer Tasks Degraded none 2026-08-31 23:33 UTC 34m

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

  1. investigating

    We have identified some degradation in Computer tasks and investigating the root cause.

  2. identified

    We have identified the root cause and rolled back.

  3. monitoring

    Rollback completed and we are monitoring the health of Computer tasks.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Computer Sandbox Errors minor 2026-08-14 10:46 UTC 57m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Investigating API issue critical 2026-08-13 00:45 UTC 1h 4m

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. monitoring

    We identified the problematic deploy and rolled back the service.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Computer Sandbox Issue minor 2026-08-06 14:30 UTC 3h 33m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. identified

    We are continuing to work on a fix for this incident.

  3. monitoring

    We have mitigated the issue and are repairing impacted instances.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Computer sandbox issues critical 2026-07-23 17:48 UTC 26m

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. monitoring

    We have identified the problem and have rolled back the impacted services.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Computer Sandbox Issue major 2026-07-02 18:30 UTC 1h 41m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. monitoring

    We implemented a fix and are currently monitoring the result.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Computer Sandbox Issue critical 2026-06-30 21:39 UTC 2h 7m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    The team has implemented a fix and are continuing to monitor recovery.

  2. monitoring

    We implemented a fix and are currently monitoring the result.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Connector connectivity issues major 2026-06-04 21:10 UTC 4h 31m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We have identified connector issues that are currently impacting users.

  2. monitoring

    Connectors are recovering and getting back to normal for all users.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Perplexity Website and API incident minor 2026-05-08 00:20 UTC 1h 39m

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

  1. investigating

    A small percentage of our users may experience instability while using Perplexity Website and products. We're investigating the incident.

  2. 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.

  3. resolved

    This incident has been resolved.

  4. identified

    We are continuing to work on a fix for this incident.

  5. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Sonar API incident critical 2026-02-16 21:35 UTC 52m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident affecting Sonar API.

  2. identified

    We have identified the root cause and working on the mitigation.

  3. monitoring

    Sonar API is recovering. We'll continue monitoring the service and its health.

  4. 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 major 2026-02-05 22:18 UTC 18m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    We are investigating elevated error rates on the Perplexity website.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Service outage critical 2025-12-05 09:06 UTC 34m

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. monitoring

    The service is recovering and we are monitoring; the outage was caused by an underlying service provider issue.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Investigating connectivity issues major 2025-11-18 13:00 UTC 2h

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. investigating

    We are currently investigating this incident.

  3. 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 major 2025-10-20 15:53 UTC 5h 17m

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

  1. investigating

    We are investigating elevated error rates on the Perplexity website.

  2. investigating

    We are still investigating this incident

  3. 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.

  4. monitoring

    Error rates have returned to normal. We will continue to monitor

  5. 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 critical 2025-10-20 06:54 UTC 3h 2m

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

  1. investigating

    We are investigating elevated error rates on the Perplexity website.

  2. 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.

  3. 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.

  4. monitoring

    Most services are operational now, we are continuing to monitor

  5. resolved

    This incident has now been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

API outage none 2025-09-05 16:30 UTC 0m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. resolved

    We experienced an outage for the API that lasted roughly 20 minutes. This incident has been resolved.

  2. 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 major 2025-06-10 11:50 UTC 3h 41m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are investigating slowness and elevated error rates on the Perplexity website.

  2. identified

    We are continuing to work on a fix for this incident.

  3. monitoring

    We implemented a fix and are currently monitoring the result.

  4. 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 major 2025-05-16 07:14 UTC 25m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are investigating elevated error rates on the Perplexity website.

  2. 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 major 2025-05-15 14:44 UTC 14m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are investigating elevated error rates on the Perplexity website.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.

Investigating increased API latency minor 2025-05-07 03:43 UTC 1h 49m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. monitoring

    We implemented a fix and are currently monitoring the result.

  3. 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 minor 2025-04-28 07:08 UTC 20h 20m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    We are currently investigating this incident.

  2. 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 major 2025-04-02 00:01 UTC 2m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    We are investigating elevated error rates on the Perplexity website.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Perplexity's status page.