Live  /  Cursor  /  Incident

Cursor: Grok Bot routines not triggering

Cursor · cursor.comMajor incidentResolved2026-10-13 20:29 UTC
Public — what happened

Summary

Cursor said that on October 13, between 10:52 AM and 1:29 PM PT, many Grok Bot routines triggered by webhooks, Slack, git, email and Linear events did not run. It said people sending webhooks may have received an HTTP 400 error about a rate limit, while other triggers failed without any error message. Cursor stated that customers' own usage was not the reason, and that routines are running normally again. It added that events sent during that window were not processed and will not be retried automatically, so anything important should be resent.

Affected

Grok Bot

As listed on Cursor’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Cursor against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Cursor: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Cursor report →

More from Cursor

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Cursor status & history page.

Related: Cursor status & history. SquidGrid is not affiliated with Cursor.