Is Cursor down?
Check Cursor availability, incident history, downtime reports, and website performance.
https://www.cursor.com/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for Cursor
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-11 04:04:50 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Cursor outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
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-11-11 04:04:50 UTC.
Checked address: https://www.cursor.com/
DNS lookup: 1 ms · TCP connection: 3 ms · TLS handshake: 4 ms. Certificate expires 2027-01-25; trusted connection: yes.
100%
Successful website checks (24h)
280 successful / 280 measurable checks
107 ms
Median response time
264 ms
95th percentile response time
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-11-11 03:56:43 UTC
11 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| IDE | operational |
| Cursor IDE (iOS) | operational |
| CLI | operational |
| cursor.com | operational |
| Cloud Agents | operational |
| Automations | operational |
| Bugbot | operational |
| Grok Bot | operational |
| Third-party models | operational |
| Origin | operational |
| Enterprise Dashboard | operational |
Official incident timeline
Elevated errors for OpenAI model requests · resolved · 2026-11-09T23:44:34.000Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We're seeing recovery and are continuing to monitor. We'll share another update soon.
- · investigating
We're investigating elevated errors affecting requests to OpenAI models. Some users may see failed or incomplete responses. Other models are unaffected and can be used in the meantime. We'll share another update as soon as we have more information.
Grok Bot is currently degraded · resolved · 2026-11-06T15:15:07.000Z
Product match: components.
Read the provider’s incident report
- · resolved
This issue has been resolved.
- · investigating
Grok Bot is currently degraded, and our team is investigating.
Computer use in Grok Bot fails for users in a few regions. · resolved · 2026-11-06T12:03:16.000Z
Product match: components.
Read the provider’s incident report
- · resolved
The issue is resolved and computer use in Grok Bot is working normally again for all users.
- · investigating
We've identified an issue where computer use in Grok Bot is failing for users in some regions. Other Grok Bot features are working normally. Our team is working on a fix, and we'll share an update as soon as we have more information.
composer-2.5 degraded · resolved · 2026-11-05T15:56:32.000Z
Product match: components.
Read the provider’s incident report
- · resolved
This issue has been resolved
- · investigating
We are currently experiencing issues with Composer 2.5 requests
Degraded Performance - Grok Bot · resolved · 2026-11-05T01:49:31.000Z
Product match: components.
Read the provider’s incident report
- · resolved
We have identified and resolved the issue.
- · investigating
We are currently investigating errors with Grok Bot.
3 "Slow clones from GH due to Github degradation" · resolved · 2026-11-03T22:53:01.000Z
Product match: components.
Read the provider’s incident report
- · resolved
GitHub has mitigated the Git operations incident, and Cloud Agent startup and Bugbot run times have returned to normal.
- · investigating
We're seeing slower Cloud Agent startups and Bugbot runs caused by an ongoing GitHub incident affecting Git operations. GitHub has identified the issue and is rolling out a mitigation. We're monitoring and will update as their fix takes effect. You can track GitHub's status at githubstatus.com.
Issues with source control integrations · resolved · 2026-11-02T10:24:48.000Z
Product match: components.
Read the provider’s incident report
- · resolved
The issue is resolved.
- · investigating
We are investigating reports of issues with source control provider integrations in Cursor and Grok Bot.
Service Degradation - Billing and Usage Dashboard · resolved · 2026-11-01T10:53:33.000Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · investigating
We are continuing to work towards a resolution and will share more information as it becomes available.
- · investigating
We are investigating a service degradation affecting our billing and usage dashboard. We will share updates as more information becomes available.
Recovery tracker
No recent recovery can be established from available evidence.
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: 108 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 right now
- is cursor down
Query “is cursor” · observed 2026-11-11 03:53:30 UTC · 0 newly observed problem phrases.
Query “cursor” · observed 2026-11-11 03:49:24 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.
No active incidents recorded.
- Changes to Cloudflare Workers are not producing Event Subscription events · investigating
- Fedramp Customers have Delayed Purges · identified
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.
11 product-matched official components are listed above. Latest public website measurement: 2026-11-11T04:04:50.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.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Elevated errors for OpenAI model requests | 34 min | resolved | |
| Grok Bot is currently degraded | 77 min | resolved | |
| Computer use in Grok Bot fails for users in a few regions. | 14 min | resolved | |
| composer-2.5 degraded | 50 min | resolved | |
| Degraded Performance - Grok Bot | 75 min | resolved | |
| Issues with source control integrations | 75 min | resolved | |
| Service Degradation - Billing and Usage Dashboard | 315 min | resolved | |
| Multiple services degraded | 44 min | resolved |
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-11-11T04:08:32.000Z.
How many Cursor outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04:00: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-11-11T03:56:43.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.