Perplexity reported "Computer Tasks Degraded" on its status page at 2026-08-31 23:50 UTC.

Perplexity did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-08-31 23:50 UTC and ended at 2026-09-01 00:06 UTC. It lasted 16 min.

How do I get alerts for Perplexity?

Subscribe to the Perplexity live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Perplexity. outages.live reads it every few minutes and keeps every update.

PerplexityIncident · 2026-08-31 23:50 UTC

Computer Tasks Degraded

ResolvedOfficial update

This incident has been resolved.

The latest update from Perplexity.

State

Resolved

Started

61 d ago

2026-08-31 23:50 UTC

Lasted

16 min

until 2026-09-01 00:06 UTC

Worst impact

Notice

Timeline

4 updates

23:5023:5423:5800:0200:06

NoticeUpdate postedTimes in UTC

Identified

2 min 15%

Monitoring

14 min 85%

Updates

Times in UTC

As posted by Perplexity

Resolved2026-09-01 00:06 UTC

This incident has been resolved.

Monitoring2026-08-31 23:53 UTC

Rollback completed and we are monitoring the health of Computer tasks.

Identified2026-08-31 23:42 UTC

We have identified the root cause and rolled back.

Investigating2026-08-31 23:33 UTC

We have identified some degradation in Computer tasks and investigating the root cause.

Perplexity in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

27 min

This incident

38% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

37 min

median 27 min

90 days agoToday

Other Perplexity incidents

All incidents

Perplexity·Elevated API errors and timeouts

The issue affecting the Website, App, and Computer has been resolved. All services are operational. The API remained operational throughout this incident.

Resolvedresolved 22 d ago

Follow Perplexity

Your coding agent knows when Perplexity is down, and tells you when a failure is theirs, not yours. You can also get Perplexity incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "perplexity" and tell me if Perplexity has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=perplexity

Slack

/feed subscribe https://outages.cc/feed.xml?providers=perplexity

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane