All services / AI
Perplexity
- Current assessment
- Operational (provider)
- Confidence
- Medium confidence
- Scope
- Provider-wide
- Last verified
- Nov 18, 10:26 PM UTC
- Sources
- 1 source: Official
Official incident history
- ResolvedStarted: · Duration: 37 min
Perplexity: API, degraded performance
Provider's original title: Elevated API errors and timeouts
Provider updates (3)
- 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.”
- Resolved “The issue affecting the Website, App, and Computer has been resolved. All services are operational. The API remained operational throughout this incident.”
- Started: · Duration: 139 minResolved
Provider updates (3)
- 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.”
- Started: · Duration: 40 minResolved
Provider updates (3)
- 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.”
- ResolvedStarted: · Duration: 34 min
Perplexity: degraded performance
Provider's original title: Computer Tasks Degraded
Provider updates (4)
- 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.”
- ResolvedStarted: · Duration: 57 min
Perplexity: outage or errors
Provider's original title: Computer Sandbox Errors
Provider updates (2)
- Investigating “We are currently investigating this incident.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 64 minResolved
Provider updates (3)
- Investigating “We are currently investigating this incident.”
- Monitoring “We identified the problematic deploy and rolled back the service.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 213 minResolved
Provider updates (4)
- 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.”
- Started: · Duration: 26 minResolved
Provider updates (3)
- 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.”
- Started: · Duration: 101 minResolved
Provider updates (3)
- Investigating “We are currently investigating this incident.”
- Monitoring “We implemented a fix and are currently monitoring the result.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 127 minResolved
Provider updates (3)
- 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.”
- Started: · Duration: 271 minResolved
Provider updates (3)
- 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.”
- Started: · Duration: 99 minResolved
Provider updates (5)
- 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.”
- Started: · Duration: 52 minResolved
Provider updates (4)
- 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.”
- Started: · Duration: 18 minResolved
Provider updates (2)
- Investigating “We are investigating elevated error rates on the Perplexity website.”
- Resolved “This incident has been resolved.”
- ResolvedStarted: · Duration: 35 min
Perplexity: outage or errors
Provider's original title: Service outage
Provider updates (3)
- 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.”
- Started: · Duration: 120 minResolved
Provider updates (2)
- Investigating “We are currently investigating this incident.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 317 minResolved
Provider updates (4)
- Investigating “We are investigating elevated error rates on the Perplexity website.”
- 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.”
- Monitoring “Error rates have returned to normal. We will continue to monitor”
- Resolved “This incident has been resolved.”
- Started: · Duration: 182 minResolved
Provider updates (4)
- 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.”
- Monitoring “Most services are operational now, we are continuing to monitor”
- Resolved “This incident has now been resolved.”
- ResolvedStarted: · Duration: 0 min
Perplexity: API, outage or errors
Provider's original title: API outage
Provider updates (1)
- Resolved “We experienced an outage for the API that lasted roughly 20 minutes. This incident has been resolved.”
- ResolvedStarted: · Duration: 221 min
Perplexity: increased latency
Provider's original title: We are investigating slowness and elevated error rates on the Perplexity website
Provider updates (4)
- 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.”
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.
| Source | Last observed | Age | Used in assessment |
|---|---|---|---|
| Official | 2 min ago | Yes, recent |
Technical details
Affected components (provider)
The provider lists no degraded components.