Perplexity reported "Elevated API errors and timeouts" on its status page at 2026-10-09 22:38 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-10-09 22:38 UTC and ended at 2026-10-09 23:15 UTC. It lasted 37 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-10-09 22:38 UTC

Elevated API errors and timeouts

ResolvedOfficial update

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

The latest update from Perplexity.

State

Resolved

Started

22 d ago

2026-10-09 22:38 UTC

Lasted

37 min

until 2026-10-09 23:15 UTC

Worst impact

Degraded

Timeline

4 updates

22:3822:4822:5723:0623:15

DegradedUpdate postedTimes in UTC

Investigating

23 min 62%

Monitoring

14 min 38%

Updates

Times in UTC

As posted by Perplexity

Resolved2026-10-09 23:15 UTC

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

Monitoring2026-10-09 23:10 UTC

Correction to our previous updates: we do not believe the API was affected by this incident and it remains operational.

Monitoring2026-10-09 23:01 UTC

The issue causing elevated API errors and timeouts has been mitigated.

Investigating2026-10-09 22:38 UTC

Users may experience errors or timeouts when making API requests. We are investigating elevated API errors and timeouts.

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

1.4× 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·Computer Tasks Degraded

This incident has been resolved.

Resolvedresolved 61 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