Cursor incident

Investigating service degradation — Grok Bot

Resolved after 5 hours 43 minutes, affecting Grok Bot, on September 18, 2026.

monitoring Sep 18, 2026, 07:53 PM UTC

A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.

Started
Sep 18, 2026, 05:19 PM UTC
Resolved
Sep 18, 2026, 11:02 PM UTC
Duration
5h 43m
Detected by Pingoru
Sep 18, 2026, 05:19 PM UTC

Affected components

Grok Bot

Update timeline

  1. investigating Sep 18, 2026, 05:19 PM UTC

    We are investigating a service degradation affecting Grok Bot.

  2. identified Sep 18, 2026, 07:01 PM UTC

    The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.

  3. monitoring Sep 18, 2026, 07:53 PM UTC

    A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.

  4. resolved Sep 18, 2026, 11:02 PM UTC

    This incident has been resolved.

Your product runs on more than Cursor

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →