How to avoid Perplexity temporary restrictions and suspicious activity flags

Step-by-Step Guide to Avoiding and Recovering from Perplexity Restrictions

Perplexity's abuse detection system is designed to distinguish heavy legitimate use from automated or abusive traffic. Most restrictions are avoidable if you understand what triggers them and which behaviors to avoid.

Step 1: Recognize the Warning Signs Before a Full Restriction

Perplexity sometimes applies soft throttling before a full restriction. Learn to recognize these early warning signs:

1. Queries take noticeably longer to return results than usual (more than 10 seconds for a standard search)
2. A CAPTCHA appears before you can submit a search
3. "Too many requests" error appears but clears after a 5-minute wait
4. The Pro Search toggle stops working even though your Pro subscription is active

If you see any of these, stop submitting queries immediately and take a break of at least 15 to 30 minutes. This usually prevents the soft throttling from escalating into a full account restriction.

Step 2: Identify Whether Your Behavior Triggered the Flag

Review your recent activity honestly before contacting support. Restrictions almost always have a cause:

High-risk behaviors that trigger flags:

• Submitting 20 or more queries within a 5-minute window
• Repeatedly running the same or nearly identical queries (common when testing prompts)
• Switching VPN server locations multiple times during a session
• Using browser automation (Selenium, Playwright, Puppeteer) to interact with Perplexity's web interface
• Logging in from multiple geographic locations within a short period
• Sharing account credentials with other people using the same login simultaneously

Normal behaviors that do not trigger flags:

• Conducting many searches throughout the day with natural pauses between them
• Using a single VPN server location consistently
• Switching between devices using the same account (as long as sessions are not simultaneous)
• Running 5 to 10 queries in a row when researching a topic

Step 3: If Flagged — Stop and Wait

If you see a "Too many requests" message, a restriction notice, or queries failing consistently:

1. Stop all queries immediately — continuing to submit queries when flagged will extend the restriction period
2. Do not open new browser tabs with Perplexity and try there — this does not help and may worsen the flag
3. Do not log out and log in with a different account to bypass the restriction — using multiple accounts to evade restrictions can result in a permanent ban on all linked accounts
4. Wait 1 to 4 hours before trying Perplexity again
5. When you return, start with a single query and wait for the full response before submitting another

Step 4: Reduce Query Rate for High-Volume Research

If you regularly conduct intensive research sessions that might trigger rate limits, adjust your workflow:

1. Spread queries across a longer time window — aim for no more than 15 queries per 10 minutes
2. Add deliberate pauses between queries when researching a topic with many sub-questions
3. Use Perplexity's "Focus" feature to make each query more targeted, reducing the number of follow-up queries needed
4. For large research tasks, consider breaking them into sessions across different hours rather than running them all at once
5. Use the Deep Research feature for complex multi-step questions — one Deep Research task covers what would otherwise require 5 to 10 individual Pro Search queries

Step 5: Fix VPN-Related Flags

If your restriction appears to be caused by VPN usage:

1. Disconnect from your VPN entirely and connect via your regular ISP connection
2. Wait 30 minutes after disconnecting before using Perplexity again
3. If you must use a VPN for privacy reasons, choose one server location and do not change it during your Perplexity session
4. Avoid VPN providers that use datacenter IP ranges (many budget VPNs do this) — residential IP-based VPNs like Mullvad or ProtonVPN are less likely to trigger flags
5. If your VPN has a "split tunneling" feature, configure Perplexity traffic to bypass the VPN — this routes your Perplexity traffic through your regular IP while protecting other traffic

Step 6: Fix API-Related Rate Limit Issues

If you are using the Perplexity API and hitting restrictions:

1. Add exponential backoff to your API client: when you receive a 429 (Too Many Requests) response, wait progressively longer before retrying — start with 1 second, then 2, then 4, then 8
2. Check your tier's rate limit in the Perplexity API documentation and ensure your request rate stays below it
3. Cache API responses locally for identical or near-identical queries rather than making repeat API calls
4. If your use case requires high-volume API access, contact support@perplexity.ai to discuss enterprise API access options with higher limits
5. Never use the web application interface via automation scripts — use the official API for programmatic access

Step 7: Contact Support for Persistent Restrictions

If your account is still restricted after 24 hours and your usage was legitimate:

1. Email support@perplexity.ai with the subject line: Account restriction — false positive request
2. Include: your account email, the date and time you first noticed the restriction, a description of your normal usage pattern, and whether you use a VPN or API access
3. Ask the support team to review your account's activity log and confirm whether the flag was accurate
4. Response time is typically 24 to 48 hours on business days
5. Do not send multiple emails about the same issue — reply to the original thread if you need to add information

Why This Happens

Perplexity's abuse detection system monitors account behavior to protect the service from bots, scrapers, and users attempting to exceed their quota limits. The system looks for behavioral patterns rather than absolute query counts — 50 queries spread evenly over a day are treated differently from 50 queries submitted in 5 minutes. VPN location-switching is a particularly strong signal because it is a common technique used by automated systems testing different IP addresses to evade geographic restrictions. The system cannot distinguish between a legitimate user switching VPN servers and a bot rotating proxies, so it applies the same restriction to both. Because the detection is automated, legitimate heavy users occasionally get caught in false positives — these are resolved through the support email channel after manual review.

Understanding Perplexity's Usage Limits

Knowing the actual limits helps you stay within them:

• Pro Search: Perplexity Pro allows up to 300 Pro searches per day; the daily limit resets at midnight UTC
• Deep Research: Pro users receive 5 Deep Research reports per day; each Deep Research task replaces what would otherwise be 5 to 10 individual Pro Search queries
• Standard Search: No documented daily cap for Standard Search on either free or Pro plans under normal use
• API rate limits: The free API tier allows 5 requests per minute and 20 requests per hour; paid API tiers have higher limits documented in the Perplexity API documentation
• File uploads: No documented per-day file upload cap, but very high-volume uploads may trigger the same abuse detection as excessive search queries

Staying clearly within these limits during any single session is the most reliable way to avoid triggering suspicious activity flags.

Common Mistakes to Avoid

• Creating a new account to bypass a restriction. Perplexity can link accounts by IP address, browser fingerprint, and payment method. Creating a new account while restricted can result in all linked accounts being banned permanently.
• Ignoring the early warning signs. A single CAPTCHA or a brief "too many requests" message is a soft warning. Stopping immediately at this point usually prevents escalation to a full restriction.
• Switching VPN servers to fix a VPN-related flag. If your VPN's location caused the flag, switching to another location makes it worse, not better. Disconnect the VPN entirely and wait before trying again.
• Using browser automation on Perplexity's web interface. Browser automation creates traffic patterns that are easily detected as non-human. Use the official Perplexity API for any programmatic access.
• Waiting less than an hour before testing again. Restriction periods do not reset instantly. Testing after 10 minutes when a 1-hour restriction is active will show the same error and may extend the restriction.
• Not implementing rate limit handling in API code. An API client without proper 429 handling will hammer Perplexity's servers with retries, escalating what would have been a brief throttle into a longer restriction.

View all Perplexity guides