outages.live
Live
xAIIncident ·

3 "Slow clones from GH due to Github degradation"

ResolvedOfficial update
0

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

State

Resolved

Started

Lasted

1 h 12 min

Worst impact

Notice

Timeline

2 updates
21:4021:5822:1622:3422:53
NoticeUpdate postedTimes in UTC

Investigating

1 h 12 min 100%

Updates

Times in UTC

As posted by xAI

Resolved

GitHub has mitigated the Git operations incident, and Cloud Agent startup and Bugbot run times have returned to normal.

Investigating

We're seeing slower Cloud Agent startups and Bugbot runs caused by an ongoing GitHub incident affecting Git operations. GitHub has identified the issue and is rolling out a mitigation. We're monitoring and will update as their fix takes effect. You can track GitHub's status at githubstatus.com.

Affected components

2
BugbotCloud Agents

xAI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

50

Days with an incident

30

Median duration

52 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 52 min
90 days agoToday

Other xAI incidents

All incidents

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

xAI·Service Degradation - Billing and Usage Dashboard

This incident has been resolved.

Resolved

xAI·Multiple services degraded

This incident has been resolved.

Resolved

xAI·Grok Degradation

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

Resolved

xAI·Auto Review Degradation

This has been resolved

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