Cursor reported "3 "Slow clones from GH due to Github degradation"" on its status page at 2026-11-03 21:40 UTC. Cursor reports slow clones from GitHub. This affects Bugbot and Cloud Agents. Cursor is investigating and monitoring the GitHub mitigation.

Cursor lists these components: Bugbot, Cloud Agents.

When did the incident start and end?

It started at 2026-11-03 21:40 UTC. This page shows the end time when Cursor marks it resolved.

How do I get alerts for Cursor?

Subscribe to the Cursor live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Cursor. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

CursorIncident ·

3 "Slow clones from GH due to Github degradation"

NoticeOfficial update

Cursor reports slow clones from GitHub. This affects Bugbot and Cloud Agents. Cursor is investigating and monitoring the GitHub mitigation.

State

Investigating

Started

Ongoing for

1 h 6 min

Worst impact

Notice

Timeline

1 update

21:4021:5722:1322:3022:46

NoticeUpdate postedTimes in UTC

Investigating

1 h 6 min 100%

Updates

Times in UTC

As posted by Cursor

Investigating

We'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.

Affected components

BugbotCloud Agents

Cursor in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 7 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

9 h 34 min

median 1 h 7 min

90 days agoToday

Other Cursor incidents

All incidents

Cursor·Issues with source control integrations

Source control integrations do not work in the Cursor IDE and Grok Bot. Cursor reports that the issue is resolved. The outage lasted 75 minutes.

Resolved

Cursor·Service Degradation - Billing and Usage Dashboard

The billing and usage dashboard does not work on cursor.com and the Enterprise Dashboard. Cursor reports that the incident is resolved. The outage lasted about 5 hours and 15 minutes.

Resolved

Cursor·Multiple services degraded

This incident has been resolved.

Resolved

Cursor·Auto Review Degradation

This has been resolved

Resolved

Cursor·Cloud Agent Degradation

This incident has been resolved. Cloud Agent services have returned to normal operation.

Resolved

Follow Cursor

Your coding agent knows when Cursor is down, and tells you when a failure is theirs, not yours. You can also get Cursor incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cursor" and tell me if Cursor has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=cursor

Slack

/feed subscribe https://outages.cc/feed.xml?providers=cursor

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane