outages.live
Live
xAIIncident ·

Elevated errors for some requests

Partial outageOfficial update
0

xAI reports that some requests fail for cursor.com and Grok Bot. The failures include purchases and other billing actions. xAI identified the cause, put a fix in place, and now monitors the service.

State

Monitoring

Started

Ongoing for

46 min

Worst impact

Partial outage

Timeline

3 updates
20:0820:1920:3120:4220:54
Partial outageDegradedUpdate postedTimes in UTC

Investigating

37 min 80%

Monitoring

9 min 20%

Updates

Times in UTC

As posted by xAI

Monitoring

A fix has been implemented and we are monitoring for service restoration.

Investigating

We've identified the cause and are rolling out a fix. We'll share another update soon.

Investigating

We're investigating an issue that may cause some requests to fail, including purchases and other billing actions. We'll share another update as soon as we have more information.

Affected components

2
cursor.comGrok Bot

xAI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

57

Days with an incident

35

Median duration

54 min

This incident

About 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·Usage data slow or unavailable for some users.

On 10 November 2026, usage data on the grok.com dashboard and usage APIs was slow or showed no usage for some users. xAI reported the incident as investigating. xAI then reported the incident as resolved. The incident lasted 1 hour and 3 minutes.

Resolved · 1 affected

xAI·Elevated errors for OpenAI model requests

xAI reported elevated errors for requests to OpenAI models. The issue affected Automations, Cloud Agents, CLI, Cursor IDE (Desktop), and third-party models. xAI resolved the incident after 34 minutes.

Resolved

xAI·Grok Bot is currently degraded

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

Resolved · 1 affected

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

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