Perplexity status — and how to poll it yourself
Snapshot: Nov 2, 2026 7:20 AM ET · Statuses shown are build-time snapshots — they refresh on each site rebuild. Live auto-refresh ships post-launch.
At this snapshot, 9 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 All Systems Operational (as of Nov 2, 2026 7:20 AM ET) |
| Components | 4/4 |
| Status API format | statuspage-v2 (incident.io-hosted, Statuspage-compatible API) |
| JSON endpoint | https://status.perplexity.com/api/v2/status.json |
| Gotcha | status.perplexity.ai redirects to status.perplexity.com. The page moved from Instatus to incident.io after our Aug 31, 2026 verification: the old Instatus /summary.json and /v2/components.json now return 404; use the Statuspage-compatible /api/v2/status.json and /api/v2/components.json. |
| Verification | verified — live fetch on 2026-11-02 |
The 4 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-11-02. All were reported operational at snapshot time. If an incident hits, these are the names its status page will scope it to.
APIAppComputerWebsite
Polling Perplexity's status programmatically
Atlassian Statuspage v2. GET /api/v2/status.json returns status.indicator (none | minor | major | critical) and a human description; GET /api/v2/components.json returns per-component state.
curl -s https://status.perplexity.com/api/v2/status.jsonGotcha (verified 2026-11-02): status.perplexity.ai redirects to status.perplexity.com. The page moved from Instatus to incident.io after our Aug 31, 2026 verification: the old Instatus /summary.json and /v2/components.json now return 404; use the Statuspage-compatible /api/v2/status.json and /api/v2/components.json.
Everything above was verified against the live endpoint on 2026-11-02 — 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.