isitdownrightnow.app
  1. Home
  2. Services
  3. Cursor
Cursor cursor.sh

Is Cursor down right now? Live status and outage tracker

No, Cursor is up.

No widespread outage detected. 2 user reports in the last hour is within the normal range.

Cursor's own status page: status.cursor.com

Live Last spike Data refreshes every 5 minutes
Not working for you? Official status pageStatus page
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

4 reports in total, counted in 15-minute windows

In the last hour, 2 problem reports came in for Cursor, and at this time of day there are usually almost none. Over the last 24 hours there were 4 reports. Worldwide, most recent reports were about app (80%) and website (20%). The last spike in reports was 27 h ago and lasted 27 min. These are user reports from the US, where most people report Cursor problems.

Around the world right now: normal in 65 other countries. By country

In the past 24 hours, 4 user reports came in for Cursor. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day. The busiest 15-minute window had 1 report, about 24 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Reports, last hour
2
None the hour before
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
1
1 report, 24 h ago
Last 24 hours

Cursor outages and problems

In the past 24 hours, 4 user reports came in for Cursor. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 1 report, about 24 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Cursor stayed at their usual level the whole time.
Official status

What Cursor's status page says

Checking status.cursor.com…

This month

Cursor in November 2026

Problem reports in November
2
Outage spikes
0
Periods of elevated reports
0

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for Cursor worldwide.

  1. App80%
  2. Website20%

Share of 5 recent reports that said what was wrong, from every country listed below.

World map

Cursor reports around the world

In the last 24 hours, 56 problem reports about Cursor came in from 14 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 032
Canada Normal 05
France Normal 03
Japan Normal 03
Vietnam Normal 03
Peru Normal 02
Hong Kong Normal 01
India Normal 01
New Zealand Normal 01
The Philippines Normal 01
Saudi Arabia Normal 01
Austria Normal 01

Each country's status compares its reports with the usual level there. 54 more countries had 2 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Cursor problem spikes, last 30 days

Since 5 October, Cursor had 3 outage spikes and 1 period of elevated reports. The longest lasted 5 h 55 min, on 29 October.

  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: 1 report
  • Tue 6 Oct: 0 reports
  • Wed 7 Oct: 1 report
  • Thu 8 Oct: 1 report
  • Fri 9 Oct: 1 report
  • Sat 10 Oct: 0 reports
  • Sun 11 Oct: 0 reports
  • Mon 12 Oct: 0 reports
  • Tue 13 Oct: 5 reports
  • Wed 14 Oct: 0 reports
  • Thu 15 Oct: 1 report
  • Fri 16 Oct: 0 reports
  • Sat 17 Oct: 0 reports
  • Sun 18 Oct: 0 reports
  • Mon 19 Oct: 0 reports
  • Tue 20 Oct: 1 report
  • Wed 21 Oct: no data
  • Thu 22 Oct: 0 reports
  • Fri 23 Oct: 0 reports
  • Sat 24 Oct: 0 reports
  • Sun 25 Oct: 0 reports
  • Mon 26 Oct: 5 reports
  • Tue 27 Oct: 0 reports
  • Wed 28 Oct: 173 reports (outage spike that day)
  • Thu 29 Oct: 79 reports (outage spike that day)
  • Fri 30 Oct: 450 reports (elevated reports that day)
  • Sat 31 Oct: 30 reports (outage spike that day)
  • Sun 1 Nov: 2 reports
  • Outage
    Sat 31 Oct, 03:33–03:59
    Lasted 27 min
    16peak reports
  • Elevated reports
    Fri 30 Oct, 06:26–06:43
    Lasted 16 min
    10peak reports
  • Outage
    Thu 29 Oct, 23:48–05:43
    Lasted 5 h 55 min
    33peak reports
  • Outage
    Wed 28 Oct, 21:53–22:59
    Lasted 1 h 6 min
    67peak reports

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • The US737
  • Japan52
  • Canada50
  • Australia35
  • Germany23
  • India23
  • Poland21
  • Brazil20

Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services

Troubleshooting

How to fix Cursor not working

Cursor is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach cursor.sh over your own connection, right now. Nothing is sent to us or stored.

  1. Reload the window

    Press Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows and Linux, then run Developer: Reload Window. This restarts the editor process without closing your files, and it clears the stuck state behind a chat panel that spins forever or a tab that stops responding. Try it first because it takes a few seconds.

  2. Sign out and back in

    Open Cursor Settings with Cmd+Shift+J or Ctrl+Shift+J, go to General, and sign out, then sign back in. Session tokens go stale, and the app then throws errors about authentication or a missing subscription even though your account is fine. A fresh sign-in issues a new token.

  3. Check proxy and network settings

    Open Cursor Settings, find the Network section, and turn off any HTTP proxy you set there if you are not behind one. A VPN or a stale proxy can block requests to the model backend, which shows up as a connection failure or a request that never finishes. Switch networks once to see if the problem follows the machine.

  4. Reinstall the current build

    Quit the app fully, then install the current build over the old one; your settings and extensions survive a normal reinstall. If chat still fails, open the Command Palette and run Developer: Toggle Developer Tools, then read the Console tab for the failing request before you report it. The official status page at https://status.cursor.com and the help centre at https://docs.cursor.sh/ cover known outages and setup details.

While Cursor is down: what to use instead

  • VS Code with GitHub Copilot Use it when you need inline completions and chat, since you can keep working in a familiar editor while the app is unavailable.
  • JetBrains AI Assistant If your project already lives in a JetBrains IDE, its assistant can explain code and draft changes without you switching tools.
  • Claude Code For terminal-heavy work, it can read files and run commands from the command line when the app's chat is down.
  • ChatGPT Handy for quick explanations and snippets when the editor chat fails.
Your device

Fix Cursor on Windows, Mac, Android and iPhone

Cursor on Windows

Fix
To fix Cursor on Windows, try restarting the application as administrator or checking if your Windows Defender Firewall is blocking its internet access. You can also reinstall the editor using the official installer if files are corrupted.
Check
Check if Cursor is down on Windows by verifying if the AI features fail to connect while your browser works normally. You can also check the developer console within the editor for network connection errors.
Command Prompt
ping cursor.shTest whether cursor's servers reply
nslookup cursor.shCheck that cursor's DNS resolves
tracert cursor.shTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Cursor on Mac

Fix
Fix Cursor on macOS by force quitting the app and clearing its application cache in your Library folder. Ensure that the app has the necessary permissions under System Settings to access your local network.
Check
To tell if Cursor is down on a Mac, check if the editor displays connection timeout warnings when querying the AI. You can also verify your internet connection by trying to load the Cursor website.
Terminal
ping -c 4 cursor.shTest whether cursor's servers reply
nslookup cursor.shCheck that cursor's DNS resolves
traceroute cursor.shTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Cursor on Android

Fix
Since Cursor is a desktop IDE, troubleshoot account issues on Android by clearing your mobile browser's cache to access the Cursor dashboard. Ensure your device is not connected to a VPN that blocks the service.
Check
Check if the Cursor service is down on Android by attempting to log into your account dashboard on the Cursor website. If the login portal fails to load, the backend services may be experiencing an outage.

Cursor on iPhone and iPad

Fix
Fix Cursor-related web issues on iOS by clearing your Safari browser history and disabling active VPNs. Ensure your mobile network is stable if you are managing your Cursor account or subscription.
Check
To tell if Cursor is down on iOS, try accessing the official Cursor login portal via your mobile browser. If the page loads but you cannot authenticate, the authentication servers may be offline.
Same time

Problems at the same time as Cursor

Since 5 October, all 4 of Cursor's spikes in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

Most often at the same time

How many of Cursor's spikes overlapped one of theirs.

During the latest spike

Cursor: Sat 31 Oct, 03:33 to 03:59

14 more services. Red dot: outage. Amber dot: elevated reports.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report Cursor problems

The busiest hour for reports about Cursor is 23:00 to 00:00 Central European time, and the busiest day is Thursday.

By hour of the day

  • 00:00 to 01:00: 0.09 reports on an average day
  • 01:00 to 02:00: 0.12 reports on an average day
  • 02:00 to 03:00: 0.28 reports on an average day
  • 03:00 to 04:00: 0.24 reports on an average day
  • 04:00 to 05:00: 0.1 reports on an average day
  • 05:00 to 06:00: 0.41 reports on an average day
  • 06:00 to 07:00: 0.89 reports on an average day
  • 07:00 to 08:00: 1.1 reports on an average day
  • 08:00 to 09:00: 0.28 reports on an average day
  • 09:00 to 10:00: 0.01 reports on an average day
  • 10:00 to 11:00: 0.03 reports on an average day
  • 11:00 to 12:00: 0.18 reports on an average day
  • 12:00 to 13:00: 0.07 reports on an average day
  • 13:00 to 14:00: 0.19 reports on an average day
  • 14:00 to 15:00: 0.22 reports on an average day
  • 15:00 to 16:00: 0.27 reports on an average day
  • 16:00 to 17:00: 0.34 reports on an average day
  • 17:00 to 18:00: 0.27 reports on an average day
  • 18:00 to 19:00: 0.5 reports on an average day
  • 19:00 to 20:00: 0.47 reports on an average day
  • 20:00 to 21:00: 0.52 reports on an average day
  • 21:00 to 22:00: 0.15 reports on an average day
  • 22:00 to 23:00: 0.16 reports on an average day
  • 23:00 to 00:00: 2.2 reports on an average day

By day of the week

  • Monday: 1.8 reports on an average Monday
  • Tuesday: 1.5 reports on an average Tuesday
  • Wednesday: 9.5 reports on an average Wednesday
  • Thursday: 26 reports on an average Thursday
  • Friday: 22 reports on an average Friday
  • Saturday: 5.1 reports on an average Saturday
  • Sunday: 0.63 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 25 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when Cursor goes down

Cursor is an AI code editor that developers use for tab completions and chat inside a VS Code-style workspace. When those AI features stall, you can still open and save files locally, but the loop of writing and testing code grinds to a halt.

An outage often starts with tab completion going quiet, chat prompts hanging, inline edits failing to apply, and codebase questions timing out. The local editor still opens files, so you may not notice until you ask for an AI action and get a spinner or a generic error. Failures are often partial: one feature can break while another still answers. The site does not ping or probe the service; the count at the top of the page only reflects user problem reports above their usual level in 15-minute windows over the last 24 hours, while the official status page and help centre cover confirmed incidents and setup fixes.

Servers and network

Cursor IP address, servers and network

IPv4 address
76.76.21.21
IPv6
Not offered
Network
AS16509 · Amazon.com, Inc., registered in the United States
Served through
Vercel · our check was answered by its Frankfurt (FRA) data centre
DNS hosted by
Amazon Route 53
HTTPS certificate
Issued by Let's Encrypt, valid until 23 Jan 2027 (83 days)
HTTP/3
Not advertised
Our check
Answered in 115 ms

Checked from our server in Frankfurt, Germany, 19 h ago, for cursor.sh. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from cursor.sh. Fastest from Paris (37 ms), slowest from Warsaw (117 ms). Every location connected to the same address, on Amazon.com, Inc. (AS16509).

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 30838 ms76.76.21.21
ViennaAustriaUp · HTTP 30866 ms76.76.21.21
MilanItalyUp · HTTP 30851 ms76.76.21.21
ParisFranceUp · HTTP 30837 ms76.76.21.21
AmsterdamNetherlandsUp · HTTP 30844 ms76.76.21.21
MadridSpainUp · HTTP 30871 ms76.76.21.21
WarsawPolandUp · HTTP 308117 ms76.76.21.21
Los AngelesUSAUp · HTTP 30859 ms76.76.21.21
São PauloBrazilUp · HTTP 30852 ms76.76.21.21
SingaporeSingaporeUp · HTTP 30882 ms76.76.21.21
TokyoJapanUp · HTTP 30893 ms76.76.21.21

Checked with check-host.net from its servers in these cities 19 h ago, for cursor.sh. Time is how long each server took to load the page.

Questions

Cursor FAQ

Is Cursor down right now?
The status at the top of this page shows whether reports for Cursor are above their usual level, counted in short windows over the past day. If it points to a wider problem, the official status page is the place for a company-confirmed outage. To check your side, try the app on another network or device, then open a small local file; if the same failure follows you across networks, the problem is probably not your machine.

Why does Cursor Tab stop working while Chat still replies?
A partial outage can hit one part of the service and leave another usable. Restart the editor. Test Tab in a small file on another network, then sign out and back in if completions stay dead everywhere.

Why does Cursor Chat fail to connect on a work VPN?
Corporate VPNs and proxies often block the long-lived connection Chat needs, while the rest of the editor keeps running. Test the same account off the VPN. If Chat works on a phone hotspot, your office network is the place to look, and the proxy setting in the app is worth a check if your team requires one.

Will a Cursor outage affect my paid subscription or billing?
A service problem does not pause or cancel a paid plan by itself. Billing is separate. If a charge looks wrong after an outage, contact support through the help centre with your account email and receipt, and do not open a second subscription to work around a temporary failure.

Why is Cursor stuck on indexing my codebase?
Indexing can stall on a large repo or a network that drops the upload. Open a smaller folder. Add the heavy paths to your ignore rules, then restart the app; if indexing fails across every project, check the official status page before you rebuild the index again.
For your site

Put the Cursor status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Cursor status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/cursor/"><img src="https://isitdownrightnow.app/badge/cursor.svg" alt="Cursor status" height="20"></a>
Markdown, for README files
[![Cursor status](https://isitdownrightnow.app/badge/cursor.svg)](https://isitdownrightnow.app/services/cursor/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Cursor

The status on this page comes from user-submitted problem reports for Cursor, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Cursor, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Cursor's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.