Perplexity degradation — 2026-08-13
Provider reports: HASISSUES It began at 2026-08-13 01:27 UTC and recovered at 2026-08-13 01:54 UTC, lasting 27 min. We recorded 9 failing checks during the window.
Check-by-check timeline
- 2026-08-13 01:15 UTCOperational61ms · HTTP 200
- 2026-08-13 01:18 UTCOperational62ms · HTTP 200
- 2026-08-13 01:21 UTCOperational66ms · HTTP 200
- 2026-08-13 01:24 UTCDegraded279ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:27 UTCDegraded58ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:30 UTCDegraded18ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:33 UTCDegraded52ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:36 UTCDegraded165ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:39 UTCDegraded68ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:42 UTCDegraded342ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:45 UTCDegraded74ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:48 UTCDegraded175ms · HTTP 200Provider reports: HASISSUES
- 2026-08-13 01:51 UTCOperational63ms · HTTP 200
- 2026-08-13 01:54 UTCOperational265ms · HTTP 200
- 2026-08-13 01:57 UTCOperational235ms · HTTP 200
- 2026-08-13 02:00 UTCOperational15ms · HTTP 200
- 2026-08-13 02:03 UTCOperational78ms · HTTP 200
- 2026-08-13 02:06 UTCOperational234ms · HTTP 200
- 2026-08-13 02:09 UTCOperational229ms · 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.