Cursor logo
ALL SYSTEMS OPERATIONAL

Cursor systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Feb 2026 · 119 incidents caught

Last checked: 6 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    Cursor is up and running.

    Last incident resolved 1 day ago


    No active incidents at this time. Noticed something?
  • 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

  • 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%

Last 90 days

90-Day Health Summary

  • Total Incidents

    66

    Since Feb 2026

  • Major / Critical

    21

    21 high-impact incidents

  • Minor Incidents

    45

    Avg. 0.5 per day

  • Median Resolution

    56m

    P95: 5h 10m

Cursor Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
MCP authentication failures in Automations and Cloud Agents
Aug 7, 2026 · 3:53 PM 2h 56m
Minor
Resolved
Details →
Degraded Performance for Grok 4.5
Aug 6, 2026 · 7:59 PM 28m
Minor
Resolved
Details →
Investigating service degradation — Cloud Agents & Automations
Aug 5, 2026 · 4:27 PM 2h 20m
Minor
Resolved
Details →
Investigating service degradation
Aug 5, 2026 · 8:01 AM 6h 34m
Minor
Resolved
Details →
Degraded performance for Cloud Agents
Aug 4, 2026 · 11:34 PM 27m
Major
Resolved
Details →
Investigating service degradation
Jul 31, 2026 · 7:50 PM 1h 19m
Critical
Resolved
Details →
Investigating service degradation — IDE
Jul 30, 2026 · 8:57 AM 51m
Minor
Resolved
Details →
Investigating service degradation — IDE
Jul 30, 2026 · 6:16 AM 17m
Minor
Resolved
Details →
Elevated errors affecting Anthropic models
Jul 29, 2026 · 7:58 PM 3h 17m
Critical
Resolved
Details →
Investigating Composer degradation
Jul 29, 2026 · 8:51 AM 2h 47m
Minor
Resolved
Details →

How do they compare?

Alternatives to Cursor

Teams monitoring Cursor also watch

Other Monitored Services

Get alerted the moment Cursor goes down.

No credit card · free plan · 2-minute setup

Common questions

Frequently Asked Questions

  • Is Cursor down today?

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

  • How often does Cursor go down?

    Based on our 90-day data, we've detected 66 incidents, of which 21 were major or critical. The median resolution time is 56m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • 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 detected a real service disruption, confirmed by multiple user reports, 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.