Official incident history

  1. Perplexity: API, degraded performance

    Provider's original title: Elevated API errors and timeouts

    Started: · Duration: 37 min
    Provider updates (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. Resolved “The issue affecting the Website, App, and Computer has been resolved. All services are operational. The API remained operational throughout this incident.”
    Resolved
  2. Started: · Duration: 139 min
    Provider updates (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.”
    Resolved
  3. Started: · Duration: 40 min
    Provider updates (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.”
    Resolved
  4. Perplexity: degraded performance

    Provider's original title: Computer Tasks Degraded

    Started: · Duration: 34 min
    Provider updates (4)
    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.”
    Resolved
  5. Perplexity: outage or errors

    Provider's original title: Computer Sandbox Errors

    Started: · Duration: 57 min
    Provider updates (2)
    1. Investigating “We are currently investigating this incident.”
    2. Resolved “This incident has been resolved.”
    Resolved
  6. Started: · Duration: 64 min
    Provider updates (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.”
    Resolved
  7. Started: · Duration: 213 min
    Provider updates (4)
    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.”
    Resolved
  8. Started: · Duration: 26 min
    Provider updates (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.”
    Resolved
  9. Started: · Duration: 101 min
    Provider updates (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.”
    Resolved
  10. Started: · Duration: 127 min
    Provider updates (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.”
    Resolved
  11. Started: · Duration: 271 min
    Provider updates (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.”
    Resolved
  12. Started: · Duration: 99 min
    Provider updates (5)
    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.”
    Resolved
  13. Started: · Duration: 52 min
    Provider updates (4)
    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.”
    Resolved
  14. Started: · Duration: 18 min
    Provider updates (2)
    1. Investigating “We are investigating elevated error rates on the Perplexity website.”
    2. Resolved “This incident has been resolved.”
    Resolved
  15. Perplexity: outage or errors

    Provider's original title: Service outage

    Started: · Duration: 35 min
    Provider updates (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.”
    Resolved
  16. Started: · Duration: 120 min
    Provider updates (2)
    1. Investigating “We are currently investigating this incident.”
    2. Resolved “This incident has been resolved.”
    Resolved
  17. Started: · Duration: 317 min
    Provider updates (4)
    1. Investigating “We are investigating elevated error rates on the Perplexity website.”
    2. Identified “This has been determined to be related to the earlier AWS service degradation. <https://health.aws.amazon.com/health/status> We are continuing to work on a fix for this incident.”
    3. Monitoring “Error rates have returned to normal. We will continue to monitor”
    4. Resolved “This incident has been resolved.”
    Resolved
  18. Started: · Duration: 182 min
    Provider updates (4)
    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. Monitoring “Most services are operational now, we are continuing to monitor”
    4. Resolved “This incident has now been resolved.”
    Resolved
  19. Perplexity: API, outage or errors

    Provider's original title: API outage

    Started: · Duration: 0 min
    Provider updates (1)
    1. Resolved “We experienced an outage for the API that lasted roughly 20 minutes. This incident has been resolved.”
    Resolved
  20. Perplexity: increased latency

    Provider's original title: We are investigating slowness and elevated error rates on the Perplexity website

    Started: · Duration: 221 min
    Provider updates (4)
    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.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
Perplexity Status ↗ · All Systems Operational · Nov 18, 10:26 PM UTC

Why this assessment

  • Provider reports no active incident.

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official2 min agoYes, recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗