xAI reported "Grok Bot is currently degraded" on its status page at 2026-11-06 13:57 UTC. Grok Bot is degraded. xAI reports that the incident is resolved. The outage lasted 1 hour and 17 minutes.

xAI lists these components: Grok Bot.

When did the incident start and end?

It started at 2026-11-06 13:57 UTC and ended at 2026-11-06 15:15 UTC. It lasted 1 h 17 min.

How do I get alerts for xAI?

Subscribe to the xAI live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of xAI. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

xAIIncident ·

Grok Bot is currently degraded

ResolvedOfficial update

Grok Bot is degraded. xAI reports that the incident is resolved. The outage lasted 1 hour and 17 minutes.

State

Resolved

Started

Lasted

1 h 17 min

Worst impact

Degraded

Timeline

2 updates

13:5714:1714:3614:5515:15

DegradedUpdate postedTimes in UTC

Investigating

1 h 17 min 100%

Updates

Times in UTC

As posted by xAI

Resolved

This issue has been resolved.

Investigating

Grok Bot is currently degraded, and our team is investigating.

Affected components

Grok Bot

xAI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

54 min

This incident

1.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

9 h 34 min

median 54 min

90 days agoToday

Other xAI incidents

All incidents

xAI·Computer use in Grok Bot fails for users in a few regions.

Computer use in Grok Bot fails for users in a few regions. xAI identified the issue and applied a fix. The issue is resolved and the failure lasted 14 minutes.

Resolved

xAI·composer-2.5 degraded

xAI reports degraded Composer 2.5 requests. The issue affected Automations, Bugbot, Cloud Agents, CLI, Cursor IDE (Desktop), and Cursor IDE (iOS). xAI resolved the issue after 50 minutes.

Resolved

xAI·Degraded Performance - Grok Bot

Grok Bot had degraded performance. xAI reports that the issue is resolved. The outage lasted 1 hour and 15 minutes.

Resolved

xAI·3 "Slow clones from GH due to Github degradation"

Slow clones from GitHub affected Bugbot and Cloud Agents. xAI reports that this incident is resolved. The incident lasted 1 hour and 12 minutes.

Resolved

xAI·Issues with source control integrations

xAI reports issues with source control provider integrations in Cursor IDE (Desktop) and Grok Bot. xAI investigated the reports. The issue is resolved and lasted 75 minutes.

Resolved

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.

Prompt

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.live/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.

RSS

https://outages.live/feed.xml?providers=xai

Slack

/feed subscribe https://outages.live/feed.xml?providers=xai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane