xAI reported "Delayed responses in Grok Bot" on its status page at 2026-10-27 20:33 UTC.

xAI lists these components: Grok Bot.

When did the incident start and end?

It started at 2026-10-27 20:33 UTC and ended at 2026-10-27 20:43 UTC. It lasted 10 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.

XxAIIncident · 2026-10-27 20:33 UTC

Delayed responses in Grok Bot

ResolvedOfficial update

This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.

The latest update from xAI.

State

Resolved

Started

5 d ago

2026-10-27 20:33 UTC

Lasted

10 min

until 2026-10-27 20:43 UTC

Worst impact

Partial outage

Timeline

2 updates

20:3320:3520:3820:4020:43

Partial outageUpdate postedTimes in UTC

Investigating

10 min 100%

Updates

Times in UTC

As posted by xAI

Resolved2026-10-27 20:43 UTC

This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.

Investigating2026-10-27 20:33 UTC

We're investigating an issue causing delayed responses in Grok Bot. We'll share an update as soon as we have more information.

Affected components

Grok Bot

xAI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

45 min

This incident

78% 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 45 min

90 days agoToday

Other xAI incidents

All incidents

xAI·Service Degradation - Billing and Usage Dashboard

This incident has been resolved.

Resolvedresolved 9 h 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