Is Perplexity AI down?

Understanding Perplexity AI availability

Perplexity AI can be partly available while a specific function is degraded. The website may load even when sign-in, searching, answer generation, or individual requests are slow or failing. A problem limited to one device or connection is more likely local; the same failure across separate browsers, devices, or networks is stronger evidence of a broader service issue.

Check the official Perplexity status page for provider-reported incidents. If it shows no incident, compare the result on another device or network before changing settings.

• Wider service issue: Perplexity fails across independent devices or networks, or the official status page reports an incident.
• Browser or session issue: The site works in a private window or another browser, but a particular tab or sign-in session fails.
• Network or DNS issue: Perplexity fails only on one connection and the error mentions DNS, a timeout, or another connection problem.
• Request-specific issue: The page opens, but one search, conversation, or answer remains stuck or returns an error.

Troubleshooting Perplexity AI problems

Check for a wider outage first

Open the official Perplexity status page. If it reports an incident affecting the website or a related function, the problem is likely service-side. Note the incident details and wait for an update rather than repeatedly changing browser settings.

If no incident is listed, test Perplexity on another device or network. This can reveal a partial issue affecting a particular provider, region, or connection path.

If Perplexity will not load

• Reload the page once, then try a private or incognito window.
• Temporarily disable extensions that alter scripts, privacy settings, or network requests.
• Clear Perplexity site data if the page is stuck in a reload loop or an old session appears corrupted.
• Try an updated browser and check whether other websites load normally.

If Perplexity works in a private window or another browser on the same device, the original browser profile, cached data, cookies, or an extension is the more likely cause.

If sign-in or an existing session fails

Try signing in through a fresh private window or another browser. If that works, the original session, cookies, or an extension is probably interfering. If sign-in fails across browsers and devices, compare the symptom with the official status page and test another network.

Do not repeatedly submit an account action that appears slow or incomplete. First confirm whether the previous attempt succeeded.

If searches or answers are slow or fail

Confirm whether the main site loads. If it does, wait briefly and try one short, new request. Note whether every request fails or only one conversation or query is affected. A failure across devices suggests a service-side problem; a single stuck conversation points more toward a session or request-specific issue.

If you see DNS, timeout, or connection errors

• DNS error: Test another network and compare whether the domain resolves there. Avoid changing DNS settings immediately if other devices on the same connection fail too.
• Connection timeout: Try a different connection, such as mobile data, to distinguish your network path from Perplexity availability.
• Connection refused or gateway error: Check the official status page and retry later; the failure may occur between your connection and the service.
• Certificate or redirect warning: Stop and do not bypass the browser’s security protection. Confirm that you are using the intended Perplexity website address.

If you use a programmatic integration

No separate API domain or API status URL is included for this service. For an integration failure, preserve the exact response, timestamp, request path, and whether the website works. Consult the provider documentation or support channel associated with that integration instead of assuming a website outage explains every API error.