xAI lists these components: Cursor IDE (Desktop), Grok Bot.

When did the incident start and end?

It started at 2026-11-02 09:09 UTC and ended at 2026-11-02 10:24 UTC. It lasted 1 h 15 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 · 2026-11-02 09:09 UTC

Issues with source control integrations

Q: What happened?

xAI reported "Issues with source control integrations" on its status page at 2026-11-02 09:09 UTC. 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.

ResolvedOfficial update

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.

State

Resolved

Started

2 h ago

2026-11-02 09:09 UTC

Lasted

1 h 15 min

until 2026-11-02 10:24 UTC

Worst impact

Degraded

Timeline

2 updates

09:0909:2809:4710:0510:24

DegradedUpdate postedTimes in UTC

Investigating

1 h 15 min 100%

Updates

Times in UTC

As posted by xAI

Resolved2026-11-02 10:24 UTC

The issue is resolved.

Investigating2026-11-02 09:12 UTC

We are investigating reports of issues with source control provider integrations in Cursor and Grok Bot.

Affected components

Cursor IDE (Desktop)Grok Bot

xAI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

46 min

This incident

1.7× the median

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

9 h 34 min

median 46 min

90 days agoToday

Other xAI incidents

All incidents

xAI·Service Degradation - Billing and Usage Dashboard

This incident has been resolved.

Resolvedresolved 1 d ago

xAI·Multiple services degraded

This incident has been resolved.

Resolvedresolved 2 d ago

xAI·Grok Degradation

This incident has been resolved. Grok.com, Grok Imagine, Grok Voice, Grok (iOS), and Grok (Android) have returned to normal performance.

Resolvedresolved 3 d ago

xAI·Auto Review Degradation

This has been resolved

Resolvedresolved 3 d ago

xAI·Cloud Agent Degradation

This incident has been resolved. Cloud Agent services have returned to normal operation.

Resolvedresolved 3 d ago

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