Grok Bot is currently degraded
Grok Bot is degraded. xAI is investigating the problem.
State
Investigating
Started
Ongoing for
1 h 3 min
Worst impact
Degraded
Timeline
1 updateInvestigating
1 h 3 min 100%
Updates
Times in UTCAs posted by xAI
Grok Bot is currently degraded, and our team is investigating.
Affected components
1xAI in the last 90 days
Full historyIncidents in 90 days
54
Days with an incident
32
Median duration
50 min
This incident
1.3× the median
Other xAI incidents
All incidentsxAI·Computer use in Grok Bot fails for users in a few regions.
Computer use in Grok Bot did not work for users in a few regions. xAI reports that the incident is resolved. The outage lasted about 14 minutes.
xAI·composer-2.5 degraded
xAI reports degraded Composer 2.5 requests. The problem affects Automations, Bugbot, Cloud Agents, CLI, Cursor IDE (Desktop), and Cursor IDE (iOS). xAI resolved the incident after 50 minutes.
xAI·Degraded Performance - Grok Bot
Grok Bot had degraded performance. xAI investigated the errors and then identified and resolved the issue. The outage is resolved and it lasted 75 minutes.
xAI·3 "Slow clones from GH due to Github degradation"
Slow clones from GitHub affected Bugbot and Cloud Agents. xAI reports that the incident is resolved. The incident lasted 1 hour and 12 minutes.
xAI·Issues with source control integrations
xAI reports that source control provider integrations did not work in Cursor IDE (Desktop) and Grok Bot. The issue is resolved. It lasted 75 minutes.
Follow xAI
Your coding agent knows when xAI is down, and tells you when a failure is theirs, not yours. You can also get xAI incidents in a feed reader or in Slack.
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 "xai" and tell me if xAI 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.
https://outages.cc/feed.xml?providers=xai/feed subscribe https://outages.cc/feed.xml?providers=xaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane