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.
May 2026
Degraded Performance for Auto
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring for service restoration.
monitoring
A fix has been implemented and we are monitoring for service restoration.
investigating
We are investigating a service degradation with the Auto model option
Service Degradation on OpenAI Models
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 affecting OpenAI models.
Investigating Service Degradation
majorSource 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 currently investigating instability for the "auto" model provider.
investigating
We are continuing to investigate this issue.
investigating
We are investigating a service degradation.
Investigating service degradation — Cloud Agents, CLI, and IDE
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating a service degradation affecting Cloud Agents, CLI, and IDE. Affected agent surfaces: Anthropic models.
Degraded Performance for Agent Sessions
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 affecting IDE, Cloud Agents, and CLI. Affected agent surfaces: Composer.
Cloud Agents degradation
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue affecting Cloud Agents for a subset of users
April 2026
Elevated Error Rate for Anthropic Models
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating a service degradation.
Elevated Error Rate for Opus 4.7
Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating this issue.
we are experiencing issues with marketplace / extensions
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue. We will provide updates as more information becomes available.
