Perplexity degradation — 2026-08-14
Provider reports: HASISSUES It began at 2026-08-14 11:57 UTC and recovered at 2026-08-14 12:03 UTC, lasting 6 min. We recorded 2 failing checks during the window.
Check-by-check timeline
- 2026-08-14 11:42 UTCOperational70ms · HTTP 200
- 2026-08-14 11:45 UTCOperational61ms · HTTP 200
- 2026-08-14 11:48 UTCOperational319ms · HTTP 200
- 2026-08-14 11:51 UTCOperational183ms · HTTP 200
- 2026-08-14 11:54 UTCDegraded171ms · HTTP 200Provider reports: HASISSUES
- 2026-08-14 11:57 UTCDegraded46ms · HTTP 200Provider reports: HASISSUES
- 2026-08-14 12:00 UTCOperational179ms · HTTP 200
- 2026-08-14 12:03 UTCOperational53ms · HTTP 200
- 2026-08-14 12:06 UTCOperational208ms · HTTP 200
- 2026-08-14 12:09 UTCOperational95ms · HTTP 200
- 2026-08-14 12:12 UTCOperational306ms · HTTP 200
- 2026-08-14 12:15 UTCOperational73ms · HTTP 200
- 2026-08-14 12:18 UTCOperational47ms · 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.