Perplexity status — and how to poll it yourself
Snapshot: Aug 31, 2026 9:30 AM ET · Statuses shown are build-time snapshots — they refresh on each site rebuild. Live auto-refresh ships post-launch.
At this snapshot, 8 of the 9 providers on our status board reported fully operational. Here is where Perplexity stood, and how to get the same answer from its status API without a browser.
| Status page | https://status.perplexity.com |
| Snapshot status | Operational Page status: UP (as of Aug 31, 2026 9:30 AM ET) |
| Components | 3/3 |
| Status API format | instatus |
| JSON endpoint | https://status.perplexity.com/summary.json |
| Components endpoint | https://status.perplexity.com/v2/components.json |
| Gotcha | status.perplexity.ai redirects to status.perplexity.com; Instatus format, not Statuspage |
| Verification | verified — live fetch on 2026-08-31 |
The 3 components Perplexity reports status for
When Perplexity says "operational", this is the granularity behind the claim — the component list its own status feed publishes, fetched 2026-08-31. All were reported operational at snapshot time. If an incident hits, these are the names its status page will scope it to.
APIComputerWebsite
Polling Perplexity's status programmatically
Instatus — not Statuspage. GET /summary.json for page status, GET /v2/components.json for components. The Statuspage-style /api/v2/status.json path does not apply here.
curl -s https://status.perplexity.com/summary.jsonGotcha (verified 2026-08-31): status.perplexity.ai redirects to status.perplexity.com; Instatus format, not Statuspage
Everything above was verified against the live endpoint on 2026-08-31 — nothing is inferred from platform defaults. If the endpoint moved, tell us.
Model retirements — Perplexity
Our 129-row deprecations table tracks the providers that publish dated, citable retirement schedules (OpenAI, Anthropic, Google Vertex AI and Azure OpenAI). Perplexity publishes no dated model-retirement schedule we could verify against its own docs — absence here means absence of a published schedule, not a no-deprecation guarantee. Pin model versions and watch the provider's changelog either way.