Elevated errors for Bitbucket Cloud integrations
Last updateresolvedOct 21 · 17:53 UTC
Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration.
Reported by Cursor on their status page.

checked Oct 23, 2026 7:06 PM UTC · Cursor's official status page
Cursor is up and running.
All components operational
Statusfield watches Cursor alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
34 reports published by Cursor in the last 30 days
When Cursor breaks, it is typically resolved in 1h 13m — median across 22 resolved incidents over 30 days.
resolvedOct 21 · 17:53 UTC
Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration.
Reported by Cursor on their status page.
resolvedOct 21 · 17:40 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 21 · 10:21 UTC
We experienced service degradation affecting Anthropic models between 5:56 ET and 6:21 ET, which has since been resolved.
Reported by Cursor on their status page.
resolvedOct 19 · 18:28 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 19 · 17:21 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 19 · 13:52 UTC
This incident has been resolved. Thank you for your patience!
Reported by Cursor on their status page.
resolvedOct 16 · 05:20 UTC
This incident has been resolved. Grok models in Cursor are working normally again.
Reported by Cursor on their status page.
resolvedOct 14 · 21:04 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 13 · 20:29 UTC
Between 10:52 AM and 1:29 PM PT on October 13, many Grok Bot routines started by webhooks, Slack, git, email and Linear events didn't run. Webhook callers may have seen an HTTP 400 "Automation run rate limit exceeded" error, and other triggers failed without an error. Your own usage didn't cause this. Routines are running normally again. Events sent during this window weren't processed and won't be retried automatically, so please resend anything important.
Reported by Cursor on their status page.
resolvedOct 13 · 03:07 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 9 · 23:09 UTC
This incident has been resolved. New Cloud Agents and Grok Bot sessions are starting normally again.
Reported by Cursor on their status page.
resolvedOct 9 · 21:42 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 8 · 20:51 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 8 · 15:31 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 7 · 17:25 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 6 · 23:04 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedOct 6 · 23:04 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 6 · 22:06 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedOct 6 · 22:06 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 6 · 18:56 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedOct 6 · 18:56 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 6 · 16:00 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedOct 6 · 16:00 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedOct 3 · 07:26 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedOct 3 · 07:26 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedSep 29 · 20:18 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedSep 29 · 20:18 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedSep 29 · 18:05 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedSep 28 · 20:36 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedSep 28 · 20:36 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedSep 26 · 00:32 UTC
This incident has been resolved.
Reported by Cursor on their status page.
resolvedSep 25 · 06:51 UTC
The service degradation affecting Grok Bot has been resolved.
Reported by Cursor on their status page.
resolvedSep 23 · 20:36 UTC
This incident has been resolved.
Reported by Cursor on their status page.
ResolvedSep 23 · 20:36 UTC
This incident has been resolved.
Reported by Cursor on their status page.