outages.live
Live
xAIIncident ·

Elevated errors for OpenAI model requests

ResolvedOfficial update
0

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.

State

Resolved

Started

Lasted

34 min

Worst impact

Degraded

Timeline

3 updates
23:1023:1823:2723:3523:44
DegradedUpdate postedTimes in UTC

Investigating

32 min 94%

Monitoring

2 min 6%

Updates

Times in UTC

As posted by xAI

Resolved

This incident has been resolved.

Monitoring

We're seeing recovery and are continuing to monitor. We'll share another update soon.

Investigating

We're investigating elevated errors affecting requests to OpenAI models. Some users may see failed or incomplete responses. Other models are unaffected and can be used in the meantime. We'll share another update as soon as we have more information.

Affected components

5
AutomationsCloud AgentsCLICursor IDE (Desktop)Third-party models

xAI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

55

Days with an incident

33

Median duration

50 min

This incident

31% shorter than the median

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

9 h 34 min
median 50 min
90 days agoToday

Other xAI incidents

All incidents

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

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

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