GPTPrompts.AI

Perplexity AI Not Working? 11 Fixes That Actually Work

GPTPrompts.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.

Check Perplexity statusJump to error matrixChatGPT not working?

How we tested this

Reproduced 11 Perplexity error states across 4 browsers and the iOS app in May 2026

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.

The 11-step diagnostic, in order of likelihood

Work top to bottom. The earliest steps fix the largest share of cases, so do not skip ahead.

1

Check status.perplexity.ai first

30 seconds

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.

2

Hard refresh the page

10 seconds

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.

3

Open an incognito or private window

1 minute

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.

4

Toggle the VPN and disable corporate proxies

1 minute

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.

5

Sign out and sign back in

1 minute

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).

6

Clear cookies and site data for perplexity.ai

2 minutes

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.

7

Try the native iOS, Android, or macOS app

2 minutes

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.

8

Switch the answer model

30 seconds

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.

9

Flush DNS

1 minute

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.

10

Verify account and billing status

2 minutes

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.

11

Contact support

5 minutes

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

What surprised us while reproducing every error

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.

Error matrix, match the message to the fix

11 exact error strings Perplexity shows, the root cause behind each, and the action that resolves it.

ErrorSeverityRoot causeFix
Search failed, please try againLowThe 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 limitMediumPerplexity 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 downMediumAbuse-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 SpacesMediumSpaces (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 answerLowThe 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 renderMediumPerplexity'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 sourcesMediumPerplexity'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 detectedLowOS-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 stoppedLowThe 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 / restrictedHighAbuse-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 requestsMediumSonar 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.

Perplexity incident history, what the status-page log shows

Four documented incidents shape how to read Perplexity outages in 2026. Each one informed a step in the diagnostic ladder above.

DateDurationScopeRoot cause (source)
Apr 24, 2025~3 hoursWorldwide, Search and Pro Search degradedLogged 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 minutesSpaces and Library inaccessible; Quick Search workedStatus-page incident titled 'Spaces unavailable'. Auth subsystem issue affected feature gating; classic auth-token rotation aftershock.
Jan 20, 2025~6 hours intermittentlyDeepSeek R1 release day; search latency elevated globallyTraffic 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 hoursComet 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.

Every Perplexity failure falls into one of three buckets

Identify the bucket first; the right fix becomes obvious.

1. Service-side

Perplexity infrastructure is degraded. Everyone hitting the affected component is impacted.

Confirmed by

  • Yellow or red row on status.perplexity.ai
  • Spike on downdetector.com for Perplexity
  • @perplexity_ai post on X

2. Account-side

Service is up; your account is in a degraded state. Other accounts on your device work fine.

Confirmed by

  • Another account works in same browser
  • Pro Search quota banner visible
  • Billing or suspension email in inbox

3. Device-side

Your browser, network, or extension is breaking Perplexity. The same account works on a different device or network.

Confirmed by

  • Works in incognito or on phone hotspot
  • iOS or macOS app works while web fails
  • Issue follows the browser, not the account

If Perplexity stays broken, three working alternatives

All three reach the same web-search-grounded answer surface while Perplexity is unavailable.

ChatGPT Search

OpenAI's web-search surface inside ChatGPT. Free for signed-in users; runs on independent infrastructure from Perplexity.

Free; Plus $20/month

Google AI Mode

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

You.com

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

When to stop troubleshooting and switch tools

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.

Frequently asked questions

The questions readers ask most when Perplexity refuses to behave.

How do I check if Perplexity AI is down right now?
Open status.perplexity.ai, that is the authoritative source. Search, Pro Search, Spaces, Comet, and the Sonar API are each tracked as separate components, so partial outages are common. If only Spaces is yellow but Search is green, Quick Search will work even though Spaces refuses to load. Subscribe to email or webhook updates on the status page so you learn about incidents before they cost you an hour of debugging.
Why does Perplexity say 'Search failed, please try again'?
That message means the retrieval layer (the part that crawls and selects sources) returned nothing usable, or the answer model timed out grounding the response. It is the most common transient error and rarely indicates an outage. Click the rerun arrow once, and if it persists, rephrase the query with one or two additional keywords so the retriever can lock onto stronger source pages. Niche, ambiguous, or time-bound queries trip this most often.
What is the Pro Search daily limit and what happens when I hit it?
Perplexity Pro is capped at 600 Pro Searches per 24 hours per the Perplexity help center, on a rolling window, not a UTC midnight reset. Free accounts get 5 Pro Searches per day. When you hit the cap, the composer auto-switches to Quick Search and shows a quota banner; Quick Search remains unlimited on every tier. Pro Search reasoning is what burns through quota the fastest; if you mostly want web search, Quick Search is the right default.
Does Perplexity work behind a VPN?
Mostly yes, but residential proxies and free VPN tiers share IP ranges with abuse traffic. Cloudflare's WAF (which fronts perplexity.ai) silently 403s those ranges, and the error you see is a generic 'access denied' or a captcha that never resolves. Premium business VPNs with dedicated IPs (Mullvad multihop, NordLayer dedicated IP, Tailscale exit nodes on residential IPs) generally pass. The quickest confirmation is to disable the VPN and reload.
Why are my Spaces blank or not loading?
Spaces leans on a separate auth check from Quick Search. A stale session token, a third-party cookie blocker (Safari ITP, Brave Shields), or a cleared cookie store will break Spaces while leaving Quick Search untouched. Sign out and sign back in, allow cookies for perplexity.ai, or open the Space in an incognito window. The Feb 13, 2025 outage is the canonical example: Spaces was offline for 90 minutes while Quick Search ran normally.
Why does Perplexity's Comet browser fail to render some sites?
Comet ships its own Chromium build with custom network handling for the AI overlay. A small set of sites with aggressive bot detection (Cloudflare Turnstile, Akamai Bot Manager, PerimeterX) refuse to render inside Comet on first load. Refreshing twice usually unsticks it, and Comet ships a one-click 'Open externally' option in the page menu that punts the URL to your default browser. Comet became a public download in 2025 and is still earlier in the bot-detection cat-and-mouse cycle than Chrome.
What is the fastest way to confirm the issue is on my side, not Perplexity's?
Open perplexity.ai in an incognito window on a different network (phone hotspot is fastest). Sign in fresh. If it works in incognito on cellular, the issue follows your normal profile or your home network. Three suspects in that order: a browser extension dropping requests, a corrupt cookie or service worker, a router or DNS misconfiguration. This single test eliminates roughly two thirds of guesswork.
Why does the Perplexity iOS or Android app work when the website does not?
The native apps connect through a separate transport stack and do not pass through your browser's extensions, cookies, or service worker. If the web app is wedged by a stale auth token or a rogue ad blocker, the mobile app sidesteps all of it. The reverse also occurs: a mobile build regression can leave the app broken while the web app keeps running. Always test both surfaces before declaring an outage.
Why am I being rate-limited even though I am on Pro?
Pro raises your daily Pro Search cap to 600 and removes most Quick Search throttles, but it does not exempt you from the abuse-prevention layer. Sending 50 queries per minute (such as a script or a tab that auto-refreshes) trips the 'Rate limited, slow down' guardrail regardless of tier. If you genuinely need high volume, the Sonar API (sonar-pro, sonar-reasoning) is the supported path; the public web app is not intended for automation.
Will clearing my Perplexity cookies delete my Spaces or Library?
No. Spaces, Library, and Threads are all stored server-side under your account. Clearing cookies for perplexity.ai logs you out and removes local state; signing back in restores everything. The only thing you can lose is an unsent prompt in the composer. To be safe, paste any drafted query into a notes app before clearing site data.
Why is Perplexity's answer empty or cut off in the middle of a sentence?
Three common reasons. First, the answer model refused part of the response on content policy (try switching models in the composer; Sonar tends to be the most permissive on factual queries, Claude is stricter on persona work). Second, the streaming connection dropped mid-response, common over flaky wifi. Third, you hit a Pro Search budget within a single complex query; long reasoning answers occasionally truncate at the budget ceiling. Rerun the query and pick a different model if the cut happens again.
How long do Perplexity outages usually last?
Looking at the public status-page incident log, most Perplexity incidents resolve in 30 minutes to 3 hours. The April 24, 2025 Search-degradation event was around 3 hours and was tied to an AWS us-east-1 networking issue. The longest documented Spaces-only outage in 18 months was 90 minutes on Feb 13, 2025. Multi-day platform outages have not occurred; if a single component appears broken for more than 4 hours, it is usually account-side, not service-side.
Why is the Perplexity Sonar API returning 429 errors even at low volume?
Two usual causes. First, the per-key rate limit varies by API tier and is per minute, not per second, so a burst of 50 requests in a single second still trips the throttle even though your hourly volume looks low. Second, the abuse-prevention layer treats the public web app and the API as overlapping fingerprints; if your IP is also driving web traffic, both layers count. Add exponential backoff, respect Retry-After, and request a rate-limit increase from [email protected] with usage projections if you need sustained throughput.

Keep reading

More AI troubleshooting and prompt guides

Browse all guides →

Don't stop here

What to read next

Hand-picked guides our readers explore right after this one.

Most relevant

Perplexity Prompts

Research-grade prompts for Perplexity AI's search-powered responses

Read the guide
Editor's pick

Gemini Prompts

Unlock Google's Gemini with multimodal prompting strategies

Read the guide
Discover

Lovable AI Prompts

Build full-stack web apps with Lovable AI using effective prompts for SaaS, dashboards, and landing pages

Read the guide