Cursor logo
ACTIVE INCIDENT

Cursor is
experiencing issues.

Pulsetic can detect an outage before the provider officially reports it. 216 incidents on record since Feb 2026

Last updated: 2 min ago · 0 user reports (24h)

  • OPERATIONAL · INVESTIGATING

    Degraded Gemini 4 Carbon

    Started 3 hours ago · Nov 19, 2026 · 4:01 PM UTC

    We are continuing to monitor an issue with an upstream provider affecting the Gemini 4 Carbon model. Some requests may fail intermittently while the provider works on a fix.


    View official incident → Having issues too?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

You checked Cursor. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked around the clock, so the next answer arrives by email.

10 monitors free, checked every 5 minutes, with email alerts on failure and recovery. No credit card.

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

90-Day Health Summary

  • Total Incidents

    81

    Aug 21 to Nov 19, 2026

  • Major / Critical

    19

    23% of the total

  • Minor Incidents

    62

    Avg. 0.7 per day

  • Median Resolution

    1h 2m

    P95: 5h 43m

Across all 4,387 services Pulsetic tracks, the incidents their status pages reported over the last 12 months had a median resolution time of 1h 58m, and 33% were rated major or critical by the provider. These numbers are calculated separately from the 90-day figures for Cursor above.

Source: The State of Uptime 2026, figures as of .

Cursor Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Degraded Gemini 4 Carbon
Nov 19, 2026 · 4:01 PM Ongoing
None
Investigating
Details →
Elevated errors for some requests
Nov 12, 2026 · 8:08 PM 1h 31m
Major
Resolved
Details →
Elevated errors for OpenAI model requests
Nov 9, 2026 · 11:10 PM 34m
Minor
Resolved
Details →
Grok Bot is currently degraded
Nov 6, 2026 · 1:57 PM 1h 17m
Minor
Resolved
Details →
Computer use in Grok Bot fails for users in a few regions.
Nov 6, 2026 · 11:49 AM 13m
Minor
Resolved
Details →
composer-2.5 degraded
Nov 5, 2026 · 3:06 PM 49m
Minor
Resolved
Details →
Degraded Performance - Grok Bot
Nov 5, 2026 · 12:34 AM 1h 14m
Minor
Resolved
Details →
3 "Slow clones from GH due to Github degradation"
Nov 3, 2026 · 9:40 PM 1h 12m
None
Resolved
Details →
Issues with source control integrations
Nov 2, 2026 · 9:09 AM 1h 15m
Minor
Resolved
Details →
Service Degradation - Billing and Usage Dashboard
Nov 1, 2026 · 5:38 AM 5h 14m
Minor
Resolved
Details →

How do they compare?

Alternatives to Cursor

Common questions

Frequently Asked Questions

  • Is Cursor down today?

    Check the status badge at the top of this page for the current status. Pulsetic follows the official status page and cross-references it with user reports to give you the most accurate picture.

  • How often does Cursor go down?

    Based on our 90-day data, we've recorded 81 incidents, of which 19 were major or critical. The median resolution time is 1h 2m.

  • How are outages detected?

    Pulsetic follows the official status page and records the incidents the provider posts there. Crowdsourced user reports and Pulsetic's own synthetic checks add an early warning, which can surface an issue before the official status page mentions it.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic recorded a service disruption from user reports and its own checks, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.