Vendors · service reliability · Perplexity

Perplexity: 2 incidents in 30 days

Every incident on Perplexity’s status page, kept from its history feed. The record reaches back to 6 Aug 2026, the oldest post in the first copy. No gap: each read reached back to the one before it. The vendor record holds Perplexity’s data terms.

Embed

Incidents in 30 days, by vendor

<iframe src="https://jesseahawkins.com/vendors/embed/status/" title="AI service reliability: OpenAI posted the most incidents: 42 in 30 days" width="100%" height="520" style="border:0;max-width:100%" loading="lazy"></iframe>

The frame credits each vendor’s own status page and links back to its page. Preview it.

Cite

This page

Jesse Hawkins, “Perplexity status history: Perplexity: 2 incidents in 30 days”, jesseahawkins.com, data retrieved 1 Nov 2026. https://jesseahawkins.com/vendors/status/perplexity/. Data: 338 incidents from the status history feeds of nine AI vendors, each kept with a sha256.

BibTeX

@misc{hawkins2026vendorsstatusperplexity,
  author = {Hawkins, Jesse},
  title = {{Perplexity status history: Perplexity: 2 incidents in 30 days}},
  year = {2026},
  howpublished = {\url{https://jesseahawkins.com/vendors/status/perplexity/}},
  note = {Data: 338 incidents from the status history feeds of nine AI vendors, each kept with a sha256, retrieved 2026-11-01}
}

The record · this site

jesseahawkins.com, “AI service reliability: every incident, kept”, read 1 Nov 2026 from the vendors’ status history feeds. https://jesseahawkins.com/vendors/status/

Download

Post on X

Incidents each month

count only: the feed gives the newest post of each incident

Aug 2026 4 incidents
Sep 2026 4 incidents
Oct 2026 2 incidents
Nov 2026 0 incidents

A vendor that posts more often is not for that reason less reliable: each vendor decides what it posts, and how finely. The first month starts at the oldest post in the first copy kept.

Which part each incident touched

this site’s grouping of Perplexity’s own component names

Incidents each month by the part of the service they touched
Part	Aug 2026	Sep 2026	Oct 2026	Nov 2026
Other	0	2	2	0
Not named	4	2	0	0

An incident that touched two parts counts in both. “Not named” means the feed names no component for it.

Every incident kept

10 · newest first · each links Perplexity’s own post

13 Oct 2026, 21:56 UTC complete Maintenance: Scheduled Computer Maintenance Computer · kept 26 Oct 2026, sha256 4921536c8eef
9 Oct 2026, 23:15 UTC resolved Elevated API errors and timeouts API, Website, App, Computer · kept 26 Oct 2026, sha256 4921536c8eef
10 Sep 2026, 21:36 UTC complete Maintenance: Status page migration to incident.io Website, App, Computer · kept 26 Oct 2026, sha256 4921536c8eef
5 Sep 2026, 07:09 UTC resolved We have identified few connectors that are impacting users. no component named · kept 26 Oct 2026, sha256 4921536c8eef
3 Sep 2026, 21:10 UTC resolved Issue with usage based billing no component named · kept 26 Oct 2026, sha256 4921536c8eef
1 Sep 2026, 00:06 UTC resolved Computer Tasks Degraded Computer · kept 26 Oct 2026, sha256 4921536c8eef
14 Aug 2026, 11:43 UTC resolved Computer Sandbox Errors no component named · kept 26 Oct 2026, sha256 4921536c8eef
13 Aug 2026, 01:49 UTC resolved Investigating API issue no component named · kept 26 Oct 2026, sha256 4921536c8eef
11 Aug 2026, 22:40 UTC resolved test incident no component named · kept 26 Oct 2026, sha256 4921536c8eef
6 Aug 2026, 18:03 UTC resolved Computer Sandbox Issue no component named · kept 26 Oct 2026, sha256 4921536c8eef

Every read of the feed

a copy is kept when its bytes change

2026-11-01 00:41 UTC 10 incidents, back to 6 Aug 2026, 18:03 UTC · sha256 14181e2ab584
2026-10-26 15:10 UTC 10 incidents, back to 6 Aug 2026, 18:03 UTC · sha256 4921536c8eef
2026-10-26 15:09 UTC 10 incidents, back to 6 Aug 2026, 18:03 UTC · sha256 4921536c8eef

Sources

status-incidents.csv RSS Every dataset → Status → Glossary →

Perplexity: status page, history feed. Read 1 Nov 2026.