Is Perplexity down?
Right now
No. Perplexity is operational.
No incidents reported.
Read from status.perplexity.com · every 120s
For agents
proceed
Proceed.
GET upbutler.com/status/perplexity/status.agent.json
MCP: upstream_status {"service":"perplexity"}
The Sonar search-grounded API and the Perplexity apps.
What Perplexity reports
Operational
Taken as is from Perplexity's own status page API. Incident titles and component names below are theirs.
Open status.perplexity.comUpButler's independent probe
There is no keyless endpoint of Perplexity that says anything useful, so UpButler does not probe it. To check your own Perplexity account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Perplexity components
4 operational
- WebsiteOperational
- AppOperational
- ComputerOperational
- APIOperational
Perplexity incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Elevated API errors and timeouts | minor | 37 min |
Tell your outage from Perplexity's
Declare that your project depends on Perplexity. When one of your monitors fails while Perplexity has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- perplexitycurl -s https://upbutler.com/status/perplexity/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "perplexity",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Perplexity down right now?
- No. As of 2026-10-10 05:09 UTC, Perplexity is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Perplexity's own status page API at https://status.perplexity.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Perplexity's words.
- How can my agent or app check Perplexity status?
- Fetch https://upbutler.com/status/perplexity/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"perplexity"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Perplexity's?
- Add "perplexity" to the dependencies of your UpButler workspace. When one of your monitors fails while Perplexity has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in ai models and tooling
UpButler is not affiliated with Perplexity. Status and incident text belong to Perplexity and are read from their public status source; the probe result is UpButler's own measurement.