Extenstions marketplace don't working

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Error while fetching extenstions. Failed to fetch

Steps to Reproduce

Trying to load extensions

Screenshots / Screen Recordings

Снимок экрана 2026-02-08 в 15.34.31.png
Снимок экрана 2026-02-08 в 15.34.31.png3386×2030 1.5 MB

Operating System

MacOS

Version Information

Version: 2.4.31
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z (4 hrs ago)
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Cursor Extension Marketplace Does not render extension
3

In additional, i have troubles with cursor tab in http 2 (chat is working)
but when i switch to http 1.1 - tab is working, but agent chat is now working (very sloooow)
Its unusable

Help me

HTTP 1.1 :

98.87.104.180 in 0ms
[2026-02-08T12:36:47.656Z] Resolved to 18.210.128.176, 52.6.14.166, 100.25.234.57, 54.156.205.110, 34.235.69.84, 98.86.34.178, 44.207.199.1, 98.87.104.180 in 0ms
[2026-02-08T12:36:47.656Z] Resolved to 18.210.128.176, 52.6.14.166, 100.25.234.57, 54.156.205.110, 34.235.69.84, 98.86.34.178, 44.207.199.1, 98.87.104.180 in 0ms
[2026-02-08T12:36:47.656Z] Resolved to 18.210.128.176, 52.6.14.166, 100.25.234.57, 54.156.205.110, 34.235.69.84, 98.86.34.178, 44.207.199.1, 98.87.104.180 in 0ms
[2026-02-08T12:36:47.656Z] Result: true

[2026-02-08T12:36:47.619Z] Start
[2026-02-08T12:36:48.019Z] URL: api cursor
[2026-02-08T12:36:48.019Z] Status: 200
[2026-02-08T12:36:48.019Z] IP: 18.210.128.176
[2026-02-08T12:36:48.019Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-02-08T12:36:48.019Z] Name: api2.cursor.sh
[2026-02-08T12:36:48.019Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-02-08T12:36:48.019Z] DNS Time: 8ms
[2026-02-08T12:36:48.019Z] Connect Time: 130ms
[2026-02-08T12:36:48.019Z] TLS Time: 132ms
[2026-02-08T12:36:48.020Z] Result: true in 401ms

[2026-02-08T12:36:47.619Z] Start
[2026-02-08T12:36:48.047Z] Result: true

[2026-02-08T12:36:47.620Z] Sending ping 1
[2026-02-08T12:36:48.288Z] Response: ‘ping’ in 668ms
[2026-02-08T12:36:48.288Z] Sending ping 2
[2026-02-08T12:36:48.693Z] Response: ‘ping’ in 405ms
[2026-02-08T12:36:48.693Z] Sending ping 3
[2026-02-08T12:36:49.108Z] Response: ‘ping’ in 415ms
[2026-02-08T12:36:49.108Z] Sending ping 4
[2026-02-08T12:36:49.504Z] Response: ‘ping’ in 396ms
[2026-02-08T12:36:49.504Z] Sending ping 5
[2026-02-08T12:36:49.908Z] Response: ‘ping’ in 404ms
[2026-02-08T12:36:49.909Z] Result: true

[2026-02-08T12:36:47.621Z] Starting streamSSE
[2026-02-08T12:36:48.038Z] Response: ‘foo’ in 416ms
[2026-02-08T12:36:49.037Z] Response: ‘foo’ in 999ms
[2026-02-08T12:36:50.037Z] Response: ‘foo’ in 1000ms
[2026-02-08T12:36:51.038Z] Response: ‘foo’ in 1001ms
[2026-02-08T12:36:52.037Z] Response: ‘foo’ in 999ms
[2026-02-08T12:36:53.041Z] Result: true

[2026-02-08T12:36:47.621Z] Starting stream
[2026-02-08T12:36:47.622Z] Pushing first message
[2026-02-08T12:36:48.467Z] Response: ‘foo’ in 845ms
[2026-02-08T12:36:48.968Z] Pushing next message
[2026-02-08T12:36:49.474Z] Response: ‘foo’ in 1007ms
[2026-02-08T12:36:49.975Z] Pushing next message
[2026-02-08T12:36:50.481Z] Response: ‘foo’ in 1007ms
[2026-02-08T12:36:50.982Z] Pushing next message
[2026-02-08T12:36:51.495Z] Response: ‘foo’ in 1014ms
[2026-02-08T12:36:51.995Z] Pushing next message
[2026-02-08T12:36:52.494Z] Response: ‘foo’ in 999ms
[2026-02-08T12:36:52.494Z] Result: true

[2026-02-08T12:36:47.618Z] Host: market place cursor
[2026-02-08T12:36:47.769Z] Response in 151ms
[2026-02-08T12:36:47.769Z] Response: 200
[2026-02-08T12:36:47.769Z] Response Type: cors
[2026-02-08T12:36:47.769Z] Server: null
[2026-02-08T12:36:47.769Z] Result: OK in 151ms

HTTP 2:
[2026-02-08T12:37:20.884Z] Host: api2.cursor.sh
[2026-02-08T12:37:20.884Z] Servers: 8.8.8.8,1.1.1.1
[2026-02-08T12:37:20.884Z] Resolved to 52.1.13.102 in 28ms
[2026-02-08T12:37:20.887Z] Resolved to 52.1.13.102 in 3ms
[2026-02-08T12:37:20.890Z] Resolved to 52.1.13.102 in 2ms
[2026-02-08T12:37:20.892Z] Resolved to 52.1.13.102 in 2ms
[2026-02-08T12:37:20.892Z] Host: api2.cursor.sh
[2026-02-08T12:37:20.892Z] Servers: system
[2026-02-08T12:37:20.892Z] Resolved to 18.210.128.176, 52.6.14.166, 100.25.234.57, 54.156.205.110, 34.235.69.84, 98.86.34.178, 44.207.199.1, 98.87.104.180 in 0ms
[2026-02-08T12:37:20.892Z] Resolved to 18.210.128.176, 52.6.14.166, 100.25.234.57, 54.156.205.110, 34.235.69.84, 98.86.34.178, 44.207.199.1, 98.87.104.180 in 0ms
[2026-02-08T12:37:20.892Z] Resolved to 18.210.128.176, 52.6.14.166, 100.25.234.57, 54.156.205.110, 34.235.69.84, 98.86.34.178, 44.207.199.1, 98.87.104.180 in 0ms
[2026-02-08T12:37:20.893Z] Resolved to 18.210.128.176, 52.6.14.166, 100.25.234.57, 54.156.205.110, 34.235.69.84, 98.86.34.178, 44.207.199.1, 98.87.104.180 in 0ms
[2026-02-08T12:37:20.893Z] Result: true

[2026-02-08T12:37:20.853Z] Start
[2026-02-08T12:37:21.136Z] Host: api2.cursor.sh
[2026-02-08T12:37:21.136Z] Protocol: h2
[2026-02-08T12:37:21.136Z] Result: true in 283ms

[2026-02-08T12:37:20.854Z] Start
[2026-02-08T12:37:21.279Z] URL: – api cursor –
[2026-02-08T12:37:21.279Z] Status: 200
[2026-02-08T12:37:21.280Z] IP: 52.1.13.102
[2026-02-08T12:37:21.280Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-02-08T12:37:21.280Z] Name: api2.cursor.sh
[2026-02-08T12:37:21.280Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-02-08T12:37:21.280Z] DNS Time: 3ms
[2026-02-08T12:37:21.280Z] Connect Time: 155ms
[2026-02-08T12:37:21.280Z] TLS Time: 134ms
[2026-02-08T12:37:21.280Z] Result: true in 426ms

[2026-02-08T12:37:20.858Z] Start
[2026-02-08T12:37:21.367Z] Result: true

[2026-02-08T12:37:20.862Z] Sending ping 1
[2026-02-08T12:37:21.375Z] Response: ‘ping’ in 513ms
[2026-02-08T12:37:21.375Z] Sending ping 2
[2026-02-08T12:37:21.537Z] Response: ‘ping’ in 162ms
[2026-02-08T12:37:21.537Z] Sending ping 3
[2026-02-08T12:37:21.667Z] Response: ‘ping’ in 130ms
[2026-02-08T12:37:21.667Z] Sending ping 4
[2026-02-08T12:37:21.799Z] Response: ‘ping’ in 132ms
[2026-02-08T12:37:21.799Z] Sending ping 5
[2026-02-08T12:37:21.931Z] Response: ‘ping’ in 132ms
[2026-02-08T12:37:21.931Z] Result: true

[2026-02-08T12:37:20.866Z] Starting stream
[2026-02-08T12:37:21.367Z] Response: ‘foo’ in 496ms
[2026-02-08T12:37:22.368Z] Response: ‘foo’ in 1001ms
[2026-02-08T12:37:23.367Z] Response: ‘foo’ in 999ms
[2026-02-08T12:37:24.375Z] Response: ‘foo’ in 1008ms
[2026-02-08T12:37:25.374Z] Response: ‘foo’ in 999ms
[2026-02-08T12:37:26.381Z] Result: true

[2026-02-08T12:37:20.871Z] Starting stream
[2026-02-08T12:37:20.871Z] Pushing first message
[2026-02-08T12:37:21.367Z] Response: ‘foo’ in 496ms
[2026-02-08T12:37:21.868Z] Pushing next message
[2026-02-08T12:37:21.994Z] Response: ‘foo’ in 627ms
[2026-02-08T12:37:22.498Z] Pushing next message
[2026-02-08T12:37:22.624Z] Response: ‘foo’ in 630ms
[2026-02-08T12:37:23.124Z] Pushing next message
[2026-02-08T12:37:23.252Z] Response: ‘foo’ in 628ms
[2026-02-08T12:37:23.755Z] Pushing next message
[2026-02-08T12:37:23.882Z] Response: ‘foo’ in 630ms
[2026-02-08T12:37:23.882Z] Result: true

[2026-02-08T12:37:20.850Z] Host: marketplace.cursorapi.com
[2026-02-08T12:37:20.995Z] Response in 145ms
[2026-02-08T12:37:20.995Z] Response: 200
[2026-02-08T12:37:20.995Z] Response Type: cors
[2026-02-08T12:37:20.995Z] Server: null
[2026-02-08T12:37:20.995Z] Result: OK in 145ms

4

Hey, thanks for the report. I’m seeing two separate issues here:

  1. Extension marketplace: “Failed to fetch”

The console logs show requests to marketplace.cursorapi.com are timing out with net::ERR_TIMED_OUT. This is a known issue that can be network-related. Can you try:

  • Are you using a VPN, proxy, or firewall? If yes, please temporarily disable it and check if the marketplace loads.
  1. HTTP/2 issue (Tab and Chat can’t work at the same time)

This is a known network issue. The fact that Tab breaks on HTTP/2 while Chat works on HTTP/1.1 suggests your network is interfering with one of the protocols. Quick question: are you on a corporate network or using any proxy (like Zscaler)?

Also, based on your diagnostics, on HTTP/2 DNS resolves to a single IP (52.1.13.102), while on HTTP/1.1 it resolves to a whole pool. That’s unusual and points to network-level interference.

Can you try:

  1. Run Cursor Settings > Network > Run Diagnostics with VPN/proxy enabled and disabled (if applicable) and share the full output
  2. Share your network setup: corporate or home network, whether you use a proxy, and which country you’re connecting from

This will help us figure out if it’s a geo/network issue or something on our side.

5

Used from Russia, Moscow

WITHOUT VPN, PROXY
HTTP2:

[2026-02-08T14:58:48.377Z] Host: api2.cursor.sh
[2026-02-08T14:58:48.377Z] Servers: 8.8.8.8,1.1.1.1
[2026-02-08T14:58:48.377Z] Resolved to 18.214.49.190 in 5ms
[2026-02-08T14:58:48.384Z] Resolved to 18.214.49.190 in 4ms
[2026-02-08T14:58:48.386Z] Resolved to 18.214.49.190 in 2ms
[2026-02-08T14:58:48.387Z] Resolved to 18.214.49.190 in 1ms
[2026-02-08T14:58:48.389Z] Host: api2.cursor.sh
[2026-02-08T14:58:48.389Z] Servers: system
[2026-02-08T14:58:48.389Z] Resolved to 18.214.49.190, 52.2.228.229, 98.85.136.24, 23.23.31.41, 174.129.226.31, 34.199.54.231, 34.199.65.28, 18.210.36.112 in 2ms
[2026-02-08T14:58:48.389Z] Resolved to 18.214.49.190, 52.2.228.229, 98.85.136.24, 23.23.31.41, 174.129.226.31, 34.199.54.231, 34.199.65.28, 18.210.36.112 in 0ms
[2026-02-08T14:58:48.389Z] Resolved to 18.214.49.190, 52.2.228.229, 98.85.136.24, 23.23.31.41, 174.129.226.31, 34.199.54.231, 34.199.65.28, 18.210.36.112 in 0ms
[2026-02-08T14:58:48.389Z] Resolved to 18.214.49.190, 52.2.228.229, 98.85.136.24, 23.23.31.41, 174.129.226.31, 34.199.54.231, 34.199.65.28, 18.210.36.112 in 0ms
[2026-02-08T14:58:48.389Z] Result: true

[2026-02-08T14:58:48.344Z] Start
[2026-02-08T14:58:48.624Z] Host: api2.cursor.sh
[2026-02-08T14:58:48.624Z] Protocol: h2
[2026-02-08T14:58:48.624Z] Result: true in 280ms

[2026-02-08T14:58:48.345Z] Start
[2026-02-08T14:58:48.744Z] URL: https://api2.cursor.sh/
[2026-02-08T14:58:48.744Z] Status: 200
[2026-02-08T14:58:48.744Z] IP: 18.214.49.190
[2026-02-08T14:58:48.744Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-02-08T14:58:48.744Z] Name: api2.cursor.sh
[2026-02-08T14:58:48.744Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-02-08T14:58:48.744Z] DNS Time: 4ms
[2026-02-08T14:58:48.744Z] Connect Time: 128ms
[2026-02-08T14:58:48.744Z] TLS Time: 136ms
[2026-02-08T14:58:48.744Z] Result: true in 399ms

[2026-02-08T14:58:48.350Z] Start
[2026-02-08T14:58:48.837Z] Result: true

[2026-02-08T14:58:48.354Z] Sending ping 1
[2026-02-08T14:58:48.847Z] Response: ‘ping’ in 493ms
[2026-02-08T14:58:48.847Z] Sending ping 2
[2026-02-08T14:58:48.985Z] Response: ‘ping’ in 138ms
[2026-02-08T14:58:48.986Z] Sending ping 3
[2026-02-08T14:58:49.121Z] Response: ‘ping’ in 135ms
[2026-02-08T14:58:49.121Z] Sending ping 4
[2026-02-08T14:58:49.337Z] Response: ‘ping’ in 216ms
[2026-02-08T14:58:49.337Z] Sending ping 5
[2026-02-08T14:58:49.530Z] Response: ‘ping’ in 193ms
[2026-02-08T14:58:49.530Z] Result: true

[2026-02-08T14:58:48.360Z] Starting stream
[2026-02-08T14:58:48.837Z] Response: ‘foo’ in 469ms
[2026-02-08T14:58:49.855Z] Response: ‘foo’ in 1018ms
[2026-02-08T14:58:50.852Z] Response: ‘foo’ in 997ms
[2026-02-08T14:58:51.853Z] Response: ‘foo’ in 1001ms
[2026-02-08T14:58:52.850Z] Response: ‘foo’ in 997ms
[2026-02-08T14:58:53.854Z] Result: true

[2026-02-08T14:58:48.367Z] Starting stream
[2026-02-08T14:58:48.368Z] Pushing first message
[2026-02-08T14:58:48.837Z] Response: ‘foo’ in 469ms
[2026-02-08T14:58:49.338Z] Pushing next message
[2026-02-08T14:58:49.502Z] Response: ‘foo’ in 665ms
[2026-02-08T14:58:50.003Z] Pushing next message
[2026-02-08T14:58:50.132Z] Response: ‘foo’ in 630ms
[2026-02-08T14:58:50.636Z] Pushing next message
[2026-02-08T14:58:50.768Z] Response: ‘foo’ in 636ms
[2026-02-08T14:58:51.268Z] Pushing next message
[2026-02-08T14:58:51.399Z] Response: ‘foo’ in 631ms
[2026-02-08T14:58:51.399Z] Result: true

[2026-02-08T14:58:48.339Z] Host: marketplace.cursorapi.com
[2026-02-08T14:58:48.610Z] Response in 271ms
[2026-02-08T14:58:48.610Z] Response: 200
[2026-02-08T14:58:48.610Z] Response Type: cors
[2026-02-08T14:58:48.610Z] Server: null
[2026-02-08T14:58:48.610Z] Result: OK in 271ms

HTTP 1.1:

[2026-02-08T15:00:11.259Z] Host: api2.cursor.sh
[2026-02-08T15:00:11.260Z] Servers: 8.8.8.8,1.1.1.1
[2026-02-08T15:00:11.260Z] Resolved to 54.227.121.228 in 36ms
[2026-02-08T15:00:11.273Z] Resolved to 54.227.121.228 in 3ms
[2026-02-08T15:00:11.275Z] Resolved to 54.227.121.228 in 2ms
[2026-02-08T15:00:11.277Z] Resolved to 54.227.121.228 in 2ms
[2026-02-08T15:00:11.280Z] Host: api2.cursor.sh
[2026-02-08T15:00:11.280Z] Servers: system
[2026-02-08T15:00:11.280Z] Resolved to 54.227.121.228, 54.234.15.20, 44.208.212.248, 44.214.210.84, 44.195.5.51, 44.195.214.102, 100.51.26.205, 174.129.226.31 in 1ms
[2026-02-08T15:00:11.280Z] Resolved to 54.227.121.228, 54.234.15.20, 44.208.212.248, 44.214.210.84, 44.195.5.51, 44.195.214.102, 100.51.26.205, 174.129.226.31 in 0ms
[2026-02-08T15:00:11.280Z] Resolved to 54.227.121.228, 54.234.15.20, 44.208.212.248, 44.214.210.84, 44.195.5.51, 44.195.214.102, 100.51.26.205, 174.129.226.31 in 0ms
[2026-02-08T15:00:11.280Z] Resolved to 54.227.121.228, 54.234.15.20, 44.208.212.248, 44.214.210.84, 44.195.5.51, 44.195.214.102, 100.51.26.205, 174.129.226.31 in 0ms
[2026-02-08T15:00:11.280Z] Result: true

[2026-02-08T15:00:11.222Z] Start
[2026-02-08T15:00:11.656Z] URL: https://api2.cursor.sh/
[2026-02-08T15:00:11.657Z] Status: 200
[2026-02-08T15:00:11.657Z] IP: 54.227.121.228
[2026-02-08T15:00:11.657Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-02-08T15:00:11.657Z] Name: api2.cursor.sh
[2026-02-08T15:00:11.657Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-02-08T15:00:11.657Z] DNS Time: 6ms
[2026-02-08T15:00:11.657Z] Connect Time: 158ms
[2026-02-08T15:00:11.657Z] TLS Time: 136ms
[2026-02-08T15:00:11.657Z] Result: true in 435ms

[2026-02-08T15:00:11.228Z] Start
[2026-02-08T15:00:11.677Z] Result: true

[2026-02-08T15:00:11.234Z] Sending ping 1
[2026-02-08T15:00:11.676Z] Response: ‘ping’ in 442ms
[2026-02-08T15:00:11.676Z] Sending ping 2
[2026-02-08T15:00:12.080Z] Response: ‘ping’ in 404ms
[2026-02-08T15:00:12.080Z] Sending ping 3
[2026-02-08T15:00:12.492Z] Response: ‘ping’ in 412ms
[2026-02-08T15:00:12.493Z] Sending ping 4
[2026-02-08T15:00:12.901Z] Response: ‘ping’ in 408ms
[2026-02-08T15:00:12.901Z] Sending ping 5
[2026-02-08T15:00:13.296Z] Response: ‘ping’ in 395ms
[2026-02-08T15:00:13.296Z] Result: true

[2026-02-08T15:00:11.240Z] Starting streamSSE
[2026-02-08T15:00:11.676Z] Response: ‘foo’ in 429ms
[2026-02-08T15:00:12.674Z] Response: ‘foo’ in 998ms
[2026-02-08T15:00:13.676Z] Response: ‘foo’ in 1002ms
[2026-02-08T15:00:14.678Z] Response: ‘foo’ in 1002ms
[2026-02-08T15:00:15.675Z] Response: ‘foo’ in 997ms
[2026-02-08T15:00:16.679Z] Result: true

[2026-02-08T15:00:11.247Z] Starting stream
[2026-02-08T15:00:11.247Z] Pushing first message
[2026-02-08T15:00:11.810Z] Response: ‘foo’ in 563ms
[2026-02-08T15:00:12.311Z] Pushing next message
[2026-02-08T15:00:12.805Z] Response: ‘foo’ in 995ms
[2026-02-08T15:00:13.308Z] Pushing next message
[2026-02-08T15:00:13.809Z] Response: ‘foo’ in 1004ms
[2026-02-08T15:00:14.310Z] Pushing next message
[2026-02-08T15:00:14.806Z] Response: ‘foo’ in 997ms
[2026-02-08T15:00:15.307Z] Pushing next message
[2026-02-08T15:00:15.806Z] Response: ‘foo’ in 1000ms
[2026-02-08T15:00:15.806Z] Result: true

[2026-02-08T15:00:11.218Z] Host: marketplace.cursorapi.com
[2026-02-08T15:00:21.443Z] Response in 10225ms
[2026-02-08T15:00:21.443Z] Response: 200
[2026-02-08T15:00:21.444Z] Response Type: cors
[2026-02-08T15:00:21.444Z] Server: null
[2026-02-08T15:00:21.444Z] Result: OK in 10226ms

6

Thanks for the diagnostics and the location info, that really helps.

There’s a pattern here that points to network-level interference by your ISP or Russian DPI. Specifically:

DNS issue: When using Google/Cloudflare DNS (8.8.8.8 / 1.1.1.1), the domain api2.cursor.sh resolves to a single IP instead of the usual pool of 8. That’s unusual and suggests DNS responses are being filtered or spoofed at the network level.

Marketplace: Over HTTP/1.1, marketplace.cursorapi.com took 10 seconds to respond, compared to ~150 ms on HTTP/2. That matches signs of connection throttling.

Here’s what I’d suggest trying:

  1. Use a VPN. Try connecting through a VPN and see if Marketplace and Tab/Chat start working correctly on the same protocol. That would confirm the issue is network filtering.

  2. Change your system DNS to something other than your ISP’s default DNS. Even if you set 8.8.8.8/1.1.1.1 inside Cursor’s internal DNS settings, your system DNS can still be affected. Try setting it at the OS level: System Settings > Network > DNS.

  3. For Marketplace specifically, try opening https://marketplace.cursorapi.com directly in your browser and tell me if the page loads.

The fact that Tab and Chat can’t work on the same HTTP version is a strong signal that something on the network path is handling these two protocols differently. A VPN should bypass that completely.

Let me know how it goes.

7

When I downloaded vless and connected to another country everything worked, both the marketplace and http2.
The question is, why doesn’t anyone from Russia work without a VPN?
I have these dns addresses at the OS level.

9

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