Cursor Status

GitHub Integrations Operational

Resolved - This incident has been resolved.
Mar 6, 09:16 UTC

Investigating - We are investigating this issue.
Mar 6, 08:47 UTC

Resolved - This incident has been resolved.
Mar 6, 08:44 UTC

Investigating - We are investigating this issue.
Mar 6, 08:31 UTC

Resolved - This incident has been resolved.
Mar 5, 20:48 UTC

Monitoring - Slack has implemented a fix and we are seeing signs of recovery. We are continuing to monitor the situation.
Mar 5, 20:37 UTC

Update - 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
Mar 5, 19:16 UTC

Identified - We are discussing with the upstream integration provider to identify the root cause.
Mar 5, 19:02 UTC

Investigating - We are investigating reports of `@Cursor` from Slack not triggering Cloud Agents.
Mar 5, 18:36 UTC

Resolved - This is now resolved
Mar 5, 20:30 UTC

Investigating - We are investigating this issue.
Mar 5, 20:25 UTC

Resolved - This incident has been resolved.
Mar 3, 20:04 UTC

Identified - 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/

Resolved - This incident has been resolved.
Feb 28, 02:53 UTC

Investigating - We are investigating this issue.
Feb 28, 02:53 UTC

Resolved - This incident has been resolved.
Feb 27, 02:44 UTC

Investigating - We are investigating this issue.
Feb 27, 02:18 UTC

Resolved - This incident has been resolved.
Feb 25, 00:01 UTC

Identified - Due to heavy traffic, we are experiencing rate limits in our integration with Github. We are working on mitigations.
Feb 24, 23:16 UTC

Investigating - We are investigating this issue.
Feb 24, 22:21 UTC

Resolved - This incident has been resolved.
Feb 24, 11:47 UTC

Monitoring - 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.
Feb 24, 11:41 UTC

Investigating - We have identified an issue with our authentication systems.
The team is investigating, and an update will be issued shortly.
Feb 24, 09:59 UTC