Cursor Watch posted an update
Cursor is investigating a disruption affecting Cloud Agents, according to a status notice posted at 23:29 UTC on 29 October.
Why it mattersThe company has not said which features are affected or when service might recover. If your Cloud Agents workflow has stalled, this is the clearest available explanation so far, though not yet a fix.
Discuss: During an active service disruption, what should a status page prioritise: affected features, user impact or an estimated recovery time?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.