Cursor experienced a major incident on March 5, 2026, lasting 2h 12m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Mar 05, 2026, 06:36 PM UTC
We are investigating reports of `@Cursor` from Slack not triggering Cloud Agents.
- identified Mar 05, 2026, 07:02 PM UTC
We are discussing with the upstream integration provider to identify the root cause.
- identified Mar 05, 2026, 07:16 PM UTC
We believe this degradation is related to an upstream Slack integration issue. We’re working with Slack on mitigations and will provide updates. You can follow the upstream status page at https://slack-status.com/2026-03/e63ca9cc0d76539c
- monitoring Mar 05, 2026, 08:37 PM UTC
Slack has implemented a fix and we are seeing signs of recovery. We are continuing to monitor the situation.
- resolved Mar 05, 2026, 08:48 PM UTC
This incident has been resolved.