Subscribe

Matrix / Status / Perplexity

Is the Perplexity MCP server down?

No. On 2026-11-02 14:02 PT, api.perplexity.ai answered StackMCP's check with an auth challenge (HTTP 401) in 263 ms. That is the normal healthy response. 22 checks since Oct 15 were up.

Status
Up · auth
HTTP
401
Latency
263 ms
Last check
2026-11-02 14:02 PT
Uptime
100% (22 of 22)
Transport
Streamable HTTP (also local stdio package)
Auth
OAuth or Bearer API key
Endpoint
https://api.perplexity.ai/mcp

What we checked

The scheduled check runs once a day, with no credentials and no API key. This log has 23 runs on 19 days, and 4 of those days have more than one run. Each run sends one MCP initialize request. HTTP 401 with an auth challenge means the server is up and wants a sign-in. That result is labeled Up · auth. HTTP 200 means the server answered without asking for a sign-in. A timeout, a 5xx response, or a 404 is a problem. Another code is labeled Unknown, because the check could not tell. The check only shows that the MCP endpoint answered. It does not show that Perplexity's app is working.

Bearer resource_metadata="https://api.perplexity.ai/.well-known/oauth-protected-resource"
Resource metadata: https://api.perplexity.ai/.well-known/oauth-protected-resource

Last 22 checks

22 stored checks, newest first. Times are Pacific Time.

CheckedHTTPmsResult
2026-11-02 14:02 PT401263Up · auth
2026-11-01 10:13 PT40166Up · auth
2026-10-31 10:28 PT40176Up · auth
2026-10-30 11:22 PT401182Up · auth
2026-10-29 11:45 PT401130Up · auth
2026-10-28 11:36 PT401157Up · auth
2026-10-27 11:30 PT401159Up · auth
2026-10-26 11:58 PT401153Up · auth
2026-10-25 09:55 PT401152Up · auth
2026-10-24 09:23 PT401189Up · auth
2026-10-23 10:38 PT401108Up · auth
2026-10-22 10:46 PT401117Up · auth
2026-10-21 10:48 PT401166Up · auth
2026-10-20 10:39 PT401138Up · auth
2026-10-19 11:56 PT401185Up · auth
2026-10-18 22:45 PT401257Up · auth
2026-10-18 09:15 PT40175Up · auth
2026-10-17 09:03 PT401106Up · auth
2026-10-16 10:06 PT401274Up · auth
2026-10-16 06:06 PT40151Up · auth
2026-10-15 23:24 PT401114Up · auth
2026-10-15 20:56 PT40181Up · auth

Last change

Up · auth since Oct 15. No later status change is stored.

Full changelog.

Is Perplexity itself down?

Perplexity publishes its own status page: Perplexity Status. Checked 2026-11-02.

Our check only shows that the MCP endpoint answers. If Perplexity's app is down, your connector can fail even when this page says up.

MCP status for other tools

FAQ

Is the Perplexity MCP server down?

No. On 2026-11-02 14:02 PT, api.perplexity.ai answered StackMCP's check with an auth challenge (HTTP 401) in 263 ms. That is the normal healthy response. 22 checks since Oct 15 were up.

What does "Up · auth" or HTTP 401 mean on an MCP status check?

It means the server is up. MCP servers that use OAuth answer an unauthenticated request with 401 and a pointer to their sign-in metadata, so a 401 with an auth challenge is the expected healthy response. It is not an error. A timeout, a 5xx error, or a 404 is what signals a problem. The check only proves the Perplexity MCP endpoint answers. It does not prove Perplexity's app is working, so also check the vendor status page when one is linked here. The check method is on the About page.

The Perplexity MCP server is up, but my connector won't work. What should I check?

This page does not list connector steps for Perplexity. The vendor pages cited for this listing do not include a troubleshooting list, and this site does not add steps of its own.

The scheduled check runs once a day. The count above is every stored check, not one check per day. No credentials are sent. The runner region is not published. The method is on the About page. Setup: Perplexity.