Live
X

xAI

xAI is operational

Checked 59 s ago Operational

History

90 days agoToday

Incidents in 90 days

48

Days with an incident

28

Median duration

45 min

Longest incident

9 h 34 min

Components

25

Grok

grok.com Operational
90 days ago3 days with an incidentToday
Grok (iOS) Operational
90 days ago1 day with an incidentToday
Grok (Android) Operational
90 days ago1 day with an incidentToday
Grok in X Operational
90 days agoNo incidentsToday
Imagine Operational
90 days ago1 day with an incidentToday
Voice Operational
90 days ago2 days with an incidentToday

Cursor

Cursor IDE (iOS) Operational
90 days ago13 days with an incidentToday
Cursor IDE (Desktop) Operational
90 days ago16 days with an incidentToday
Cloud Agents Operational
90 days ago20 days with an incidentToday
CLI Operational
90 days ago14 days with an incidentToday
Automations Operational
90 days ago14 days with an incidentToday
BugBot Operational
90 days ago3 days with an incidentToday
Review Agents Operational
90 days ago7 days with an incidentToday
Grok Bot Operational
90 days ago21 days with an incidentToday
cursor.com Operational
90 days ago9 days with an incidentToday

API

Global (api.x.ai) Operational
90 days ago2 days with an incidentToday
US (us.api.x.ai) Operational
90 days ago1 day with an incidentToday
EU (eu-west-1.api.x.ai) Operational
90 days agoNo incidentsToday

Services

Console Operational
90 days agoNo incidentsToday
Docs Operational
90 days agoNo incidentsToday
Origin Operational
90 days ago4 days with an incidentToday
x.ai Operational
90 days agoNo incidentsToday
Single Sign-On Operational
90 days agoNo incidentsToday
Admin APIs Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane