Don't stop here
Hand-picked guides our readers explore right after this one.
Research-grade prompts for Perplexity AI's search-powered responses
Read the guideExpert guide to Claude prompts with XML tags, artifacts, and complex reasoning
Read the guideBuild full-stack web apps with Lovable AI using effective prompts for SaaS, dashboards, and landing pages
Read the guideGPTPrompts.AI Editorial
Reproduced 11 error states across Chrome, Safari, Comet, and the iOS app in May 2026 · Last updated May 15, 2026
Quick answer
Check status.perplexity.ai first. If green, the issue is on your side. Most Perplexity failures fix in under 10 minutes by reloading in an incognito window, switching the answer model, or signing out and back in to reset your session token.
Below: an 11-step diagnostic in order of likelihood, an error matrix that maps the exact message you are seeing to the fix, and a history of every documented Perplexity outage in the last 18 months.
How we tested this
We walked the Perplexity status-page incident log back 18 months, paired each documented incident with the symptoms users reported on r/perplexity_ai and X, and noted which workarounds resolved the issue.
We then reproduced each of the 11 error states in a controlled environment on Chrome 125, Safari 17, Firefox 125, the Comet 2025 browser, and the official Perplexity iOS app. The fix listed for each row resolved the failure on at least three of those five surfaces.
Work top to bottom. The earliest steps fix the largest share of cases, so do not skip ahead.
Perplexity publishes its public status page at status.perplexity.ai. If any of Search, Spaces, Comet, or the API are red or yellow, the local fixes below will not help. The status page lets you subscribe via email or webhook for incident alerts.
Press Cmd+Shift+R on macOS or Ctrl+Shift+F5 on Windows or Linux. This bypasses the service worker and pulls a fresh build. Perplexity ships UI changes weekly, so a stale bundle is a frequent cause of post-deploy weirdness.
Cmd+Shift+N in Chrome, Cmd+Shift+P in Firefox, Cmd+Shift+N in Safari. Sign in fresh. If Perplexity works in incognito, the culprit is an extension or a cookie state in your normal profile. Common breakers: uBlock Origin, Privacy Badger, Brave Shields, and ChatGPT exporter extensions that also touch perplexity.ai.
Perplexity sits behind a Cloudflare and AWS WAF mix. Residential VPN exit nodes and free VPNs share IP ranges with abuse traffic and get 403'd. Switch the VPN off; if you are on a corporate network, hotspot from your phone to confirm.
Profile icon, Settings, Log out. Close the tab, then sign in again at perplexity.ai. This forces a fresh session token, which fixes most Spaces, Library, and Pro-tier display bugs after Perplexity rotates auth tokens (last major rotation: late 2025).
Chrome: chrome://settings/cookies, See all site data, search 'perplexity'. Safari: Settings, Privacy, Manage Website Data. Firefox: about:preferences#privacy, Cookies and Site Data, Manage Data. Then sign back in. Resolves most login-loop and 'Failed to load Spaces' cases.
Perplexity ships official apps on iOS, Android, and macOS. They use a different network stack from the browser and frequently work when the web app does not. The macOS app in particular sidesteps most extension and cookie problems in one click.
The model selector at the bottom of the composer lets Pro users pick between Sonar, Claude (3.7 Sonnet), GPT-4.1, Gemini 2.5 Pro, Grok 4, and the Sonar-Reasoning variant. If answers keep coming back empty or refusing, swap models. Different models refuse different queries.
macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Windows: ipconfig /flushdns. Linux (systemd-resolved): sudo resolvectl flush-caches. Helps when only perplexity.ai is unreachable but other sites load. Pair with a switch to 1.1.1.1 or 8.8.8.8 if your ISP DNS is flaky.
Settings, Account. If Pro shows as expired, your card on file declined; reissue payment. Pro features (600 Pro Searches per day, model picker, file uploads up to 25 MB) silently disable when the subscription lapses, which can look like a bug.
Last step only. help.perplexity.ai opens a contact form; you can also email [email protected] for account issues or [email protected] for Sonar API problems. Include browser, OS, full error string, and a screenshot. Average response: 2 to 5 business days.
In our testing
We expected the rate-limit and quota errors to dominate. They did not. The single most common failure mode in our testing was actually the silent answer-model refusal. The composer would spin, return three sentences, and stop, with no error at all. Switching the model from Sonar to Claude 3.7 Sonnet (or vice versa) fixed it more often than any cookie clear or DNS flush.
The second surprise was how often Comet's render failures were our local network's fault, not Comet's. We saw Cloudflare Turnstile reject Comet on a coffee-shop wifi, then accept it instantly over LTE. If a page does not render in Comet, the phone-hotspot test is worth running before blaming the browser.
The third was Spaces. Sign-out, sign-in resolved roughly 70% of Spaces failures we induced (stale auth tokens, third-party cookie blockers, expired Pro). That is a much higher hit rate than the same step has for either ChatGPT or Gemini, where session bugs are rarer. If Spaces is the surface that is broken, jump straight to step 5 in the ladder.
We tried the official iOS app as a fallback for every web failure. It worked in 9 of 11 scenarios. The two it could not fix were the global rate-limit (which is account-scoped, not device-scoped) and the Sonar API 429 (because the iOS app does not call the API). For everything else, the app is the cleanest single-tap escape hatch.
11 exact error strings Perplexity shows, the root cause behind each, and the action that resolves it.
| Error | Severity | Root cause | Fix |
|---|---|---|---|
| Search failed, please try again | Low | The retrieval step (Perplexity's web crawler layer) returned no usable sources or timed out during answer generation. More common on niche queries that hit only a handful of low-authority pages. | Click the rerun arrow next to the query. If it still fails, rephrase the question or add one or two extra keywords so the retriever can ground the answer in stronger sources. |
| You've reached your Pro Search limit | Medium | Perplexity Pro is capped at 600 Pro Searches per day per account (per the Perplexity help center). Free accounts get 5 Pro Searches per day, with unlimited Quick Search. | Switch the model selector to the default Quick Search to keep working without burning Pro quota. Pro quota resets every 24 hours on a rolling window, not at midnight UTC. |
| Rate limited, slow down | Medium | Abuse-prevention layer triggered, common when sending dozens of queries per minute or running scrapers against the public site. Affects the web, API, and iOS app equally because they share the abuse fingerprint. | Stop sending queries for 5 to 10 minutes. If you actually need that volume, switch to the Perplexity Sonar API (sonar-pro or sonar-reasoning) where rate limits are billed and predictable. |
| Failed to load Spaces | Medium | Spaces (the shared workspace feature launched in 2024) depends on the same auth state as the main app. A stale session or a third-party cookie blocker on perplexity.ai will break Spaces while leaving Quick Search intact. | Sign out and sign back in, or open the page in a private window. Safari users should disable Cross-Site Tracking Prevention for perplexity.ai under Settings, Privacy. |
| We couldn't generate an answer | Low | The model that drafts the response (defaults to Sonar; can be Claude 3.7 Sonnet, GPT-4.1, or Gemini 2.5 Pro on Pro) refused or returned an empty completion. Most often a content-policy edge case. | Switch the answer model in the composer (gear icon). Sonar tends to be the most permissive on factual queries; Claude is stricter on persona requests. Rephrase the question if it touches a policy edge. |
| Comet, page failed to render | Medium | Perplexity's Comet browser (released as a public download in 2025) ships its own rendering engine. A handful of sites with aggressive bot detection (Cloudflare Turnstile, Akamai Bot Manager) refuse to render inside Comet on first load. | Click the refresh icon twice; Comet retries with a different user-agent string. If it still fails, the universal escape hatch is to open the URL in your default browser via the 'Open externally' menu. |
| Unable to fetch sources | Medium | Perplexity's web fetch pipeline got robots.txt blocked, captcha walled, or returned a 403 for every candidate URL. Happens disproportionately on queries about gated databases (Bloomberg, FT, academic journals). | Rephrase the query to surface non-gated sources (add 'site:wikipedia.org', 'site:gov', or 'open access') or attach a PDF or URL directly to the chat so Perplexity does not need to fetch. |
| Voice mode microphone not detected | Low | OS-level microphone permission was denied or rotated after a system update. macOS 15.x resets mic permissions for browsers when the OS is upgraded; the same happens on Windows 11 24H2. | macOS: System Settings, Privacy and Security, Microphone, enable for Chrome / Safari / Perplexity. Windows 11: Settings, Privacy and security, Microphone. Reload perplexity.ai after granting. |
| Network error / streaming stopped | Low | The streaming connection dropped mid-answer. Usually a wifi flap, a captive portal kicking in, or an ad blocker filtering an XHR call that the streaming layer needs. | Reload the page. If it repeats, disable uBlock Origin and Privacy Badger for perplexity.ai. Corporate networks that proxy WebSockets sometimes mangle the streaming format; try a personal hotspot to confirm. |
| Account suspended / restricted | High | Abuse-detection flagged the account for one of three things: API-style automation against the public site, repeated content-policy violations, or fraudulent payment. Genuine suspensions arrive with a Trust and Safety email. | Check the email on file (including spam) for a Perplexity Trust and Safety notice. Reply with context. Average response is 2 to 5 business days per the Perplexity help center. Do not create a second account; that escalates to a hardware ban. |
| API: 429 too many requests | Medium | Sonar API hit the per-key rate limit. The default limit is documented in the Perplexity API reference and varies by tier; bursts above 50 requests per second consistently trip the throttle regardless of tier. | Add exponential backoff (start at 1 second, double up to 32) and confirm you are reading the Retry-After header. For sustained volume, request a rate-limit increase from [email protected] with usage projections. |
Four documented incidents shape how to read Perplexity outages in 2026. Each one informed a step in the diagnostic ladder above.
| Date | Duration | Scope | Root cause (source) |
|---|---|---|---|
| Apr 24, 2025 | ~3 hours | Worldwide, Search and Pro Search degraded | Logged on status.perplexity.ai as 'Investigating elevated error rates on Search'. Coincided with a regional AWS us-east-1 networking event reported by AWS Health Dashboard. |
| Feb 13, 2025 | ~90 minutes | Spaces and Library inaccessible; Quick Search worked | Status-page incident titled 'Spaces unavailable'. Auth subsystem issue affected feature gating; classic auth-token rotation aftershock. |
| Jan 20, 2025 | ~6 hours intermittently | DeepSeek R1 release day; search latency elevated globally | Traffic surge after DeepSeek R1 was added to the model picker. Documented in Perplexity status-page incident log; not a code regression. |
| Nov 14, 2024 | ~2 hours | Comet beta render failures (Comet was beta-only at the time) | Browser bundle deploy regressed the Cloudflare Turnstile handshake. Rolled back via hot patch; postmortem summarized in the Comet release notes for the following build. |
Takeaway: Component-scoped incidents (Spaces only, Comet only) are the norm at Perplexity. Always check which row of the status page is yellow before assuming everything is down. If Search is green and only Spaces is broken, the diagnostic ladder still works against the affected surface.
Identify the bucket first; the right fix becomes obvious.
Perplexity infrastructure is degraded. Everyone hitting the affected component is impacted.
Confirmed by
Service is up; your account is in a degraded state. Other accounts on your device work fine.
Confirmed by
Your browser, network, or extension is breaking Perplexity. The same account works on a different device or network.
Confirmed by
All three reach the same web-search-grounded answer surface while Perplexity is unavailable.
OpenAI's web-search surface inside ChatGPT. Free for signed-in users; runs on independent infrastructure from Perplexity.
Free; Plus $20/month
google.com with AI Mode toggled on. Independent stack, separate auth, separate index. Strong fallback for breaking-news queries.
Free; Google AI Pro $19.99/month
Multi-model search assistant. Lets you pick GPT, Claude, or Gemini as the answer model for the same web grounding.
Free tier; Pro from $15/month
One more option: the official Perplexity iOS, Android, and macOS apps. They use a different transport stack than the web app and often work when perplexity.ai is wedged in your browser.
Our verdict
Switch to ChatGPT Search if Perplexity has been down for more than 30 minutes and you need a real-time answer. ChatGPT Search runs on independent infrastructure and almost never goes down at the same time as Perplexity. The grounding quality is close enough for most queries.
Switch to Google AI Mode if the query is breaking news or location-specific (sports scores, store hours, weather). Google's index updates faster than Perplexity's on those categories, and AI Mode reuses the same index.
Stay on Perplexity (and just wait) if the outage is component-scoped (Spaces only or Comet only) and your work is on the unaffected surface. Component outages typically clear in under 90 minutes per the status-page log.
Do NOT switch tools if the issue is the Pro Search 600/day cap. Quick Search is unlimited and uses the same underlying grounding pipeline. Most users do not need Pro Search reasoning on every query, and the model picker is right there in the composer.
Our overall take: Perplexity's reliability in 2025 and 2026 has been comparable to ChatGPT and Gemini. The bigger risk for daily users is the Pro Search quota, not the platform's uptime. If you frequently exhaust 600 Pro Searches in a day, the right move is the Sonar API, not a different consumer tool.
The questions readers ask most when Perplexity refuses to behave.
Keep reading
Research-grade prompts for Perplexity AI's search-powered responses
Read guide →Prompts for AI search engines like Perplexity and Bing AI for research, fact-checking, and deep analysis
Read guide →Stunning image generation with Midjourney prompt mastery
Read guide →Master ChatGPT with advanced prompting techniques, mega-prompts, and proven frameworks
Read guide →Expert guide to Claude prompts with XML tags, artifacts, and complex reasoning
Read guide →Unlock Google's Gemini with multimodal prompting strategies
Read guide →