No impact incident
Cursor: 3 "Slow clones from GH due to Github degradation"
Nov 3, 2026, 21:40 UTC
started
22:53 UTC
resolved
1 h 12 min
duration
Affected: Bugbot, Cloud Agents
Current status of Cursor: Operational — live Cursor status
Timeline
- Nov 3, 2026, 21:40 UTCinvestigatingWe're seeing slower Cloud Agent startups and Bugbot runs caused by an ongoing GitHub incident affecting Git operations. GitHub has identified the issue and is rolling out a mitigation. We're monitoring and will update as their fix takes effect. You can track GitHub's status at githubstatus.com.
- Nov 3, 2026, 22:53 UTCresolvedGitHub has mitigated the Git operations incident, and Cloud Agent startup and Bugbot run times have returned to normal.
Updates as published by Cursor (original).
Other services with incidents at the same time
This was part of a wider event: 119 services reported incidents within the hour.
- Ably 22:40 UTC · eu-west-1 NLB issues
- FloQast 22:24 UTC · Users unable to sign in with SSO on the APAC Database
- Vanta 22:18 UTC · Missing check results for GitHub pull requests
- Grafana Cloud 22:00 UTC · October usage report visualization issue
- OpenText 21:39 UTC · Fax2Mail and Core Messaging - Email experienced processing delays
- Hostinger 21:39 UTC · Emergency Server US-1419 Maintenance
- Zapier 21:03 UTC · Delayed or failed template recommendations and template setup
- GitHub 20:57 UTC · Incident with Git Operations
- SerpApi 20:45 UTC · [Google Search API] The "Site:" Operator is Ignored
More Cursor incidents
- November 6, 2026 Grok Bot is currently degraded
- November 6, 2026 Computer use in Grok Bot fails for users in a few regions.
- November 5, 2026 composer-2.5 degraded
- November 5, 2026 Degraded Performance - Grok Bot
- November 2, 2026 Issues with source control integrations
- November 1, 2026 Service Degradation - Billing and Usage Dashboard