outages.live
Live

Perplexity

Perplexity is operational

Checked 54 s ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

3

Median duration

27 min

Longest incident

37 min

Components

4
Website Operational
90 days agoNo incidentsToday
App Operational
90 days agoNo incidentsToday
Computer Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 9, 2026

Duration37 min22:38 to 23:15Elevated API errors and timeoutsDegraded

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

Aug 31, 2026

Duration16 min23:50 to 00:06Computer Tasks DegradedNotice

This incident has been resolved.

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.live/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.live/feed.xml?providers=perplexity
Slack
/feed subscribe https://outages.live/feed.xml?providers=perplexity

Go from tracking outages to fixing production issues with Polylane.

Try Polylane