Cursor logo
ALL SYSTEMS OPERATIONAL

Cursor systems
are operational.

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

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

  • ALL SYSTEMS OPERATIONAL

    Cursor is up and running.

    Last incident resolved 2 days 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

You checked Cursor. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds, so the next answer arrives by email.

10 monitors free, 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%

Last 90 days

90-Day Health Summary

  • Total Incidents

    69

    Since Feb 2026

  • Major / Critical

    17

    17 high-impact incidents

  • Minor Incidents

    52

    Avg. 0.6 per day

  • Median Resolution

    1h 7m

    P95: 6h 34m

Cursor Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Investigating service degradation — cursor.com and IDE
Aug 27, 2026 · 7:31 PM 7m
Critical
Resolved
Details →
Investigating service degradation — Grok Bot
Aug 27, 2026 · 2:23 PM 42m
Minor
Resolved
Details →
Degraded performance of Grok models
Aug 25, 2026 · 8:34 PM 53m
Minor
Resolved
Details →
Degraded performance of Grok 4.6
Aug 25, 2026 · 2:54 PM 2h 42m
Minor
Resolved
Details →
Investigating service degradation — Automations
Aug 24, 2026 · 4:04 PM 29m
Minor
Resolved
Details →
Elevated errors for Claude Opus 5
Aug 24, 2026 · 5:38 AM 3h 12m
Minor
Resolved
Details →
Investigating service degradation
Aug 21, 2026 · 9:20 AM 47m
Minor
Resolved
Details →
Fable 5 unavailable
Aug 19, 2026 · 11:10 PM 2h 41m
Major
Resolved
Details →
Increased error rates for Composer 2.5
Aug 19, 2026 · 12:52 PM 3h 2m
Minor
Resolved
Details →
GitHub-connected Cloud Agent workflows degraded
Aug 18, 2026 · 7:47 PM 6h 56m
Minor
Resolved
Details →

How do they compare?

Alternatives to Cursor

Teams monitoring Cursor also watch

Other Monitored Services

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 69 incidents, of which 17 were major or critical. The median resolution time is 1h 7m.

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