# \# Perplexity Sonar Deep Research Model Timeout Issue - Seeking Solution

**URL:** <https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094>\
**Category:** Bug Reports\
**Created:** [October 16, 2025, 9:47am UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094 "2025-10-16T09:47:20Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![yila](https://avatars.discourse-cdn.com/v4/letter/y/7feea3/32.png) [@yila](https://community.perplexity.ai/u/yila)\
**Post date:** [October 16, 2025, 9:47am UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094/1 "2025-10-16T09:47:20Z")

</div>

## 🐛 Describe the Bug

## Problem Summary

I’m experiencing consistent timeout issues with the `sonar-deep-research` model in my production application. The model works fine for simple requests but consistently times out after approximately 60 seconds for complex report generation tasks.

## ✅ Expected Behavior

work as before - output content

## ❌ Actual Behavior

credit deducted but timeout, so no output created

## 🔄 Steps to Reproduce

## 📌 API Request & Response (if applicable)

## 🌍 Environment

- ## Environment Details

## 📎 Logs or Screenshots (if applicable)

## Detailed Error Logs

### Error Pattern

```

SocketError: other side closed

- Code: UND\_ERR\_SOCKET

- Remote: 104.18.27.48:443

- Bytes Written: 8353 (request sent successfully)

- Bytes Read: 0 (no response received)

- Timeout: ~60 seconds consistently

```

### Test Results Comparison

| Test Type | Model | Status | Duration | Error |

|-----------|-------|--------|----------|-------|

| Simple Hello | sonar-deep-research | ✅ SUCCESS | 7s | None |

| Full Report | sonar-deep-research | ❌ FAILED | 60s | Socket closed |

| Same Report | sonar | ✅ SUCCESS | 21s | None |

### Complete Error Log

```json

{

“error”: “TypeError: fetch failed”,

“cause”: {

“type”: “SocketError”,

“message”: “other side closed”,

“code”: “UND\_ERR\_SOCKET”,

“socket”: {

“localAddress”: “26.26.26.1”,

“localPort”: 59321,

“remoteAddress”: “104.18.27.48”,

“remotePort”: 443,

“remoteFamily”: “IPv4”,

“timeout”: null,

“bytesWritten”: 8353,

“bytesRead”: 0

```
}

```

}

}

```

## Request Configuration

```json

{

“model”: “sonar-deep-research”,

“messages”: [

```
{

```

“role”: “system”,

“content”: “[COMPREHENSIVE\_SYSTEM\_PROMPT\_FOR\_INVESTMENT\_ANALYSIS]”

```
},

{

```

“role”: “user”,

“content”: “Analyze Apple Inc. (AAPL) with current price $150.00”

```
}

```

],

“max\_tokens”: 15000,

“temperature”: 0.0,

“search\_queries”: true,

“search\_recency\_filter”: “month”,

“return\_citations”: true,

“top\_p”: 0.1,

“presence\_penalty”: 0.0,

“frequency\_penalty”: 0.0

}

```

## What I’ve Tried

1. \*\*Reduced token limits\*\* (15000 → 12000 → 10000)

2. \*\*Shortened search recency\*\* (month → week)

3. \*\*Simplified prompts\*\* (still times out)

4. \*\*Connection optimization\*\* (keep-alive headers)

5. \*\*Retry mechanisms\*\* (3 attempts with delays)

6. \*\*Streaming approach\*\* (same timeout issue)

## Key Observations

- \*\*Model-specific issue\*\*: Only `sonar-deep-research` fails; `sonar` works perfectly

- \*\*Consistent pattern\*\*: Always fails after ~60 seconds regardless of request complexity

- \*\*Server-side closure\*\*: Server accepts request but closes connection during processing

- \*\*No response data\*\*: Bytes written but zero bytes read

## Business Impact

- \*\*High Priority\*\*: Blocking production report generation

- \*\*User Experience\*\*: Reports fail to generate consistently

- \*\*Cost\*\*: API credits consumed without successful completion

- \*\*Reliability\*\*: Service appears unreliable to users

## Questions for the Community

1. \*\*Is this a known issue\*\* with `sonar-deep-research` model?

2. \*\*Are there specific parameters\*\* that can prevent this timeout?

3. \*\*Is there a server-side timeout limit\*\* for this model that’s different from others?

4. \*\*What’s the recommended approach\*\* for handling long-running deep research tasks?

5. \*\*Are there any workarounds\*\* that have worked for others?

## Request for Help

I need to use `sonar-deep-research` specifically for its deep research capabilities, but the consistent 60-second timeout makes it unusable for production. Any insights, workarounds, or solutions would be greatly appreciated.

## Contact Information

- \*\*Application\*\*: TopAnalyst - Investment Analysis Platform

- \*\*Use Case\*\*: Generating comprehensive investment reports

- \*\*Priority\*\*: High (blocking production usage)

-–

\*\*Note\*\*: This issue is preventing the use of `sonar-deep-research` model in production applications. The regular `sonar` model works fine, suggesting the issue is specific to the deep research model’s implementation or server-side processing limits.

## 📝 Additional Context

Add any other context about the problem here.

---

<div class="post-metadata">

**Author:** ![mr\_robot](https://avatars.discourse-cdn.com/v4/letter/m/67e7ee/32.png) [@mr\_robot](https://community.perplexity.ai/u/mr_robot)\
**Post date:** [October 16, 2025, 1:17pm UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094/2 "2025-10-16T13:17:55Z")

</div>

I experience the same issue since today. Have been using deep-research model for some time now and never ran into timeouts. Credits are deducted too though….

---

<div class="post-metadata">

**Author:** ![gerry](https://avatars.discourse-cdn.com/v4/letter/g/c77e96/32.png) [@gerry](https://community.perplexity.ai/u/gerry)\
**Post date:** [October 16, 2025, 9:45pm UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094/3 "2025-10-16T21:45:46Z")

</div>

+1 I’m experiencing this issue as well

---

<div class="post-metadata">

**Author:** ![Ricco\_Friedrich](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/ricco_friedrich/32/1444_2.png) [@Ricco\_Friedrich](https://community.perplexity.ai/u/Ricco_Friedrich)\
**Post date:** [October 17, 2025, 7:52am UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094/4 "2025-10-17T07:52:24Z")

</div>

Likewise, its costing me millions of tokens and my application does not run due to constant time out issues. Has anyone found a solution?

---

<div class="post-metadata">

**Author:** ![yila](https://avatars.discourse-cdn.com/v4/letter/y/7feea3/32.png) [@yila](https://community.perplexity.ai/u/yila)\
**Post date:** [October 17, 2025, 8:55am UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094/5 "2025-10-17T08:55:49Z")

</div>

no I am still waiting for the team’s final response, said they are reviewing

---

<div class="post-metadata">

**Author:** ![Michal\_Kowalkowski](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/michal_kowalkowski/32/1506_2.png) [@Michal\_Kowalkowski](https://community.perplexity.ai/u/Michal_Kowalkowski)\
**Post date:** [October 21, 2025, 1:33pm UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094/6 "2025-10-21T13:33:35Z")

</div>

I have the same issue in production, it was around 14th Oct I started getting “Cannot connect to API: Headers Timeout Error” errors (only sonar-deep-research).

---

<div class="post-metadata">

**Author:** ![yila](https://avatars.discourse-cdn.com/v4/letter/y/7feea3/32.png) [@yila](https://community.perplexity.ai/u/yila)\
**Post date:** [October 25, 2025, 4:04am UTC](https://community.perplexity.ai/t/perplexity-sonar-deep-research-model-timeout-issue-seeking-solution/2094/7 "2025-10-25T04:04:49Z")

</div>

The team has made an update, now you could go and try should resolve some of your problems, I can generate contents now just need to check if the quality is the same as before