Perplexity 'Something Went Wrong': API Failures and Service Timeouts Fixed

Step-by-Step Fix

1. Wait 30 to 60 seconds and retry

Unlike query-content errors that repeat reliably, 'Something Went Wrong' is usually a transient technical failure. The correct first response is to wait rather than immediately troubleshoot.

1. Do not retry the query immediately — rapid retries during a backend failure overload an already stressed system and are unlikely to succeed.
2. Wait 30 to 60 seconds. Use the time to review what you were researching or prepare your next follow-up question.
3. Submit a simple test query first: something generic like "What is machine learning?" If this succeeds, the error was isolated to the previous request.
4. If the test query also fails, the issue is broader than a single failed request. Move on to the next diagnostic step.

2. Refresh your browser session

A dropped or corrupted WebSocket or HTTP streaming connection is a common cause of this error. A fresh page load re-establishes the connection.

1. Close the current Perplexity browser tab completely.
2. Open a new tab and navigate directly to perplexity.ai.
3. Do not use the Back button or a cached page — load the site fresh from the address bar.
4. Sign in again if your session has expired and submit a test query.
5. A fresh session re-establishes all connection channels, which resolves streaming-related failures.

3. Test on a different network

Network instability — especially on mobile data, shared Wi-Fi, or VPN connections — can interrupt the streaming connection Perplexity uses to deliver results, producing this error.

1. Switch from your current network to a different one: from Wi-Fi to mobile hotspot, or from a corporate network to a personal connection.
2. If you use a VPN, disable it entirely and test on a direct connection.
3. Navigate to perplexity.ai and submit a test query on the new network.
4. If the error disappears on a different network, your original network or VPN is causing the streaming connection to drop. Consider switching VPN servers or disabling the VPN for Perplexity sessions.

4. Check perplexity.ai/status for service incidents

Backend failures that affect many users simultaneously appear on the official status page, usually within a few minutes of detection.

1. Open perplexity.ai/status in a new tab.
2. Look for any active incidents mentioning "search," "API," "model," or "performance."
3. If an incident is active, read the latest update to understand the estimated resolution time. Subscribe to updates via email on the status page.
4. Check Twitter/X for @perplexity_ai for real-time communication about ongoing incidents, including workarounds the team may share.
5. If no incident is listed, the failure may be isolated to a specific server region or a small subset of users — proceed with the remaining diagnostic steps.

5. Test in an incognito window with extensions disabled

Browser extensions can interfere with Perplexity's streaming API in ways that produce 'Something Went Wrong' errors:

1. Open a new incognito/private window (all browser extensions are disabled by default in this mode).
2. Navigate to perplexity.ai and sign in.
3. Submit your query. If it succeeds in incognito but fails in your normal window, a browser extension is breaking the connection.
4. Return to your normal window and disable extensions one at a time to identify the culprit. Common causes: ad blockers (uBlock Origin, AdBlock Plus), privacy extensions (Privacy Badger, Ghostery), VPN browser extensions, and script blockers.

6. Try a different browser

If the issue persists across incognito modes, the problem may be at the browser engine level.

1. If you normally use Chrome, try Firefox or Edge (or vice versa).
2. If you have Safari on macOS, test there — Safari's networking stack is distinct from Chromium-based browsers.
3. Submit the same query in the alternative browser.
4. If the error resolves in a different browser, your main browser has a configuration or update issue affecting its streaming capabilities. Updating the browser or resetting it to default settings may fix the problem in your preferred browser.

7. Use the Perplexity mobile app as a fallback

If the web browser version is consistently failing, the iOS or Android mobile app routes through a different networking path and may not be affected by whatever is causing the web error.

1. Open the Perplexity app on your mobile device (available on the App Store and Google Play).
2. Sign in with the same account.
3. Submit the query that failed on desktop.
4. If it works on mobile, continue your research session there. The web version will typically recover within 30 to 60 minutes as Perplexity's infrastructure stabilizes.

Why This Happens

"Something Went Wrong" is Perplexity's generic error message for backend technical failures — API calls that return unexpected status codes, model endpoints that exceed their response timeout (typically 30 to 60 seconds), web retrieval services that return errors during source fetching, and streaming connections that drop before the full response is delivered.

Unlike content-level errors that occur because of what you asked, this error occurs because of infrastructure issues that are largely outside your control. The most common triggering scenarios are: a model API call times out because the inference cluster is under high load, a web source Perplexity tried to retrieve returned an error that cascaded into the query pipeline, or a network disruption between your browser and Perplexity's servers interrupted the streaming response.

Retrying after a short wait resolves the majority of these errors because the infrastructure redistributes the request to a healthy instance on the next attempt.

Common Mistakes to Avoid

• Retrying immediately and repeatedly. The 'Something Went Wrong' error is usually infrastructure-related. Waiting 30 to 60 seconds before retrying is more effective than rapid successive attempts, which may extend or worsen a transient server-side problem.
• Assuming the query content caused the error. This error is a technical failure, not a content moderation or input validation issue. Rewriting your query is unlikely to help unless the original query was unusually long or complex.
• Not testing on a different network. A dropped streaming connection due to network instability is a frequent cause of this error and is easily diagnosed by switching networks.
• Ignoring browser extensions. Extensions that intercept or modify HTTP requests can break Perplexity's streaming connection silently. Always test in incognito mode to rule this out quickly.
• Not checking the status page before extensive troubleshooting. If there is an active incident, no amount of local troubleshooting will fix the problem. Check perplexity.ai/status first to rule out a platform-wide issue before spending time diagnosing your own setup.
• Giving up and switching tools when a short wait would resolve it. Most transient backend errors clear within 2 to 5 minutes. A brief wait is usually all that is needed.

Understanding Perplexity's Error Types at a Glance

Knowing which error message maps to which cause speeds up troubleshooting significantly.

| Error message | Likely cause | First action | |---|---|---| | "Something Went Wrong" | Backend/API technical failure | Wait 60 seconds, retry | | "Error in Processing Query" | Query too complex or content filter | Simplify and rephrase query | | "Too Many Requests" / 429 | Rate throttling (too fast) | Wait 90 seconds, slow down | | "Weekly limit reached" | Pro quota exhausted | Switch to Standard mode | | "Session Expired" | Auth token timed out | Log back in | | "Access Denied" | IP block or subscription lapse | Check VPN, check subscription |

"Something Went Wrong" sits squarely in the technical failure category — the fix is always some variation of wait, refresh, switch environment, and retry. It is never caused by what you searched for, so do not waste time rewording the query.

Tracking Perplexity's Reliability History

If you are a frequent Perplexity user who needs to plan work around its reliability patterns:

• perplexity.ai/status maintains a history of past incidents with resolution times. Reviewing this history shows how frequently outages occur and how long they typically last.
• Most Perplexity incidents resolve within 30 minutes to 2 hours based on historical patterns.
• Major incidents affecting the core search service are relatively infrequent — several per quarter. Minor, short-duration errors affecting a subset of users occur more regularly but typically resolve within minutes.
• For mission-critical research workflows, always have a backup tool available: Bing Copilot, Google AI Overviews, or a standalone LLM like Claude or ChatGPT can cover most research needs during Perplexity downtime.

Preventing Future Occurrences of "Something Went Wrong"

While this error is largely caused by infrastructure factors outside your control, a few habits reduce how often you encounter it.

Maintain a stable browser environment:

• Keep your browser updated to the latest version — outdated browsers can have WebSocket compatibility issues that break streaming connections.
• Avoid running Perplexity in extremely resource-constrained environments (a browser with 50+ tabs open, very low RAM, or on a throttled corporate network). Resource pressure on the client side can cause connection drops that trigger this error.

Use a consistent, reliable network:

• Avoid running intensive Perplexity research sessions on mobile data in areas with weak coverage. Streaming response delivery is sensitive to intermittent network drops.
• If you use a VPN, choose a server that is geographically close to minimize added latency in the connection chain.

Set up status monitoring:

• Subscribe to email notifications at perplexity.ai/status so you are automatically informed when incidents begin and end.
• This prevents the frustrating experience of troubleshooting a problem that is actually a platform incident — you will know immediately rather than spending 20 minutes diagnosing your own setup.

View all Perplexity guides