# Deepseek Unavailable! No Response from Customer Support!

**URL:** <https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044>\
**Category:** Help\
**Created:** [December 12, 2025, 7:59am UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044 "2025-12-12T07:59:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![user1450](https://avatars.discourse-cdn.com/v4/letter/u/ce7236/32.png) [@user1450](https://forum.cursor.com/u/user1450)\
**Post date:** [December 12, 2025, 7:59am UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/1 "2025-12-12T07:59:53Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Yesterday early morning, I was still using the Deepseek model in Cursor for work. When I got back to continue working in the afternoon, I couldn’t find the Deepseek model option anymore. I also searched for it in Models but it didn’t exist at all. What exactly is the reason? I contacted customer support, but there’s still no reply after nearly 24 hours. It’s not a regional issue…

### Steps to Reproduce

I didn’t even close the Cursor client at all in the meantime — the Deepseek model was gone as soon as I got back to work, and I’m unable to reproduce the issue.

### Expected Behavior

I hope it can be fixed as soon as possible — I need it for my work.

### Screenshots / Screen Recordings

 ![微信图片_2025-12-12_155859_206.png](https://us1.discourse-cdn.com/cursor1/original/3X/9/4/944d734dbcb52a03f901ac9518c3f79b4748a8cb.png)

### Operating System

Windows 10/11

### Current Cursor Version (Menu → About Cursor → Copy)

Cursor  
Version:2.2.14 (user setup)VSCode Version: 1.105.1Commit: 1685afce45886aa5579025ac7e077fc3d4369c50Date:2025-12-11T01:12:35.790Z(1天前)Electron: 37.7.0  
Chromium: 138.0.7204.251Node.js:22.20.0V8:13.8.258.32-electron.0OS: Windows NTx64 10.0.26100  
Copy  
OK

### For AI issues: which model did you use?

deepseekR1

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![tonymarston](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@tonymarston](https://forum.cursor.com/u/tonymarston)\
**Post date:** [December 11, 2025, 4:57pm UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/2 "2025-12-11T16:57:52Z")

</div>

I can’t select any Deepseek model with the latest Cursor update, what’s going on? If I install an older version, they don’t appear either.

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/f/1/f1b41e729862872e77cb939d46b0f65f0b4ea817.png)

---

<div class="post-metadata">

**Author:** ![sanjeed5](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sanjeed5/32/9610_2.png) [@sanjeed5](https://forum.cursor.com/u/sanjeed5)\
**Post date:** [December 12, 2025, 2:50pm UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/3 "2025-12-12T14:50:53Z")

</div>

Thanks for the report and sorry for the confusion. DeepSeek models were removed due to low usage, but we understand this is disruptive.

**Workaround:** You can add them back now using custom model identifiers in Cursor Settings → Models → Add Model with these keys:

- `deepseek-r1-0528`
- `deepseek-v3.1`

The team is working on making this easier - we’ll update here when that’s ready.

---

<div class="post-metadata">

**Author:** ![user1450](https://avatars.discourse-cdn.com/v4/letter/u/ce7236/32.png) [@user1450](https://forum.cursor.com/u/user1450)\
**Post date:** [December 12, 2025, 3:12pm UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/4 "2025-12-12T15:12:49Z")

</div>

![image](https://us1.discourse-cdn.com/cursor1/original/3X/8/f/8f0c23e0040e0f2eac0b1d625e5bdb7816195ec0.png)Is it like this? Don’t we need to fill in the KEY and URL?

---

<div class="post-metadata">

**Author:** ![user1450](https://avatars.discourse-cdn.com/v4/letter/u/ce7236/32.png) [@user1450](https://forum.cursor.com/u/user1450)\
**Post date:** [December 12, 2025, 3:17pm UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/5 "2025-12-12T15:17:03Z")

</div>

Is it no longer possible to utilize the DeepSeek model?

---

<div class="post-metadata">

**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\
**Post date:** [December 15, 2025, 10:03am UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/6 "2025-12-15T10:03:13Z")

</div>

Please go to Settings \> Models \> Add model and add the models Sanjeed listed there.

---

<div class="post-metadata">

**Author:** ![zljh](https://avatars.discourse-cdn.com/v4/letter/z/958977/32.png) [@zljh](https://forum.cursor.com/u/zljh)\
**Post date:** [December 15, 2025, 11:54am UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/7 "2025-12-15T11:54:33Z")

</div>

> [@sanjeed5](#):
>
> deepseek-v3.1

Just a follow up question, are we bringing the lastest V3.2 or coder V2 to Cursor Platform?

---

<div class="post-metadata">

**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\
**Post date:** [December 15, 2025, 12:18pm UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/8 "2025-12-15T12:18:41Z")

</div>

I am not aware of those models being in the pipeline at the moment.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [January 6, 2026, 12:18pm UTC](https://forum.cursor.com/t/deepseek-unavailable-no-response-from-customer-support/146044/9 "2026-01-06T12:18:52Z")

</div>

Closed on January 6, 2026, 12:18pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
