Perplexity degradation — 2026-09-03
Provider reports: HASISSUES It began at 2026-09-03 20:36 UTC and recovered at 2026-09-03 21:15 UTC, lasting 39 min. We recorded 13 failing checks during the window.
Check-by-check timeline
- 2026-09-03 20:21 UTCOperational513ms · HTTP 200
- 2026-09-03 20:24 UTCOperational171ms · HTTP 200
- 2026-09-03 20:27 UTCOperational255ms · HTTP 200
- 2026-09-03 20:30 UTCOperational244ms · HTTP 200
- 2026-09-03 20:33 UTCDegraded441ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:36 UTCDegraded553ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:39 UTCDegraded393ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:42 UTCDegraded296ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:45 UTCDegraded377ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:48 UTCDegraded646ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:51 UTCDegraded509ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:54 UTCDegraded339ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 20:57 UTCDegraded171ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 21:00 UTCDegraded299ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 21:03 UTCDegraded185ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 21:06 UTCDegraded368ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 21:09 UTCDegraded229ms · HTTP 200Provider reports: HASISSUES
- 2026-09-03 21:12 UTCOperational181ms · HTTP 200
- 2026-09-03 21:15 UTCOperational346ms · HTTP 200
- 2026-09-03 21:18 UTCOperational121ms · HTTP 200
- 2026-09-03 21:21 UTCOperational361ms · HTTP 200
- 2026-09-03 21:24 UTCOperational113ms · HTTP 200
- 2026-09-03 21:27 UTCOperational280ms · HTTP 200
- 2026-09-03 21:30 UTCOperational125ms · 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.