Perplexity degradation — 2026-09-01
Provider reports: HASISSUES It began at 2026-09-01 00:00 UTC and recovered at 2026-09-01 00:12 UTC, lasting 12 min. We recorded 4 failing checks during the window.
Check-by-check timeline
- 2026-08-31 23:45 UTCOperational94ms · HTTP 200
- 2026-08-31 23:48 UTCOperational183ms · HTTP 200
- 2026-08-31 23:51 UTCOperational239ms · HTTP 200
- 2026-08-31 23:54 UTCOperational120ms · HTTP 200
- 2026-08-31 23:57 UTCDegraded358ms · HTTP 200Provider reports: HASISSUES
- 2026-09-01 00:00 UTCDegraded451ms · HTTP 200Provider reports: HASISSUES
- 2026-09-01 00:03 UTCDegraded286ms · HTTP 200Provider reports: HASISSUES
- 2026-09-01 00:06 UTCDegraded181ms · HTTP 200Provider reports: HASISSUES
- 2026-09-01 00:09 UTCOperational460ms · HTTP 200
- 2026-09-01 00:12 UTCOperational145ms · HTTP 200
- 2026-09-01 00:15 UTCOperational140ms · HTTP 200
- 2026-09-01 00:18 UTCOperational262ms · HTTP 200
- 2026-09-01 00:21 UTCOperational355ms · HTTP 200
- 2026-09-01 00:24 UTCOperational48ms · HTTP 200
Current Perplexity status and full outage history
How this is measured
Readings are taken every few minutes from outside Perplexity's network, combining their published status feed with a timed request to the service itself.
An incident opens after two consecutive bad readings and closes after two consecutive good ones, so the recorded duration may be a few minutes wider than the true outage.
Perplexity's official status page is the authority on causes and affected components.