Vendor record
Perplexity
Checked
Front door check counts and Perplexity’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against Perplexity in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Perplexity product, region or your app worked.
How we count front door checksPerplexity says
Incident posts from Perplexity’s status page, with its titles, impact levels and times. They say what Perplexity chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
1
incidents Perplexity posted, last 30 days
Most recent records · all dates
Elevated API errors and timeouts
Not specifiedStarted, per Perplexity
Closed in our record(46m)
We have identified few connectors that are currently impacting users.
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(1h 26m)
Issue with usage based billing
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(49m)
Computer Tasks Degraded
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(42m)
Investigating API issue
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(37m)
7 older records
Computer Sandbox Issue
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(3h 40m)
Computer sandbox issues
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(26m)
Computer Sandbox Issue
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(1h 45m)
Computer outage
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(11m)
Computer Sandbox Issue
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(2h 11m)
Connector connectivity issues
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(4h 40m)
Perplexity Website incident
Not specifiedPerplexity’s postStarted, per Perplexity
Closed in our record(4h 17m)
Your code, your dependencies
See which of your code paths call Perplexity
Connect GitHub or GitLab to find where your public or private repository uses Perplexity. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Perplexity status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Perplexity currently down?
Perplexity's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Perplexity last have an outage?
The most recent closed incident record began 6 days ago and spans 46 minutes. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Perplexity?
No. CheckUpstream does not run front door checks against Perplexity. The incident history on this page is what Perplexity reported, not a measure of how often it was available.
How do I monitor Perplexity in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Perplexity?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.