CheckUpstream does not yet run an independent probe against Perplexity, so no availability figure is published for it — only Perplexity's own disclosure record below. 11 incidents were recorded in the past 12 months; the most recent resolved earlier today after 32 minutes. Status signals are polled from Perplexity's official Instatus status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Perplexity yet, so we publish no availability figure for it. What follows is Perplexity's own disclosure record, which is a different thing.
Vendor disclosed: 1 incident · 7 of 7 days with none posted · 9m of declared impact
Fewer incidents in the last 30 days than 18% of 232 tracked services.
Share of each window with no impact declared by Perplexity
7d
99.904%
30d
99.965%
90d
99.988%
180d
99.994%
1y
99.997%
Downtime like this can be refundable
If you're a paying Perplexity customer, outages in these windows may count against Perplexity's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Perplexity entitlement →Does Perplexity actually matter to you?
A Perplexity outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 31, 23:33 UTC · resolved in 32m · Resolved
Aug 13, 01:22 UTC · resolved in 17m · Resolved
Live Perplexity status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/perplexity)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Perplexity is currently Operational. CheckUpstream tracks Perplexity in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Perplexity down" view? See the Perplexity Live status page.
Perplexity's last resolved incident started earlier today and lasted 32 minutes (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Perplexity yet, and the only other figure available would be derived from Perplexity's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Perplexity to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Perplexity's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.