iszdown
Menu
Service status & outage reports

Is Cursor down?

Check Cursor availability, incident history, downtime reports, and website performance.

https://www.cursor.com/ ↗
Provider reports operational

Mapped components are operational in the latest status update; individual experiences can vary.

0 recorded outage reports · rolling 24 hours

Text version ↗

My watchlist

Estimated down reports for Cursor

Last 24 hours

There is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.

Last collection attempt: 2026-10-20 07:35:17 UTC · Insufficient activity.

No user-submitted outage reports in the last 24 hours.

Cursor outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

NovDecJanFebMarAprMayJunJulAugSepOct
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Cursor website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-10-22 00:11:55 UTC.

Checked address: https://www.cursor.com/

DNS lookup: 2 ms · TCP connection: 1 ms · TLS handshake: 7 ms. Certificate expires 2026-11-24; trusted connection: yes.

100%
Successful website checks (24h)
136 successful / 136 measurable checks

120 ms
Median response time

303 ms
95th percentile response time

Successful website response times, 0 to 557 milliseconds557 ms0 ms2026-10-21T12:38:37.000Z: 137 ms2026-10-21T12:43:46.000Z: 105 ms2026-10-21T12:48:55.000Z: 95 ms2026-10-21T12:54:05.000Z: 220 ms2026-10-21T12:59:11.000Z: 235 ms2026-10-21T13:04:19.000Z: 303 ms2026-10-21T13:09:29.000Z: 87 ms2026-10-21T13:14:39.000Z: 306 ms2026-10-21T13:19:49.000Z: 125 ms2026-10-21T13:24:57.000Z: 101 ms2026-10-21T13:30:04.000Z: 140 ms2026-10-21T13:35:09.000Z: 159 ms2026-10-21T13:40:17.000Z: 101 ms2026-10-21T13:45:25.000Z: 113 ms2026-10-21T13:50:33.000Z: 90 ms2026-10-21T13:55:43.000Z: 120 ms2026-10-21T14:00:51.000Z: 122 ms2026-10-21T14:06:00.000Z: 87 ms2026-10-21T14:11:09.000Z: 83 ms2026-10-21T14:16:17.000Z: 178 ms2026-10-21T14:21:25.000Z: 94 ms2026-10-21T14:26:35.000Z: 124 ms2026-10-21T14:31:45.000Z: 128 ms2026-10-21T14:36:55.000Z: 89 ms2026-10-21T14:42:01.000Z: 177 ms2026-10-21T14:47:07.000Z: 319 ms2026-10-21T14:52:13.000Z: 98 ms2026-10-21T14:57:17.000Z: 112 ms2026-10-21T15:02:23.000Z: 98 ms2026-10-21T15:07:29.000Z: 120 ms2026-10-21T15:12:35.000Z: 148 ms2026-10-21T15:17:43.000Z: 120 ms2026-10-21T15:22:49.000Z: 114 ms2026-10-21T15:27:57.000Z: 119 ms2026-10-21T15:33:05.000Z: 105 ms2026-10-21T15:38:09.000Z: 125 ms2026-10-21T15:43:17.000Z: 139 ms2026-10-21T15:48:25.000Z: 253 ms2026-10-21T15:53:35.000Z: 114 ms2026-10-21T15:58:43.000Z: 246 ms2026-10-21T16:03:51.000Z: 124 ms2026-10-21T16:09:01.000Z: 151 ms2026-10-21T16:14:11.000Z: 90 ms2026-10-21T16:19:21.000Z: 90 ms2026-10-21T16:24:29.000Z: 125 ms2026-10-21T16:29:37.000Z: 161 ms2026-10-21T16:34:41.000Z: 151 ms2026-10-21T16:39:47.000Z: 97 ms2026-10-21T16:44:51.000Z: 471 ms2026-10-21T16:49:59.000Z: 131 ms2026-10-21T16:55:07.000Z: 203 ms2026-10-21T17:00:17.000Z: 106 ms2026-10-21T17:05:27.000Z: 97 ms2026-10-21T17:10:36.000Z: 126 ms2026-10-21T17:15:45.000Z: 109 ms2026-10-21T17:20:55.000Z: 427 ms2026-10-21T17:26:05.000Z: 108 ms2026-10-21T17:31:11.000Z: 109 ms2026-10-21T17:36:21.000Z: 109 ms2026-10-21T17:41:30.000Z: 112 ms2026-10-21T17:46:35.000Z: 270 ms2026-10-21T17:51:39.000Z: 158 ms2026-10-21T17:56:45.000Z: 148 ms2026-10-21T18:01:53.000Z: 154 ms2026-10-21T18:07:01.000Z: 120 ms2026-10-21T18:12:11.000Z: 110 ms2026-10-21T18:17:19.000Z: 97 ms2026-10-21T18:22:28.000Z: 116 ms2026-10-21T18:27:35.000Z: 167 ms2026-10-21T18:32:43.000Z: 105 ms2026-10-21T18:37:53.000Z: 469 ms2026-10-21T18:43:03.000Z: 126 ms2026-10-21T18:48:13.000Z: 118 ms2026-10-21T18:53:21.000Z: 123 ms2026-10-21T18:58:30.000Z: 243 ms2026-10-21T19:03:39.000Z: 93 ms2026-10-21T19:08:45.000Z: 123 ms2026-10-21T19:13:55.000Z: 108 ms2026-10-21T19:19:05.000Z: 103 ms2026-10-21T19:24:15.000Z: 114 ms2026-10-21T19:29:23.000Z: 106 ms2026-10-21T19:34:31.000Z: 120 ms2026-10-21T19:39:41.000Z: 116 ms2026-10-21T19:44:49.000Z: 145 ms2026-10-21T19:49:58.000Z: 177 ms2026-10-21T19:55:07.000Z: 129 ms2026-10-21T20:00:17.000Z: 129 ms2026-10-21T20:05:25.000Z: 128 ms2026-10-21T20:10:33.000Z: 117 ms2026-10-21T20:15:43.000Z: 133 ms2026-10-21T20:20:51.000Z: 115 ms2026-10-21T20:26:00.000Z: 107 ms2026-10-21T20:31:09.000Z: 107 ms2026-10-21T20:36:18.000Z: 557 ms2026-10-21T20:41:27.000Z: 192 ms2026-10-21T20:46:35.000Z: 129 ms2026-10-21T20:51:45.000Z: 124 ms2026-10-21T20:56:53.000Z: 91 ms2026-10-21T21:02:01.000Z: 124 ms2026-10-21T21:07:09.000Z: 152 ms2026-10-21T21:12:17.000Z: 86 ms2026-10-21T21:17:25.000Z: 105 ms2026-10-21T21:22:33.000Z: 104 ms2026-10-21T21:27:43.000Z: 178 ms2026-10-21T21:32:53.000Z: 127 ms2026-10-21T21:37:59.000Z: 103 ms2026-10-21T21:43:03.000Z: 118 ms2026-10-21T21:48:09.000Z: 141 ms2026-10-21T21:53:13.000Z: 129 ms2026-10-21T21:58:19.000Z: 132 ms2026-10-21T22:03:23.000Z: 161 ms2026-10-21T22:08:29.000Z: 124 ms2026-10-21T22:13:33.000Z: 114 ms2026-10-21T22:18:39.000Z: 92 ms2026-10-21T22:23:43.000Z: 98 ms2026-10-21T22:28:53.000Z: 117 ms2026-10-21T22:33:59.000Z: 132 ms2026-10-21T22:39:09.000Z: 100 ms2026-10-21T22:44:19.000Z: 94 ms2026-10-21T22:49:29.000Z: 121 ms2026-10-21T22:54:39.000Z: 109 ms2026-10-21T22:59:49.000Z: 134 ms2026-10-21T23:04:58.000Z: 109 ms2026-10-21T23:10:07.000Z: 106 ms2026-10-21T23:15:17.000Z: 107 ms2026-10-21T23:20:25.000Z: 124 ms2026-10-21T23:25:33.000Z: 103 ms2026-10-21T23:30:43.000Z: 101 ms2026-10-21T23:35:53.000Z: 112 ms2026-10-21T23:41:01.000Z: 124 ms2026-10-21T23:46:11.000Z: 89 ms2026-10-21T23:51:21.000Z: 212 ms2026-10-21T23:56:31.000Z: 178 ms2026-10-22T00:01:39.000Z: 109 ms2026-10-22T00:06:47.000Z: 84 ms2026-10-22T00:11:55.000Z: 111 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Cursor official status · fetched 2026-10-21 23:59:00 UTC

8 mapped components · 0 reporting problems
ComponentProvider status
Automationsoperational
Review Agentsoperational
CLIoperational
Cloud Agentsoperational
cursor.comoperational
IDEoperational
Originoperational
Grok Botoperational

Official incident timeline

Elevated errors for Bitbucket Cloud integrations · resolved · 2026-10-21T17:53:46.938Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration.

  2. · investigating

    We are investigating an issue affecting Cursor's Bitbucket Cloud integration. More information: https://bitbucket.status.atlassian.com/incidents/ldlx0fdgls28.

Investigating service degradation · resolved · 2026-10-21T17:40:30.167Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · monitoring

    A fix has been implemented and we are monitoring for service restoration.

  3. · investigating

    We are investigating a service degradation affecting billing dashboards. You may notice errors in regards to billing, usage, and plan changes.

Investigating service degradation · resolved · 2026-10-21T10:37:17.623Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    We experienced service degradation affecting Anthropic models between 5:56 ET and 6:21 ET, which has since been resolved.

Investigating service degradation — Grok Bot · resolved · 2026-10-19T18:28:33.771Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · investigating

    We are investigating a service degradation affecting Grok Bot and grok.com. You may notice errors related to billing, plans, and usage.

Investigating service degradation — Grok Bot · resolved · 2026-10-19T17:21:36.794Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · monitoring

    A fix has been implemented and we are monitoring for service restoration.

  3. · investigating

    We are continuing to investigate this issue. We will provide updates as more information becomes available.

  4. · investigating

    We are investigating a service degradation affecting Grok Bot where routines may be delayed.

Investigating service degradation · resolved · 2026-10-19T13:52:07.400Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved. Thank you for your patience!

  2. · monitoring

    A fix has been implemented and we are monitoring for service restoration.

  3. · investigating

    We are investigating elevated errors for Anthropic Opus 5.5.

Elevated errors affecting Grok models · resolved · 2026-10-16T05:20:54.462Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved. Grok models in Cursor are working normally again.

  2. · monitoring

    A fix has been implemented and we are monitoring for service restoration.

  3. · investigating

    We are investigating elevated errors affecting Grok models in Cursor. Some requests may fail with a capacity error. Retrying the request or switching to another model may help.

Investigating service degradation — Grok Bot · resolved · 2026-10-14T21:04:46.631Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · identified

    We've identified the issue impacting Grok Bot for some users and are working on a fix.

  3. · investigating

    We are investigating a service degradation affecting Grok Bot and preventing some users from reaching their computers

Recovery tracker

Provider marked the incident resolved; at least three subsequent website checks succeeded.

6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

No sustained slowdown has been established against the earlier baseline.

Recent median: 111 ms · Earlier median: 120 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

  • is cursor down

Query “cursor” · observed 2026-10-22 00:01:38 UTC · 0 newly observed problem phrases.

Query “is cursor” · observed 2026-10-22 00:01:38 UTC · 0 newly observed problem phrases.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Cursor.

GitHub official status · 2026-10-22 00:11:10 UTC

No active incidents recorded.

Cloudflare official status · 2026-10-22 00:11:10 UTC

About Cursor status on Iszdown

Check Cursor availability, incident history, downtime reports, and website performance.

This page combines the available Cursor report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

8 product-matched official components are listed above. Latest public website measurement: 2026-10-22T00:11:55.000Z.

Visit the official Cursor website · Official provider status · How it works

What to check when Cursor is not working

These are troubleshooting suggestions, not a list of currently reported problems.

Cursor will not open

Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

Cursor is slow or only one feature fails

Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent Cursor outage history

Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

IncidentStarted (UTC)Recorded durationLast collected status
Elevated errors for Bitbucket Cloud integrations13 minresolved
Investigating service degradation114 minresolved
Investigating service degradation1 minresolved
Investigating service degradation — Grok Bot19 minresolved
Investigating service degradation — Grok Bot67 minresolved
Investigating service degradation27 minresolved
Elevated errors affecting Grok models416 minresolved
Investigating service degradation — Grok Bot318 minresolved

Frequently asked questions about Cursor

Is Cursor down right now?

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T00:12:35.000Z.

How many Cursor outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

Why does Cursor show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Cursor feature.

When was Cursor status last updated?

The latest status observation was 2026-10-21T23:59:00.000Z. Only matched product components and incidents are shown. The assessment is recent.

Has Cursor had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

How do I follow Cursor or report a problem?

Use “Watch this service” to save Cursor in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.

Related services to Cursor

Check a related product separately; its status can differ from Cursor.

Cursor