Perplexity AI Not Working? 9 Fixes That Hold

Perplexity AI not working is rarely one single failure, and the fastest fix in 2026 is to separate a global outage from a local browser, app, network or account problem before you reinstall anything. I found the most useful pattern is simple: check status first, then isolate the device, then isolate the network, then isolate the account. That order saves time because a hard refresh will not repair a server incident, and a status page will not clear a corrupted Chrome cookie.

The stakes are higher than ordinary search downtime because Perplexity now sits across web search, iPhone and Android apps, Comet, Perplexity Computer, enterprise workspaces and the Sonar API. When it breaks, the symptom can look deceptively vague: a blank screen, a frozen answer, a Cloudflare loop, a missing Pro feature, a one-time passcode that never arrives, or a file upload that stalls without a clear error. During our 2026 evaluation, those symptoms usually mapped to one of five root causes: service availability, cached client state, security challenge friction, app version mismatch, or quota and plan limits.

This guide is written for people who need a practical fix now rather than a theory of AI search. I cover browser repair, iPhone and Android recovery, VPN and firewall problems, login issues, pricing limits that masquerade as faults, and developer-facing API bottlenecks. I also include the current commercial matrix, support paths and a repeatable workflow that lets you diagnose Perplexity calmly instead of trying random fixes.

Perplexity ai not working: 9 fixes to try first

Use this ordered checklist before reinstalling anything or changing account settings. It turns the headline promise into a practical diagnostic path and keeps the safest, fastest fixes first.

Perplexity AI not working quick fixes checklist

1. Check the official Perplexity status page and a third-party outage tracker. If both show a wider incident, wait rather than changing local settings.
2. Hard refresh the web page. On Windows use Ctrl + F5. On Mac use Command + Shift + R.
3. Open Perplexity in an incognito or private window to test whether an extension, cookie, or cached script is interfering.
4. Clear only Perplexity site data first. Remove cookies, cached storage, and local permissions for perplexity.ai before clearing the entire browser.
5. Disable browser extensions one by one, especially ad blockers, privacy blockers, script blockers, and AI sidebar tools that inject code into pages.
6. Turn off the VPN, DNS-level ad blocker, strict firewall rule, or corporate proxy for one test session because edge security can block Cloudflare checks.
7. Switch networks. Move from Wi Fi to mobile hotspot, or from mobile data to Wi Fi, to separate device faults from router, ISP, or office-network blocks.
8. Update the browser or mobile app, then restart. On Android, clear app cache before clearing storage. On iPhone, offload or reinstall only after lighter fixes fail.
9. Check sign-in, OTP, and subscription state. Try email login instead of one-click login, confirm the right account, then contact support with device, browser, network, VPN state, exact error, and timestamp.

The best first move is not clearing every cache on your machine. It is triage. Open the official status page, check whether both Website and API are operational, then test Perplexity from a second network such as mobile data. If the service works on your phone but not your desktop, you probably have a browser, extension, DNS or firewall issue. If it fails across every device and third-party reports are rising, the sensible action is to wait, monitor and avoid unnecessary local changes.

In our hands-on testing, the most common user mistake was treating every failure as a local bug. That leads people to reinstall apps, reset passwords and delete browser profiles while the real cause is upstream. The opposite mistake also happens: assuming Perplexity is down globally when a single VPN exit node has triggered repeated Cloudflare checks. Perplexity’s own Help Center warns that VPN use is not recommended because it can trigger Cloudflare security checks and may make the mobile app unusable. That makes VPN status a first-tier diagnostic, not a last resort.

A useful mental model is to classify the symptom before touching settings. A 500-level message suggests server or edge infrastructure. A looping login suggests cookies, blocked email, Apple Relay, or account mismatch. A blank mobile screen suggests app cache, app build, operating-system permission, or network reachability. A hanging answer suggests WebSocket, DNS or content-filter interference. For a deeper adjacent fault pattern, the magazine’s internal error troubleshooting is a useful companion because internal errors often share the same cache, network and server causes.

My rule is strict: do the least destructive fix first. Hard refresh before clearing all browsing data. Disable one extension before uninstalling the browser. Switch network before resetting the router. Offload an iPhone app before wiping device settings. This keeps your thread history, account state and enterprise controls intact while still moving quickly.

What I verified before drafting the guide

This article uses current platform sources rather than recycled forum advice. I checked Perplexity’s official status page, which reported Website and API as operational on 21 June 2026, with no notices in the previous seven days. I also checked StatusGator and Downdetector because they capture user reports that can appear before a provider acknowledges an issue. Third-party trackers are not definitive, but they are valuable when many users suddenly report the same symptom across regions.

For commercial and technical claims, I used official Perplexity pages wherever possible. The Help Center lists the current subscription families: Free Standard, Pro, Max, Education Pro, Enterprise Pro, Enterprise Max and Sonar API. The enterprise pricing page provides current list prices and feature caps, including Pro at $20 monthly or $200 yearly, Enterprise Pro at $40 per seat monthly or $400 yearly, and Enterprise Max at $325 per seat monthly or $3,250 yearly. The developer pricing page lists Search API at $5 per 1,000 requests and Sonar token and request charges by model and context size.

For mobile evidence, I checked the current App Store and Google Play listings. Google Play showed the Android app at 100M+ downloads, a 4.8 rating and 1.98M reviews, with the app updated on 12 June 2026. The App Store listing showed the iPhone app as free with in-app purchases, 4.8 rating and 479K ratings, and a size of 187.5 MB. These details matter because troubleshooting advice changes when an app is actively updated and installed at mass scale.

For infrastructure context, I reviewed Cloudflare’s November 2025 postmortem and subsequent reporting because many Perplexity access problems present as Cloudflare challenges rather than Perplexity error messages. Cloudflare CEO Matthew Prince wrote that any outage of Cloudflare systems is unacceptable, while CTO Dane Knecht publicly said the company had failed customers and the broader internet. Those statements underline a practical point: even sophisticated AI tools depend on ordinary web infrastructure.

Server outage or local fault? Read the signals correctly

A global outage has a different footprint from a local fault. If Perplexity is down globally, the official status page, social reports and monitoring tools usually converge: website, API or login services degrade together, users in different regions report similar symptoms, and retrying from a second device changes nothing. If the fault is local, the pattern is uneven: one browser fails, one Wi Fi network fails, one VPN route fails, or one account fails while another account works.

Perplexity’s official status page is the highest-trust source for acknowledged website and API health. On 21 June 2026 it showed Website and API as operational, with website uptime shown at 99.82 percent and API uptime at 100.0 percent in the visible status module. That does not mean no user can be affected. It means the provider has not declared a current platform incident. StatusGator, by contrast, said it had detected a June 3, 2026 issue that was never officially acknowledged and listed top reported issues such as connectivity, error messages, sign-in problems and app loading failures. That gap is common in edge-case outages.

Cloudflare’s November 2025 outage is the cautionary example. The company said the issue began at 11:20 UTC, was largely resolved for core traffic by 14:30, and was fully restored by 17:06. For users, that kind of edge-network incident may look like Perplexity has failed even when the underlying Perplexity application has not changed. That is why outage diagnosis should include the edge layer, not just the app.

The right response depends on the evidence. When official and third-party status signals both show trouble, preserve your setup and wait. When official status is green and the fault is isolated to one device, move to local repair. When the API is down but the web app is up, separate developer workloads from consumer access. The table below gives a practical reading map.

Signal	Likely cause	What to do first
Official status shows Website/API incident	Global or provider-side fault	Wait, subscribe to status updates, avoid reinstalling apps
Status green but one browser fails	Cache, cookie, extension or browser policy	Hard refresh, private window, disable extensions, clear site data
Works on mobile data but not Wi Fi	Router, DNS, firewall or corporate filter	Switch DNS, disable filtering, test another network
Cloudflare challenge repeats	VPN, blocked script or suspicious IP route	Disable VPN, allow Cloudflare challenge scripts, retry clean browser
Web works but API fails	API key, billing, rate limit or endpoint issue	Check API dashboard, request format, model and status page

Browser fixes for Chrome, Edge and Firefox

Browser issues are the most fixable Perplexity failures because the browser is where stale scripts, blocked cookies, privacy extensions and Cloudflare checks collide. Start with a hard refresh. On Windows, use Ctrl + F5. On macOS, use Command + Shift + R. This forces the browser to fetch fresh assets instead of reusing a broken cached script. If that works, stop there. Do not keep clearing data just because a guide says so.

Next, open Perplexity in a private or incognito window. This is a quick extension isolation test because most extensions are disabled by default in private windows. If Perplexity works there, the culprit is likely an ad blocker, privacy extension, script blocker, corporate browser agent or old site data. Re-enable extensions one by one until the failure returns. In Firefox, hardened tracking protection and DNS-over-HTTPS combinations can create failure modes that resemble a server outage. In Chrome and Edge, aggressive content blockers can interrupt live search requests or challenge scripts.

When private browsing fixes the issue only temporarily, remove site data for Perplexity rather than clearing your entire browser. Delete cookies, cached storage and service-worker data for the Perplexity domain, then sign in again. The adjacent connection timeout guide is relevant when a browser waits indefinitely for a response because timeouts often come from local DNS, proxy or firewall conditions rather than the website itself.

Keep browser and operating-system updates in the workflow, but do them after the quick isolation steps. Updating first is slower and can mask the real cause. In enterprise environments, also check whether managed browser policies are blocking third-party cookies, WebSocket traffic, challenge pages or file uploads. Perplexity is not just a static webpage. It relies on live requests, account state, model selection and retrieved sources. A browser that can load a simple website may still break an AI answer engine.

During our 2026 evaluation, the shortest reliable browser sequence was: hard refresh, private window, extension toggle, site-data deletion, VPN off, DNS switch, update, then alternate browser. Most Perplexity web faults were solved before the final two steps.

Cloudflare, VPNs, DNS filters and corporate networks

Many Perplexity access failures are really network reputation failures. Perplexity’s Help Center states that using a VPN with Perplexity is not recommended because it can trigger frequent Cloudflare security checks and potentially make the mobile app unusable. That single line explains a large share of Cloudflare loops, blank mobile sessions and repeated login challenges. A VPN is useful for privacy in many contexts, but for Perplexity it can look like a risk signal when many users share the same exit IP.

The fix is not simply to abandon privacy tools. It is to test methodically. Turn the VPN off for one session, reload Perplexity, then try a different VPN location if you must use one. If your organisation routes all traffic through a secure web gateway, ask IT whether Cloudflare challenge pages, WebSocket traffic, Perplexity domains or AI tools are being filtered. DNS-level ad blockers can also break the service by blocking challenge scripts, analytics calls used for abuse detection, or file-upload endpoints. A clean mobile-data test is the fastest way to prove whether the local network is involved.

Cloudflare’s own outage history shows why edge security can look like application failure. In its November 2025 postmortem, Cloudflare said a change to database permissions generated a larger-than-expected Bot Management feature file that caused routing failures across its network. Matthew Prince wrote that any outage of Cloudflare systems is unacceptable, and CTO Dane Knecht said, “we failed our customers and the broader Internet.” For a Perplexity user, the practical lesson is that a Cloudflare-branded error is not always caused by your account or by Perplexity itself.

Corporate networks add one more layer. Finance, healthcare, legal and education networks increasingly classify AI tools separately from ordinary websites. That can produce partial failures: login loads, but search stalls; chat works, but file upload fails; mobile app opens, but account sync never completes. I recommend capturing the exact error text, network type, VPN state, browser, and device before contacting support. That evidence helps distinguish a platform incident from a firewall policy.

Mobile app crashes: iPhone, Android and Samsung edge cases

Mobile troubleshooting depends on the operating system. Android gives users direct access to app cache and storage controls. iPhone does not offer the same universal cache-clearing path, so the equivalent repair is usually force quit, offload, update, or reinstall. Treat those differences as normal platform behaviour, not as a sign that one app version is uniquely broken.

For Android, force stop the app, reopen it, then clear cache if the blank screen returns. If login or thread loading remains broken, clear storage only after confirming you know your sign-in method. Then update from Google Play. Google Play currently lists the Perplexity Android app as 100M+ downloads, rated 4.8, with 1.98M reviews and an update date of 12 June 2026. That scale means review spikes can be noisy, so trust repeatable symptoms on your own device more than one-off comments.

For iPhone, force quit the app, restart the phone, then check the App Store for updates. The App Store listing shows Perplexity as a free iPhone app with in-app purchases, a 4.8 rating from 479K ratings, and a 187.5 MB app size. If the app crashes after an update, offload it through iPhone Storage, reinstall, and sign in again. Users who rely on Apple Relay or Hide My Email should confirm that sign-in emails are forwarding properly. For a wider setup context, the magazine’s iPhone setup guide explains the iOS app experience, while the Android setup guide covers Android assistant and setup behaviour.

Samsung devices need special attention because Samsung’s own support guidance says a pre-installed Perplexity app on Galaxy phones may have to be updated through Galaxy Store, and if a user tries Google Play and sees installation problems, uninstalling and reinstalling can be required. That is a platform distribution issue, not a model failure.

The table below shows the safest mobile order. It deliberately delays deletion until lighter fixes have failed.

Device or app path	Likely symptom	Fix order
iPhone 15 after update	Crash on launch or frozen splash screen	Force quit, restart iPhone, update, offload app, reinstall
Android phone	Blank screen or stale session	Force stop, clear cache, switch network, update, clear storage only if needed
Samsung pre-installed app	Update unavailable or Play Store conflict	Check Galaxy Store, then uninstall/reinstall if instructed
Any mobile app on VPN	Cloudflare loop or unusable app	Disable VPN, retry on mobile data, then change VPN route
Login email missing	OTP never arrives	Check spam, allow sender, verify address, test another connection

Account sign-in, OTP and subscription mismatch fixes

A Perplexity login problem can look like an outage because the app may load but never restore your library, Spaces, Pro features or previous threads. Start with the identity layer. Confirm whether you originally signed in with email, Google, Apple, or another single sign-on method. Then use the same method on every device. Switching between Apple private relay, Google one-click and email OTP can create the impression that your subscription disappeared when you are actually in a different account.

Perplexity’s help article on missing one-time passcodes tells users to check spam or junk folders, whitelist the sender team@mail.perplexity.ai, verify the email address, and check the internet connection. It also lists support@perplexity.ai as the contact point when sign-in emails still do not arrive. That advice is simple, but it matters because many support tickets start with the wrong email address or a blocked forwarding route. Apple Relay and corporate email filters are common suspects.

Subscription mismatch is the next account-level issue. Perplexity’s Help Center says the Free plan has practically unlimited basic searches, a very limited amount of Pro Searches, basic file uploads and no advanced AI models, image generation or premium support. Pro adds extended Pro Search access, advanced models, image and video generation, higher file and attachment limits, exclusive support channels and up to 50 file uploads per Space. Education Pro includes Pro features at a verified discount. Max adds the highest access to advanced models, early products, extended file and app creation, Brain preview and priority support.

That means a missing feature is not always a bug. It may be a plan boundary, a weekly limit, or a web-only capability. The free plan walkthrough is helpful for users trying to distinguish broken access from normal free-tier behaviour, while the Pro versus free comparison provides a practical upgrade decision for people who keep hitting usage limits.

Before contacting support, collect four facts: account email, sign-in method, platform, and exact missing feature. Support can act faster when the report distinguishes sign-in failure from billing mismatch, account duplication, or a genuine platform fault.

Pricing, limits and feature caps that can look like faults

Perplexity’s commercial structure can mislead users because the same brand covers consumer search, mobile apps, enterprise workspaces, Comet, Computer and the API. A user may say Perplexity is not working when the real issue is a plan limit. A developer may think Pro includes API usage when the Help Center states API access is pay as you go and does not provide advanced web-app models or Pro features inside the interface. An enterprise user may have features controlled by admin policy even when the plan includes them generally.

The public enterprise pricing page and Help Center currently show a broad matrix. Pro is listed at $20 per month or $200 per year. Enterprise Pro is $40 per month per seat or $400 per year, while Enterprise Max is $325 per month per seat or $3,250 per year. Annual pricing is displayed elsewhere on the same enterprise page as $17 per month for Pro, $34 per month per seat for Enterprise Pro, and $271 per month per seat for Enterprise Max when billed annually. This is not a contradiction if interpreted as annualised monthly equivalent versus standard monthly billing, but it can confuse buyers.

The important support point is that limits differ by plan and context. Enterprise Max can host 10,000 files in My Files and 5,000 files per Space, while Enterprise Pro includes organisation file repository and internal knowledge search. File uploads in threads remain subject to separate limits, and persistent files can have additional controls. The magazine’s 2026 pricing breakdown is useful background for readers comparing these plan layers, while the file upload guide helps separate file-cap limits from actual upload failure.

Use the table below as a troubleshooting matrix, not as purchase advice. Pricing changes, so always verify inside the live Perplexity billing screen before making a commercial decision.

Plan or product	Public price signal	Limits that may look like faults
Free Standard	$0	Very limited Pro Searches, basic uploads, no advanced models or premium support
Pro	$20/month or $200/year	Higher search and file limits, but still separate from API billing
Education Pro	$10/month with verification	Requires student or educator verification via SheerID
Max	$200/month or annual option where available	Advanced models, early access and priority support, but not unlimited API
Enterprise Pro	$40/seat/month or $400/year	Admin controls, SSO/SCIM, internal knowledge, organisation limits
Enterprise Max	$325/seat/month or $3,250/year	Highest enterprise limits, 10,000 My Files, 5,000 files per Space

API, Sonar and developer troubleshooting

Developer failures need a separate diagnostic path. The Perplexity web app can be operational while your API call fails because the API key is invalid, billing credit is exhausted, a request parameter is wrong, the selected model is unavailable, a context fee is higher than expected, or your application mishandles streaming. The developer docs state that the Search API charges $5 per 1,000 requests with no token costs. Sonar API pricing combines token costs with request fees that vary by search context size for Sonar, Sonar Pro and Sonar Reasoning Pro.

The current token table lists Sonar at $1 per million input tokens and $1 per million output tokens. Sonar Pro is $3 input and $15 output per million. Sonar Reasoning Pro is $2 input and $8 output per million. Sonar Deep Research is $2 input, $8 output, $2 citation tokens, $5 per 1,000 search queries and $3 reasoning tokens per million. Request fees by context size are $5, $8 and $12 per 1,000 for Sonar, and $6, $10 and $14 per 1,000 for Sonar Pro and Sonar Reasoning Pro. Pro Search on Sonar Pro can raise request fees to $14, $18 or $22 per 1,000 depending on context size.

That complexity can look like a malfunction when it is actually cost classification. In a June 2026 CNBC interview reported by Business Insider, Aravind Srinivas said that if an open-source model gets the job done 90 percent of the time, he would probably use it if it were 10 to 20 times cheaper than a frontier model. For developers, that quote is a reminder to design fallbacks, budget caps and model routing rather than calling the most expensive search mode for every query.

When we integrated this API pattern during our 2026 evaluation, the practical failures were mundane: missing stream handling, overlarge prompts, unbounded citation costs, and assuming a consumer subscription covered API calls. Log request IDs, model name, context size, token counts, response code and wallet balance before filing a support issue.

API component	Official price or rule	Troubleshooting implication
Search API	$5 per 1,000 requests	No token costs, so failures usually involve key, endpoint, filters or billing
Sonar	$1 input and $1 output per 1M tokens plus context request fee	Cheap base model still needs context fee checks
Sonar Pro	$3 input and $15 output per 1M tokens plus request fee	Output-heavy prompts can cost more than expected
Sonar Reasoning Pro	$2 input and $8 output per 1M tokens plus request fee	Reasoning workloads need latency and cost monitoring
Sonar Deep Research	Token, citation, search-query and reasoning charges	Budget controls are essential for multi-step research workflows
Pro Search on Sonar Pro	Fast, pro or auto search type with varying fees	Auto classification can make costs appear inconsistent

Step-by-step workflow for Windows, Mac, iPhone and Android

A repeatable workflow matters because random troubleshooting destroys evidence. For a Windows laptop on Chrome, start with Ctrl + F5, then test Incognito, then disable extensions, then clear site data only for Perplexity. Next, turn off VPN and DNS-level blocking. Then test Edge or Firefox. If every browser fails on the same network but mobile data works, escalate to DNS, firewall or router settings. If every network fails, return to status monitoring.

For macOS and Safari or Chrome, use Command + Shift + R, private browsing, extension isolation and site-data removal. macOS users should also check content blockers, iCloud Private Relay, DNS profiles and device-management profiles. In corporate fleets, a managed browser profile can block scripts or cookies while a personal browser profile works. That is an IT policy clue, not a Perplexity bug.

For iPhone, close the app from the app switcher, reopen, restart the phone, update from the App Store, offload the app, reinstall, then sign in with the same identity provider used on desktop. If the problem began immediately after an app update, search for current review clusters but do not rely on one review as proof. Test on Wi Fi and mobile data. If Apple Relay is involved in sign-in, confirm mail forwarding. If an OTP never arrives, whitelist the Perplexity mail sender and retry from another connection.

For Android, force stop, clear cache, switch network, update, then clear storage or reinstall only when lighter fixes fail. If the device is Samsung and the app came pre-installed, check Galaxy Store because Samsung guidance says some pre-installed Perplexity app updates are handled there rather than through Google Play.

For all platforms, record the precise state after every step. The useful log is short: date and time, device, app or browser version, network, VPN state, error text, status page state, and whether another device works. A five-line log often beats a long emotional support ticket.

Known bottlenecks and 2026 information gain

Three details rarely appear in basic troubleshooting posts, but they change the diagnosis. First, Cloudflare challenge failures are not binary. A browser may pass the initial challenge, then fail a later request when a script, storage call or background connection is blocked. That produces partial loading rather than a clean error. The practical fix is to allow the challenge domain and test with privacy extensions disabled rather than only refreshing the visible page.

Second, plan limits can look like silent product degradation. A user who moves from desktop to mobile may think the app is broken because advanced models, Pro Search volume, file upload limits, Spaces, Research mode or Computer features differ by plan, device, enterprise policy and current rollout. Check the feature itself against the plan table before assuming the app failed. In particular, API access remains commercially separate from web and app subscriptions, which is a common surprise for builders.

Third, outage signals are often layered. The official status page is authoritative for acknowledged incidents, but third-party reports can reveal localised or short incidents that never become official notices. StatusGator listed a June 3, 2026 account-data-loading issue as detected but never acknowledged. That does not prove a platform-wide failure, but it explains why some users can experience a real disruption while the official page remains green.

During our 2026 evaluation, I also found that the fastest non-destructive test was not reinstalling anything. It was a clean comparison: same account, different browser, same device, different network, then different device, same network. This isolates browser state, network state and account state in minutes. If Perplexity works in those comparison tests, the platform is not globally down. If every axis fails and reports rise, the user has enough evidence to pause local repair and monitor status.

The durable skill is not memorising every fix. It is learning to ask which layer failed: Perplexity service, Cloudflare edge, browser storage, network policy, app build, identity provider, subscription limit, or API billing.

When to contact Perplexity support and what to include

Contact support after you have separated platform, network, browser, app and account causes. That does not mean spending hours on fixes. It means doing a minimal evidence pass so the support team receives a report they can act on. Perplexity’s Help Center lists support@perplexity.ai for sign-in email problems, and the developer documentation points API users toward community and support channels. Enterprise customers should use their contracted support path or admin channel because workspace and security policies may not be visible to individual users.

A useful support note contains the symptom, scope and proof. Symptom means the exact error or behaviour, such as Cloudflare loop, blank screen, 500 error, missing OTP, missing Pro feature, frozen upload or failed API request. Scope means where it happens: Chrome on Windows, Safari on iPhone, Android app, Comet, API, one account, one network, or every device. Proof means time, screenshots, request IDs, app version, browser version, VPN state and status-page reading.

Do not send passwords, secret API keys, private documents or unnecessary personal data. If reporting an API issue, include redacted request shape, endpoint, model, response code, request ID and billing state. If reporting a mobile crash, include device model, operating system version, app build if visible, whether reinstall changed anything, and whether it works on another network. If reporting enterprise issues, include workspace name, affected seats, SSO provider, SCIM or data retention policy only if relevant and safe to share through the approved support channel.

The threshold for contact is simple. If status is green, the app fails on multiple clean networks, reinstall or clean browser state does not help, and the same account fails across devices, contact support. If status is red or user reports are surging, wait for the incident to settle unless the issue is account-specific or business-critical.

Alternatives and continuity planning while Perplexity is unavailable

A troubleshooting article should not pretend uptime is the only answer. Professionals who rely on Perplexity need a continuity plan for the minutes or hours when it is unavailable. The plan should match the task. For quick web answers, use a second search engine or another AI search tool. For academic work, move the source-discovery stage to Google Scholar, PubMed, Semantic Scholar or a library database, then return to Perplexity for synthesis when service resumes. For coding, use a local IDE assistant or another model provider. For enterprise workflows, maintain a documented fallback for research, citation capture and file analysis.

Continuity planning matters because Perplexity increasingly sits in workflows beyond casual question answering. Reuters reported that Perplexity was in discussions with mobile device makers to pre-install Comet, and Aravind Srinivas said it is not easy to persuade mobile original equipment manufacturers to change defaults from Chrome. He also said the company aimed to reach tens to hundreds of millions of users after stabilising the desktop version. Those ambitions make availability, browser defaults and mobile reliability business issues, not minor app inconveniences.

The best fallback is not a panic switch. It is a small checklist saved outside Perplexity: official status page, third-party status tracker, support contact, alternate browser, alternate network, alternate search tool and a note on which account identity you use. Keep critical sources in a reference manager or workspace that survives an app outage. Export important answers when they become part of paid work or regulated research.

Perplexity is valuable because it compresses search, reading and synthesis. That value also creates dependency. A resilient user treats it as the primary research layer, not the only research layer. When the service returns, you can move back without losing momentum.

Takeaways

• Check the official status page before changing local settings, especially if Perplexity fails across every device.
• Use one clean comparison test: same account on another browser, then same device on another network.
• Turn off VPN or security routing early because Perplexity warns that VPNs can trigger Cloudflare checks and break mobile access.
• Fix browsers in the lightest order: hard refresh, private window, extension isolation, site-data deletion, then update.
• Fix iPhone crashes with force quit, restart, update, offload and reinstall; fix Android with force stop, cache clear, update and storage clear only if needed.
• Treat missing Pro features as a possible plan, account or admin-policy issue before assuming the app is broken.
• For API failures, log model, endpoint, context size, response code, request ID, token usage and billing state.
• Contact support only after collecting device, browser, network, VPN, account and error details so the ticket is actionable.

Our Content Testing Methodology

This troubleshooting guide was compiled through empirical failure mapping, live-source verification and reproducible 2026 repair workflows. I checked Perplexity’s official status page, Help Center, enterprise pricing page, Sonar API pricing documentation, App Store listing, Google Play listing, Samsung support guidance for Galaxy app update issues, Cloudflare’s outage postmortem, StatusGator, Downdetector and current reporting on Perplexity’s browser and business direction. During our 2026 evaluation, the editorial workflow replicated the main fault classes discussed here: stale browser state, extension interference, VPN or Cloudflare challenge friction, mobile app reset paths, sign-in email failures, subscription-limit confusion and API billing or request-format errors. Each fix is ordered from least destructive to most destructive, so readers can preserve account state, thread history and enterprise controls wherever possible. Pricing, limits and status observations reflect the sources available on 22 June 2026 and should be rechecked before commercial or enterprise decisions.

Conclusion

Perplexity will keep becoming more than a search box. Its 2026 product surface spans web, mobile, Comet, Computer, enterprise workspaces and API infrastructure, so future failures will not always be obvious. A blank page may be cache. A Cloudflare screen may be VPN routing. A missing model may be a plan boundary. A stalled answer may be DNS filtering. A failed API call may be billing or context pricing rather than downtime.

The healthy response is structured troubleshooting. Start with status, then isolate browser, network, device, account and plan. Use the least destructive fix that tests the likely layer. Preserve evidence before support contact. Keep a fallback search and citation workflow for professional use.

The open question is how transparent AI answer engines will become when partial degradations affect only specific regions, models, networks, or enterprise policies. Traditional status pages were designed for web and API uptime, not for model routing, agentic browsing and retrieval quality. Until those signals mature, the user’s best defence is a disciplined diagnostic routine. The future of AI search may be conversational, but fixing it still depends on careful, ordinary systems thinking.

FAQs

Why is Perplexity AI not loading?

The most common causes are server incidents, cached browser data, extension interference, VPN or Cloudflare checks, DNS filtering, or an outdated mobile app. Check the official status page first, then test another browser and network.

How do I know if Perplexity is down for everyone?

Check Perplexity’s official status page first, then compare with Downdetector or StatusGator. If multiple regions report the same problem and your phone, desktop and another network all fail, it is more likely to be a wider incident.

Why does Perplexity show a Cloudflare error?

Cloudflare errors usually mean the security challenge, network reputation, blocked scripts, VPN route, or Cloudflare itself is involved. Disable VPN, allow challenge scripts, try a clean browser, and test mobile data.

Why does Perplexity work on my phone but not my computer?

That pattern usually points to your desktop browser, extensions, cookies, DNS, firewall, or VPN. Try a hard refresh, private window, extension isolation, site-data clearing, and a different desktop browser.

How do I fix the Perplexity iPhone app crashing?

Force quit the app, restart the iPhone, update from the App Store, then offload and reinstall if needed. After reinstalling, sign in using the same method you used on desktop.

How do I fix a blank screen on Android?

Force stop the app, clear cache, switch between Wi Fi and mobile data, update from Google Play or Galaxy Store where applicable, then clear storage or reinstall if lighter steps fail.

Can a VPN stop Perplexity from working?

Yes. Perplexity says VPN use is not recommended because it can trigger Cloudflare checks and may make the mobile app unusable. Test once with VPN off before making deeper changes.

Who do I contact if nothing works?

For general sign-in email problems, Perplexity lists support@perplexity.ai. Enterprise users should use their organisation’s contracted support path. Include device, browser, app version, network, VPN state and exact error text.

References

Apple. (2026). Perplexity – AI Search & Chat. App Store. https://apps.apple.com/us/app/perplexity-ai-search-chat/id1668000334

Cloudflare. (2025, November 18). Cloudflare outage on November 18, 2025. Cloudflare Blog. https://blog.cloudflare.com/18-november-2025-outage/

Downdetector. (2026). Perplexity AI down? Current problems and outages. https://downdetector.pk/en/status/perplexityai/

Google Play. (2026). Perplexity – Ask Anything. Google Play. https://play.google.com/store/apps/details?id=ai.perplexity.app.android

Perplexity. (2026). Perplexity – Status Page. https://status.perplexity.com/

Perplexity. (2026). Pricing. Perplexity API Documentation. https://docs.perplexity.ai/docs/getting-started/pricing

Perplexity. (2026). Which Perplexity subscription plan is right for you? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/11187416-which-perplexity-subscription-plan-is-right-for-you

Perplexity. (2026). Account management and security. Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/10352998-account-management-and-security

Sriram, A. (2025, July 18). Perplexity in talks with phone makers to pre-install Comet AI mobile browser on devices. Reuters. https://www.reuters.com/business/perplexity-talks-with-phone-makers-pre-install-comet-ai-mobile-browser-devices-2025-07-18/