Vendor reports: degradedResolved · vendor status “resolved”Official status API

Computer use in Grok Bot fails for users in a few regions.

Reported by Cursor · AI & ML · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Nov 6, 2026, 11:49 UTC
Vendor's clock
Resolved
Nov 6, 2026, 12:03 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
14 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Cursor reports degraded: "Computer use in Grok Bot fails for users in a few regions.".[E1, E2]
  • The vendor marked it resolved at 2026-11-06 12:03 UTC.[E3, E7]

Affected products and regions

  • Components: Grok Bot.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-06 12:03 UTC · summary s1, evidence a64fc65ba7f4ace9

Evidence (7)
  1. E1Cursor reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Computer use in Grok Bot fails for users in a few regions.". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-11-06 11:49 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Grok Bot. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-11-06 12:03 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Grok Bot

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Cursor is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Nov 6, 2026, 11:49 UTCVendor-reported startVendor time
  2. Nov 6, 2026, 12:03 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.