Is Perplexity down right now?
Live public-endpoint check for Perplexity (perplexity.ai). We compare EU and US reachability, then link to the provider reference for broader context.
Checking Perplexity…
Pinging perplexity.ai from our servers
About Perplexity
Perplexity is an answer engine combining real-time web search with LLM reasoning, popular for research, news summarisation, and citation-backed answers. It offers Pro search (using stronger models, Pro for deeper questions), Spaces (workspace-style threads), and the Sonar API for developers. Outages show up as the answer pane loading indefinitely, citations failing to link to source pages, image search returning no results, or the Chrome extension/Arc integration timing out. Because Perplexity crawls fresh web results live rather than relying purely on pre-training, a Perplexity outage differs from a pure LLM outage, the search-retrieval layer can fail independently of the model.
Perplexity does not publish a reliable public status dashboard for every outage. The community outage reference below can help with extra context, but independent monitoring is still the safer signal.
How Perplexity outages affect production workloads
Developer-platform outages have outsized impact because they cascade. When Perplexity is degraded, every customer's build pipeline, deploy hook, or webhook delivery can stall, and the failure mode often looks like a customer problem before engineers realize the dependency is the cause. CI runs hang, status checks never report, and queued jobs pile up silently.
The live check above provides independent public-endpoint evidence from EU and US, including status and response timing. That helps separate a broad reachability problem from a local client issue, but it does not execute your private API call, build, webhook, or deploy. Test the exact dependency path before attributing the incident to Perplexity.
Common signs Perplexity is having issues
- API rate limits returning earlier than the documented thresholds
- Webhook deliveries showing 5xx errors or unusual latency tail
- Deploy or build hooks accepted by Perplexity but never firing downstream
- OAuth or token endpoints failing intermittently for the same client credentials
What to do when Perplexity is degraded
When Perplexity is having trouble, the fastest mitigation is usually feature-flagging the dependency off if your application can degrade gracefully. Check the multi-region results on this page first; if both regions report healthy but your application still sees failures, the issue is likely your network path or DNS, not Perplexity itself.
Monitor Perplexity automatically.
Get independent alerts when the public Perplexity endpoint fails a confirmed check. Start free with 10-minute checks, or use Business or Agency for 60-second uptime checks.
10-minute free checks
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Email + push on Free
Paid plans unlock additional team and incident channels.
free forever · paid trials last 10 days
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Perplexity on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Perplexity uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.