outages.live
Live
xAIIncident · 2026-09-21 06:39 UTC

Investigating service degradation

ResolvedOfficial update

This incident has been resolved.

The latest update from xAI.

State

Resolved

Started

42 d ago

2026-09-21 06:39 UTC

Lasted

22 min

until 2026-09-21 07:00 UTC

Worst impact

Degraded

Timeline

2 updates
06:3906:4406:4906:5507:00
DegradedUpdate postedTimes in UTC

Investigating

22 min 100%

Updates

Times in UTC

As posted by xAI

Resolved2026-09-21 07:00 UTC

This incident has been resolved.

Investigating2026-09-21 06:39 UTC

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.

Affected components

5
AutomationsCloud AgentsCLICursor IDE (Desktop)Cursor IDE (iOS)

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

RSS
https://outages.cc/feed.xml?providers=xai
Slack
/feed subscribe https://outages.cc/feed.xml?providers=xai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane