Looking for an update now? Check the current status, or follow Cursor for future changes.
45.6%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
36.7%
30
19
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time.
investigating
We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.
A fix has been implemented and we are monitoring for service restoration.
identified
The root cause has been identified and a fix is being implemented.
investigating
Customers using Cloud Agents with Dockerfile-based builds may be unable to create new builds. Existing Cloud Agents continue to run on their current image; only new Dockerfile builds are affected.
Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7
We are investigating degraded performance for requests that use Grok models. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok models are used. Other models are unaffected.
We are investigating degraded performance for requests that use Grok 4.6. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok 4.6 is used. Other models are unaffected.
Sign-in is recovering. The issue came from our authentication provider, who has identified the cause and is seeing recovery on their side. We are monitoring to confirm everything is back to normal.
investigating
We are investigating an issue affecting sign-in. Signing in, signing out, and loading the dashboard may hang or fail. If you are already signed in, your session should continue to work normally. We will provide another update shortly.
A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.
identified
The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.
investigating
We are investigating a service degradation affecting Grok Bot.
A fix has been implemented and we are monitoring for service restoration.
investigating
Affected services are back to normal operation. Our team continues to monitor everything closely.
investigating
We are continuing to investigate this issue. Cloud Agents, Automations, and Review Agents (resulting from Cloud Agents) are affected. Bugbot is not affected.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue. We will provide updates as more information becomes available.
investigating
We are investigating a service degradation affecting Cloud Agents and Automations
Legacy Incident Archive
109 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Grok 4.6 availability issues
minorSource not attested
Last archived state: resolved
View archived record details
IDE
monitoring
Grok 4.6 is operating normally again. We’re monitoring to ensure continued stability.
investigating
Customers may encounter errors when using Grok 4.6. We’re investigating and will share updates as we learn more.
We’re seeing signs of recovery, consistent with our upstream dependency’s latest status updates. We’re continuing to monitor our service health and GitHub's upstream status (https://www.githubstatus.com/)
investigating
We are currently investigating this issue. We will provide updates as more information becomes available.
investigating
We are investigating a service degradation affecting Automations, Cloud Agents, Review Agents and Codebase related to a GitHub degradation reported in GitHub's status page: https://www.githubstatus.com/
Investigating service degradation
minorSource not attested
Last archived state: resolved
View archived record details
AutomationsCLICloud Agentscursor.comIDE
monitoring
A fix has been implemented and we are monitoring for service restoration.
investigating
We are investigating a service degradation for requests that use Grok 4.6 (non-fast).
Users may experience slowness and high error rates. Other models are unaffected.
Investigating service degradation — Automations, Cloud Agents, and IDE
majorSource not attested
Last archived state: resolved
View archived record details
investigating
All systems and components are operating as expected, but due to a service outage for one of our model providers, agent surfaces using Anthropic Models Claude Mythos 5, Claude Fable 5, and Claude Sonnet 5 may run into issues.
Investigating service degradation — Bugbot and Cloud Agents
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating a service degradation affecting Cloud Agents and Bugbot due to an ongoing GitHub outage. Users may see failures or delays when starting or running Cloud Agents and when Bugbot attempts to run.
Investigating service degradation
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating degraded performance for requests that use Claude Fable. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Claude Fable is used. Other models are unaffected.
Investigating service degradation — Automations, Cloud Agents, and IDE
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating degraded performance for requests that use Composer 2.5. Users may see failed or retried requests in Automations, Cloud Agents, and the IDE when Composer 2.5 is used. Other models are unaffected.
Investigating service degradation — Automations, Cloud Agents, and IDE
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for service restoration.
monitoring
We are continuing to monitor this issue.
investigating
We found the root cause and are working on implementing a fix.
investigating
We are currently investigating this issue. We will provide updates as more information becomes available.
investigating
This service degradation is affecting Claude Fable 5 as well.
investigating
We are investigating a service degradation affecting Automations, Cloud Agents, and IDE. Affected agent surfaces: Composer, Claude Fable 5
MCP authentication failures in Automations and Cloud Agents
minorSource not attested
Last archived state: resolved
View archived record details
identified
The root cause has been identified and a fix is being implemented.
investigating
We are investigating an issue where users are unable to authenticate with MCP servers in Automations and Cloud Agents. Affected runs may fail to connect to their MCP tools.
Degraded Performance for Grok 4.5
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring for service restoration.
investigating
We are investigating a service degradation with Grok 4.5.
