Perplexity degradation — 2026-09-05
Provider reports: HASISSUES It began at 2026-09-05 05:57 UTC and recovered at 2026-09-05 07:15 UTC, lasting 1h 18m. We recorded 26 failing checks during the window.
Check-by-check timeline
- 2026-09-05 05:42 UTCOperational523ms · HTTP 200
- 2026-09-05 05:45 UTCOperational146ms · HTTP 200
- 2026-09-05 05:48 UTCOperational232ms · HTTP 200
- 2026-09-05 05:51 UTCOperational256ms · HTTP 200
- 2026-09-05 05:54 UTCDegraded126ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 05:57 UTCDegraded522ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:00 UTCDegraded56ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:03 UTCDegraded86ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:06 UTCDegraded217ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:09 UTCDegraded87ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:12 UTCDegraded104ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:15 UTCDegraded370ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:18 UTCDegraded112ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:21 UTCDegraded149ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:24 UTCDegraded403ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:27 UTCDegraded101ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:30 UTCDegraded58ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:33 UTCDegraded347ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:36 UTCDegraded156ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:39 UTCDegraded116ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:42 UTCDegraded369ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:45 UTCDegraded183ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:48 UTCDegraded144ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:51 UTCDegraded358ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:54 UTCDegraded102ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 06:57 UTCDegraded103ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 07:00 UTCDegraded260ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 07:03 UTCDegraded107ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 07:06 UTCDegraded130ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 07:09 UTCDegraded236ms · HTTP 200Provider reports: HASISSUES
- 2026-09-05 07:12 UTCOperational197ms · HTTP 200
- 2026-09-05 07:15 UTCOperational122ms · HTTP 200
- 2026-09-05 07:18 UTCOperational95ms · HTTP 200
- 2026-09-05 07:21 UTCOperational559ms · HTTP 200
- 2026-09-05 07:24 UTCOperational231ms · HTTP 200
- 2026-09-05 07:27 UTCOperational96ms · 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.