# Cursor: Investigating service degradation — Grok Bot

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-09-18 17:19 UTC · Resolved: 2026-09-18 23:02 UTC · Duration: 5.7 h
- Updates: 4 · Affected components: Grok Bot
- [Vendor status page: https://stspg.io/k5db4cd96jlz](https://stspg.io/k5db4cd96jlz)
- [Company: Cursor](https://rewindex.com/company/cursor.md)

## Summary

Cursor reported a major Grok Bot degradation: some users received slow responses or no response. The incident ran from 2026-09-18 17:19 UTC to 2026-09-18 23:02 UTC, lasting 5 h 43 min. A fix was implemented by 19:53 UTC, when Cursor said Grok Bot should be responding normally again. _(machine-written, sol)_
## Timeline of updates

- **investigating** 2026-09-18 17:19 UTC: We are investigating a service degradation affecting Grok Bot.
- **identified** 2026-09-18 19:01 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.
- **monitoring** 2026-09-18 19:53 UTC: A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.
- **resolved** 2026-09-18 23:02 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2026-09-18 17:19 UTC: [Major incident: Investigating service degradation — Grok Bot](https://rewindex.com/change/i0de1eea89ff18e.md)


---
Canonical: https://rewindex.com/company/cursor/incidents/14xbn0wxbpdb · Markdown: https://rewindex.com/company/cursor/incidents/14xbn0wxbpdb.md · JSON: https://rewindex.com/api/v1/companies/cursor/incidents/14xbn0wxbpdb · Generated 2026-10-18T11:30:26.217Z