Elevated errors for Bitbucket Cloud integrations
DegradedAtlassian has reported the issue as resolved and they are continuing to monitor for service restoration.
Is Cursor down?
Cursor is up and running. Cursor is an AI code editor with its own inference backend.
Last 90 days
90 days agoToday
Cursor’s status page only shares its latest incidents, so just the last 52 days are shown; grey days have no data.
Worked out from the incidents Cursor reported, so it is an estimate and not a measurement.
Cursor reliability, last 90 days
50Incidents reported
4Full outages
1 hTypical duration
6 h 56 minLongest incident
Last incident: “Elevated errors for Bitbucket Cloud integrations”, yesterday.
Components
AutomationsOperational
Review AgentsOperational
CLIOperational
Cloud AgentsOperational
cursor.comOperational
IDEOperational
OriginOperational
Grok BotOperational
Recent incidents
Investigating service degradation
DegradedThis incident has been resolved.
Investigating service degradation
DegradedWe experienced service degradation affecting Anthropic models between 5:56 ET and 6:21 ET, which has since been resolved.
Investigating service degradation — Grok Bot
DegradedThis incident has been resolved.
Investigating service degradation — Grok Bot
DegradedThis incident has been resolved.
Questions
Is Cursor down right now?
Cursor’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
When was Cursor last down?
The most recent incident Cursor reported was “Elevated errors for Bitbucket Cloud integrations”, yesterday (2026-10-21 17:40 UTC). Its last full outage started 9 days ago.
Which parts of Cursor are tracked here?
Cursor reports 8 components on its status page, including Automations, Review Agents, CLI, Cloud Agents, cursor.com. Each is checked again whenever this page refreshes.
What should I do if Cursor is down?
Retry with exponential backoff, fall back to another model or provider if your product allows it, and avoid hammering the API while it recovers.
Cursor's agent won't respond but the IDE itself works?
The editor and the agent backends are separate components — Cursor lists IDE, Cloud Agents, Review Agents and the CLI individually, so chat/agent failures can happen while editing is unaffected.
Are Cursor tab completions part of the same status row?
Completions ride on Cursor's inference backend and the status page tracks agent features separately from the IDE. When completions lag but the IDE row is green, the degraded row usually names the feature involved.
How do I tell if Cursor is down for everyone or only for me?
If the status above is operational but Cursor still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
How can I get alerted when my own site goes down?
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.