Cursor Outage History

Cursor is up right now

There were 48 Cursor outages since February 4, 2026 totaling 27h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cursor.com

Critical March 20, 2026

Service Degradation

Detected by Pingoru
Mar 20, 2026, 11:37 PM UTC
Resolved
Mar 21, 2026, 03:41 AM UTC
Duration
4h 3m
Timeline · 3 updates
  1. investigating Mar 20, 2026, 11:37 PM UTC

    We are investigating this issue.

  2. monitoring Mar 21, 2026, 12:36 AM UTC

    We continue to see service degradation for some users. We have identified what triggered the degradation and are working to gradually recover all services and functionality prioritizing agent workloads.

  3. resolved Mar 21, 2026, 03:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2026

Elevated Agent Errors

Detected by Pingoru
Mar 19, 2026, 10:30 AM UTC
Resolved
Mar 19, 2026, 10:30 AM UTC
Duration
Affected: IDE
Timeline · 1 update
  1. resolved Apr 24, 2026, 10:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 17, 2026

Elevated Errors for Opus 4.6

Detected by Pingoru
Mar 17, 2026, 08:42 PM UTC
Resolved
Mar 17, 2026, 08:42 PM UTC
Duration
Affected: AutomationsCLICloud AgentsIDE
Timeline · 1 update
  1. resolved Apr 24, 2026, 10:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2026

Degraded Performance for All Products

Detected by Pingoru
Mar 06, 2026, 09:22 AM UTC
Resolved
Mar 06, 2026, 09:22 AM UTC
Duration
Affected: AutomationsBugbotCLICloud Agentscursor.comIDECursor Marketplace
Timeline · 1 update
  1. resolved Apr 24, 2026, 10:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2026

Slack integration degradation

Detected by Pingoru
Mar 05, 2026, 06:36 PM UTC
Resolved
Mar 05, 2026, 08:48 PM UTC
Duration
2h 12m
Timeline · 5 updates
  1. investigating Mar 05, 2026, 06:36 PM UTC

    We are investigating reports of `@Cursor` from Slack not triggering Cloud Agents.

  2. identified Mar 05, 2026, 07:02 PM UTC

    We are discussing with the upstream integration provider to identify the root cause.

  3. identified Mar 05, 2026, 07:16 PM UTC

    We believe this degradation is related to an upstream Slack integration issue. We’re working with Slack on mitigations and will provide updates. You can follow the upstream status page at https://slack-status.com/2026-03/e63ca9cc0d76539c

  4. monitoring Mar 05, 2026, 08:37 PM UTC

    Slack has implemented a fix and we are seeing signs of recovery. We are continuing to monitor the situation.

  5. resolved Mar 05, 2026, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 3, 2026

Cloud Agents degradation due to GitHub outage

Detected by Pingoru
Mar 03, 2026, 07:42 PM UTC
Resolved
Mar 03, 2026, 08:04 PM UTC
Duration
21m
Timeline · 2 updates
  1. identified Mar 03, 2026, 07:42 PM UTC

    GitHub is experiencing an outage, with downstream impact on Cloud Agents. Notably, some Cloud Agents are failing to start because of upstream errors while cloning repositories from GitHub. More information can be found on the GitHub status page: https://www.githubstatus.com/

  2. resolved Mar 03, 2026, 08:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 1, 2026

Cursor.com Is Down

Detected by Pingoru
Mar 01, 2026, 02:53 AM UTC
Resolved
Mar 01, 2026, 02:53 AM UTC
Duration
Affected: Cloud Agentscursor.com
Timeline · 1 update
  1. resolved Apr 24, 2026, 10:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 28, 2026

cursor.com is Unavailable

Detected by Pingoru
Feb 28, 2026, 02:53 AM UTC
Resolved
Feb 28, 2026, 02:53 AM UTC
Duration
9s
Timeline · 2 updates
  1. investigating Feb 28, 2026, 02:53 AM UTC

    We are investigating this issue.

  2. resolved Feb 28, 2026, 02:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 27, 2026

Degraded Performance for Auto

Detected by Pingoru
Feb 27, 2026, 02:18 AM UTC
Resolved
Feb 27, 2026, 02:44 AM UTC
Duration
26m
Timeline · 2 updates
  1. investigating Feb 27, 2026, 02:18 AM UTC

    We are investigating this issue.

  2. resolved Feb 27, 2026, 02:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 24, 2026

Bugbot and Cloud Agents Degraded

Detected by Pingoru
Feb 24, 2026, 10:21 PM UTC
Resolved
Feb 25, 2026, 12:01 AM UTC
Duration
1h 40m
Timeline · 3 updates
  1. investigating Feb 24, 2026, 10:21 PM UTC

    We are investigating this issue.

  2. identified Feb 24, 2026, 11:16 PM UTC

    Due to heavy traffic, we are experiencing rate limits in our integration with Github. We are working on mitigations.

  3. resolved Feb 25, 2026, 12:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

Elevated Github Rate Limits

Detected by Pingoru
Feb 24, 2026, 11:28 AM UTC
Resolved
Feb 24, 2026, 11:28 AM UTC
Duration
Affected: BugbotCloud Agents
Timeline · 1 update
  1. resolved Apr 24, 2026, 10:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

Authentication Systems Degraded

Detected by Pingoru
Feb 24, 2026, 09:59 AM UTC
Resolved
Feb 24, 2026, 11:47 AM UTC
Duration
1h 48m
Timeline · 3 updates
  1. investigating Feb 24, 2026, 09:59 AM UTC

    We have identified an issue with our authentication systems. The team is investigating, and an update will be issued shortly.

  2. monitoring Feb 24, 2026, 11:41 AM UTC

    We have identified an issue with our authentication systems and have implemented mitigations. Our systems are currently recovering and we expect normal service to resume shortly.

  3. resolved Feb 24, 2026, 11:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 17, 2026

Degraded Performance for Sonnet & Opus

Detected by Pingoru
Feb 17, 2026, 05:30 PM UTC
Resolved
Feb 17, 2026, 07:35 PM UTC
Duration
2h 4m
Timeline · 2 updates
  1. investigating Feb 17, 2026, 05:30 PM UTC

    We are investigating this issue.

  2. resolved Feb 17, 2026, 07:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 11, 2026

Cloud Agents degradation

Detected by Pingoru
Feb 11, 2026, 05:18 PM UTC
Resolved
Feb 11, 2026, 06:52 PM UTC
Duration
1h 34m
Timeline · 4 updates
  1. investigating Feb 11, 2026, 05:18 PM UTC

    We are investigating reports of some Cloud Agents failing to start. The issue appears limited in scope and we recommend retrying while we are investigating.

  2. identified Feb 11, 2026, 05:29 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 11, 2026, 05:58 PM UTC

    A fix has been implemented and we are seeing signs of recovery.

  4. resolved Feb 11, 2026, 06:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2026

Degraded Performance for Opus 4.6 Fast

Detected by Pingoru
Feb 10, 2026, 10:14 PM UTC
Resolved
Feb 11, 2026, 03:15 AM UTC
Duration
5h
Timeline · 2 updates
  1. investigating Feb 10, 2026, 10:14 PM UTC

    We are investigating this issue.

  2. resolved Feb 11, 2026, 03:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 10, 2026

Bugbot elevated error rate

Detected by Pingoru
Feb 10, 2026, 05:08 PM UTC
Resolved
Feb 10, 2026, 07:36 PM UTC
Duration
2h 28m
Timeline · 2 updates
  1. investigating Feb 10, 2026, 05:08 PM UTC

    We are investigating this issue.

  2. resolved Feb 10, 2026, 07:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 9, 2026

Bugbot is Degraded

Detected by Pingoru
Feb 09, 2026, 07:51 PM UTC
Resolved
Feb 09, 2026, 08:23 PM UTC
Duration
31m
Timeline · 2 updates
  1. investigating Feb 09, 2026, 07:51 PM UTC

    Bugbot is degraded as a result of a Github outage. You can follow the upstream status page at https://www.githubstatus.com/incidents/lcw3tg2f6zsd

  2. resolved Feb 09, 2026, 08:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 9, 2026

Cloud Agents degradation due to third-party outage

Detected by Pingoru
Feb 09, 2026, 07:05 PM UTC
Resolved
Feb 09, 2026, 08:23 PM UTC
Duration
1h 18m
Timeline · 2 updates
  1. investigating Feb 09, 2026, 07:05 PM UTC

    Some Cloud Agents may fail to launch as a result of a Github outage. Other Cloud Agents features related to Github are also impacted. You can follow the upstream status page at https://www.githubstatus.com/incidents/lcw3tg2f6zsd

  2. resolved Feb 09, 2026, 08:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Cursor downtime and outages?

Pingoru polls Cursor's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Cursor reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Cursor alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Cursor for free

5 free monitors · No credit card required